Le mercredi, 27 août 2025, 01.16:20 h heure d’été d’Europe centrale Antoine Le
Gonidec a écrit :
> Le Wed, Aug 27, 2025 at 12:24:18AM +0200, Alexander Wirt a écrit :
> > Today one project
> > (node-glob?!?) alone took 25% of all jobs (2700?!? I really have to check
> > those numbers afer some sleep, but all others numbers look sane).
>
> Probably not a mistake on your part. That package triggers jobs for each
> of its reverse build-deps, and it has 1360 of these in unstable. Two
> jobs for each of these and we get almost exactly to the 2700 number
> you’re reporting.
An important question to ask is: does it really need to proceed to trigger
2000+ jobs _at every commit_ (= technically, at every branch ref update pushed
to Salsa)?
Gitlab CI yaml syntax allows a lot of flexibility to determine when the CI
gets ran automatically, manually, or not at all (see rules: in
https://salsa.debian.org/help/ci/yaml/_index.md#rules , it can also filter on
commit message regexps, branch names, merge request conditions, etc), and I'd
argue that the salsa-ci-team/pipeline should perhaps grow the capability (I
have not checked, perhaps it exists already) to only launch on `debian/
latest`, or manually, or allow customizations.
Of course, having a full CI at every ref update can be useful (provided that
someone actively cares when this fails), but there are many cases in which the
pusher knows that their packaging change will not have an impact, and perhaps
we should default to not having CI always be ran.
--
OdyXAttachment:
signature.asc
Description: This is a digitally signed message part.