[Debian-salsa-ci] Release team to utilize Salsa CI for Forky quality assurance?

[Andrea Pappacoda]

Hi all,

On Sun Jun 7, 2026 at 4:56 PM CEST, Otto Kekäläinen wrote:
> Hi Debian Release Team,
>
> I am resurrecting this proposal for using the Salsa CI status in
> unstable->testing migration.
>
> Specifically I'd like to float the idea that IF a project uses Salsa
> CI, AND IF the Salsa CI was failing (red) for the git tag
> corresponding to the upload (vcswatcher already has this data), the
> migration would be delayed by 10 days.

This in principle would be very good. Still, I feel Salsa CI is still 
not reliable enough for these kinds of penalties.

One third of my packages report a failure in the VCS column of my DDPO 
page, to failures related to either Salsa CI or Salsa itself. For some 
of these, the failures are not transient and are caused by limitations 
of Salsa CI, and I don't bother with checking them anymore since they 
are so frequent.

https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/371

I hope that things will get better soon! I'm not motivated enough to fix 
them myself as I configured my local sbuild to run lintian and 
autopkgtests after build, and paired with git-debpush it gives me 
a somewhat high confidence of the quality of my uploads. Still, better 
CI would be a plus :)

Bye!