From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org, git@vger.kernel.org
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Derrick Stolee" <derrickstolee@github.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jeff King" <peff@peff.net>, "Junio C Hamano" <gitster@pobox.com>
Subject: [PATCH 0/1] ci: avoid unnecessary builds, with ci-config
Date: Tue, 8 Nov 2022 13:25:42 -0500 [thread overview]
Message-ID: <cover.1667931937.git.me@ttaylorr.com> (raw)
This is an alternative approach to Johannes's patch in [1], which
cancels running GitHub Actions workflows when newer ones appear via the
'concurrency' controls.
Though the original patch was promising, it does not satisfy all
workflows. A couple examples:
- ÆVar points out in [2] that he pushes a topic branch multiple times
while working on it to see where CI breaks along a stream of
commits.
- Junio points out in [3] that he will often push various combinations
of topics merged into 'seen' to try and "bisect" the culprit when
debugging CI failures.
On the other hand, being able to cancel previously initiated runs of a
workflow on a given branch name is useful when the branch has been
updated locally and the results of the in-progress CI run are no longer
interesting.
This patch takes an alternative approach to the original patch in [1] by
using the same ci-config mechanism to cancel in-progress jobs when newer
ones appear only when configured to do so.
The original patch I posted with this approach in [4] had syntax issues.
This approach works as expected.
Thanks in advance for your review.
[1]: https://lore.kernel.org/git/pull.1404.git.1667482458622.gitgitgadget@gmail.com/
[2]: https://lore.kernel.org/git/221104.86bkpnzdqi.gmgdl@evledraar.gmail.com/
[3]: https://lore.kernel.org/git/xmqqk046cmmv.fsf@gitster.g/
[4]: https://lore.kernel.org/git/Y2R3vJf1A2KOZwA7@nand.local/
Taylor Blau (1):
ci: avoid unnecessary builds
.github/workflows/check-whitespace.yml | 6 ++++
.github/workflows/l10n.yml | 6 ++++
.github/workflows/main.yml | 40 ++++++++++++++++++++++++--
3 files changed, 50 insertions(+), 2 deletions(-)
--
2.38.0.16.g393fd4c6db
next reply other threads:[~2022-11-08 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 18:25 Taylor Blau [this message]
2022-11-08 18:25 ` [PATCH 1/1] ci: avoid unnecessary builds Taylor Blau
2022-11-08 18:52 ` Ævar Arnfjörð Bjarmason
2022-11-08 20:08 ` Taylor Blau
2022-11-08 20:09 ` Taylor Blau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1667931937.git.me@ttaylorr.com \
--to=me@ttaylorr.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).