Git development
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
	"Todd Zullinger" <tmz@pobox.com>,
	"SZEDER Gábor" <szeder.dev@gmail.com>
Subject: Re: [PATCH v3 2/8] ci: fix "fedora-breaking-changes-meson" job
Date: Wed, 14 Oct 2026 12:35:08 +0200	[thread overview]
Message-ID: <as9a3E6NeR_sQeYd@pks.im> (raw)
In-Reply-To: <20261014091037.GB1341124@coredump.intra.peff.net>

On Wed, Oct 14, 2026 at 05:10:37AM -0400, Jeff King wrote:
> On Wed, Oct 14, 2026 at 10:30:28AM +0200, Patrick Steinhardt wrote:
> 
> > The "fedora-breaking-changes-meson" job exercises Git with breaking
> > changes enabled on Fedora with Meson. There's a typo in our CI scripts
> > though, which has the effect that the build does not enable breaking
> > changes by accident.
> >
> > [...]
> >
> >  case "$jobname" in
> > -fedora-breaking-changes-musl|linux-breaking-changes)
> > +fedora-breaking-changes-meson|linux-breaking-changes)
> >  	export WITH_BREAKING_CHANGES=YesPlease
> >  	MESONFLAGS="$MESONFLAGS -Dbreaking_changes=true"
> >  	;;
> 
> Seems obviously correct, but I wonder if just:
> 
>   *breaking-changes*)
> 
> would fix this and prevent any issues for possible future jobs. The
> downside of a loose pattern is false matches, but it seems like a small
> risk given our universe of jobs.

In general I think the way we structure these is somewhat lackluster:

  - I never really understood the split between "ci/lib.sh" and
    "ci/run-build-and-tests.sh".

  - There is a bunch of duplication that could be avoided.

  - And your suggestion makes sense, too.

I originally carried a patch that merges all of this into "ci/lib.sh",
and it also did changes similar to what you propose. We could probably
revive that patch, but if so I'd propose to do that as a follow-up.

Patrick

  reply	other threads:[~2026-10-14 10:35 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 10:01 [PATCH 0/8] ci: some housekeeping and modernizations Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 1/8] t5004: skip SHA-1-only test in SHA-256 repository Patrick Steinhardt
2026-10-08 18:05   ` Junio C Hamano
2026-10-09  5:46     ` Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 2/8] ci: fix "fedora-breaking-changes-meson" job Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 3/8] ci: drop unused "linux-clang" logic Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 4/8] ci: switch away from unsupported i386/ubuntu image Patrick Steinhardt
2026-10-08 15:03   ` Todd Zullinger
2026-10-08 18:12     ` Junio C Hamano
2026-10-09  5:46       ` Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 5/8] ci: rename linux-TEST-vars job Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 6/8] ci: switch away from EOL'd Ubuntu version in linux-exotic Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 7/8] ci: drop now-dead Python 2 coverage Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 8/8] ci: drop redundant linux-reftable job Patrick Steinhardt
2026-10-08 18:18   ` Junio C Hamano
2026-10-09  5:55     ` Patrick Steinhardt
2026-10-09 20:22       ` Junio C Hamano
2026-10-09 11:31 ` [PATCH v2 0/8] ci: some housekeeping and modernizations Patrick Steinhardt
2026-10-09 11:31   ` [PATCH v2 1/8] t5004: skip SHA-1-only test in SHA-256 repository Patrick Steinhardt
2026-10-09 11:31   ` [PATCH v2 2/8] ci: fix "fedora-breaking-changes-meson" job Patrick Steinhardt
2026-10-09 11:32   ` [PATCH v2 3/8] ci: drop unused "linux-clang" logic Patrick Steinhardt
2026-10-09 11:32   ` [PATCH v2 4/8] ci: switch away from unsupported i386/ubuntu image Patrick Steinhardt
2026-10-09 11:32   ` [PATCH v2 5/8] ci: rename linux-TEST-vars job Patrick Steinhardt
2026-10-09 15:31     ` SZEDER Gábor
2026-10-13  7:21       ` Patrick Steinhardt
2026-10-13 14:47         ` Junio C Hamano
2026-10-14  7:03           ` Patrick Steinhardt
2026-10-09 11:32   ` [PATCH v2 6/8] ci: switch away from EOL'd Ubuntu version in linux-exotic Patrick Steinhardt
2026-10-09 11:32   ` [PATCH v2 7/8] ci: drop now-dead Python 2 coverage Patrick Steinhardt
2026-10-09 11:32   ` [PATCH v2 8/8] ci: improve reftable test coverage Patrick Steinhardt
2026-10-14  8:30 ` [PATCH v3 0/8] ci: some housekeeping and modernizations Patrick Steinhardt
2026-10-14  8:30   ` [PATCH v3 1/8] t5004: skip SHA-1-only test in SHA-256 repository Patrick Steinhardt
2026-10-14  9:07     ` Jeff King
2026-10-14 10:34       ` Patrick Steinhardt
2026-10-14  8:30   ` [PATCH v3 2/8] ci: fix "fedora-breaking-changes-meson" job Patrick Steinhardt
2026-10-14  9:10     ` Jeff King
2026-10-14 10:35       ` Patrick Steinhardt [this message]
2026-10-14 11:07         ` Jeff King
2026-10-14 11:18           ` Patrick Steinhardt
2026-10-14  8:30   ` [PATCH v3 3/8] ci: drop unused "linux-clang" logic Patrick Steinhardt
2026-10-14  8:30   ` [PATCH v3 4/8] ci: switch away from unsupported i386/ubuntu image Patrick Steinhardt
2026-10-14  9:17     ` Jeff King
2026-10-14 10:35       ` Patrick Steinhardt
2026-10-14 11:08         ` Jeff King
2026-10-14  8:30   ` [PATCH v3 5/8] ci: rename linux-TEST-vars job Patrick Steinhardt
2026-10-14  9:17     ` Jeff King
2026-10-14  8:30   ` [PATCH v3 6/8] ci: switch away from EOL'd Ubuntu version in linux-feature-testbed Patrick Steinhardt
2026-10-14  9:18     ` Jeff King
2026-10-14  8:30   ` [PATCH v3 7/8] ci: drop now-dead Python 2 coverage Patrick Steinhardt
2026-10-14  8:30   ` [PATCH v3 8/8] ci: improve reftable test coverage Patrick Steinhardt
2026-10-14  9:21     ` Jeff King
2026-10-14 10:35       ` Patrick Steinhardt
2026-10-14 11:13         ` Jeff King
2026-10-14 11:18           ` Patrick Steinhardt
2026-10-14 13:47             ` Jeff King
2026-10-14  9:22   ` [PATCH v3 0/8] ci: some housekeeping and modernizations Jeff King

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=as9a3E6NeR_sQeYd@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=szeder.dev@gmail.com \
    --cc=tmz@pobox.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox