All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Taylor Blau <me@ttaylorr.com>,
	git@vger.kernel.org,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Derrick Stolee <derrickstolee@github.com>,
	Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/1] ci: avoid unnecessary builds
Date: Tue, 8 Nov 2022 15:09:35 -0500	[thread overview]
Message-ID: <Y2q3f5noQSXmK0o8@nand.local> (raw)
In-Reply-To: <221108.86r0ydqmts.gmgdl@evledraar.gmail.com>

On Tue, Nov 08, 2022 at 07:52:07PM +0100, Ævar Arnfjörð Bjarmason wrote:
> I.e. the "cancel-in-progress" seems to work perfectly. I pushed a branch
> with this, it started CI, then I made a trivial update, re-pushed, and
> the initial branch's CI run was stopped, one job at a time (not all at
> the same time, but almost).

Thanks to Johannes for all of that ;-).

> Now, obviously it's a bit more of a verbose solution v.s. Johannes's
> original in [1], but on the other hand our main.yml is full of that sort
> of copy/pasting already.
>
> Aside from the change under discussion I don't find that to be a big
> deal. It's a general "problem", and we could always generate the file
> with a script if we really cared, but I think for the forseeable future
> the copy/pasting is fine.

To be fair, I think that the solution I came up with is pretty gross.
But after spending a few hours with the Actions docs, I think that it's
the least-gross solution that meets the needs of our respective
workflows.

So I'm OK with it.

Thanks,
Taylor

      parent reply	other threads:[~2022-11-08 20:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 18:25 [PATCH 0/1] ci: avoid unnecessary builds, with ci-config Taylor Blau
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 [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y2q3f5noQSXmK0o8@nand.local \
    --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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.