salsa: unconditional rebuild of all reverse dependencies on every push considered abuse (was "Salsa CI overload")

[Antonio Terceiro]

On Thu, Aug 28, 2025 at 09:00:41AM +0200, Didier 'OdyX' Raboud wrote:
> 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)?

Not only it's not needed, it's also considered abuse of the salsa
infrastructure. I'm copying this message to all packages that seem to be
doing this (based on a search for debian/rdeps-ci.yml on codesearch).

Please note: if your package CI is triggering the rebuild of all reverse
dependencies on every single push, you are abusing the salsa
infrastructure. I do not imply malice, it's most probably just an
oversight.

I ask, however, that the maintainers of each package in Cc: to look into
it and take action to mitigate the abuse of shared resources (otherwise
I will have to). Maybe your packages does not have as many reverse
dependencies as node-glob, and it's fine, but please think about the
collective.

> 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.

There is a similar feature being developed for Salsa CI proper, as part
of a GSoC project. But in there, it needs to be explicitly triggered by
a person. I also suggested to the developer working on this to provide
an option of triggering the rebuild of a sample of the of reverse
dependencies, instead of all, and he said he'll work on it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-maintainers/attachments/20250828/a552c850/attachment.sig>