On Thu, 13 Jun 2024 at 14:34, Timo Röhling <roehl...@debian.org> wrote: > > Hi, > > * Luca Boccassi <bl...@debian.org> [2024-06-13 14:23]: > >As far as I understand in the current proposal the trigger is a > >webhook running on Salsa after a push - have you considered instead > >having the trigger be a stage in the salsa-ci pipeline, that would run > >after the previous stages have completed successfully? > I hate that idea. From past experience, the Salsa CI pipeline is > slower and much more flaky than the buildds, so I'm not going to > spend several hours (and retries) per upload waiting to see if the > Salsa CI deemed my upload worthy.
Pipeline stages are by definition locally controlled, as the configuration lives in the git repository it runs for, so a maintainer can disable some or all of them on your repositories. >From past experience, the Salsa CI pipeline has been a huge boon, finding issues that would have otherwise been missed, and ensuring everything goes under the same degree of testing, regardless of where it comes from. Not to mention the massive time saver it is: just push and come back later and see the result, instead of driving things manually.
