Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?
Hi,
Andreas Tille <andreas@an3as.eu> ezt írta (időpont: 2024. aug. 22., Cs, 17:22):
>
> Am Tue, Aug 20, 2024 at 06:35:52PM -0700 schrieb Otto Kekäläinen:
> > ...
>
> ACK to everything.
>
> > However, pushing for wider Salsa CI adoption I think makes sense as a
> > goal by itself, and I would be keen to hear what people think is a
> > reasonable way to proceed with that?
>
> ACK. What about configuring Salsa that Salsa CI is switched on by
> default?
>
> Since 2021 I'm discussing with Debian Java team (last mail about this in
> my DPL contact[1]) to not hide the "Switch Salsa CI on"-button which
> makes it extra hard to get Salsa CI for these packages. Not sure about
> other teams but IMHO the better strategy would be to make it extra
> hard to switch of Salsa CI.
I wholeheartedly agree with Otto's goals in his first email and wanted
to propose the same, just make Salsa CI opt-out instead of opt-in.
The default (recipes/debian.yml@salsa-ci-team/pipeline) should work
well for most packages.
There is another thread about enabling Salsa CI team-wide involving
multiple teams and it did not progress much:
https://salsa.debian.org/salsa/support/-/issues/170
Enabling CI by default Salsa-wide would finally end those time
consuming discussions, too.
Cheers,
Balint
> Kind regards
> Andreas.
>
> [1] https://lists.debian.org/debian-java/2024/06/msg00007.html
>
> --
> https://fam-tille.de
>
Reply to: