Richard Lewis <richard.lewis.debian-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> writes: > Otto Kekäläinen <otto-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org> writes: > >> Hi! >> >>> > Salsa CI is a great system for all aspiring Debian packagers to test >>> > their packages before requesting review from mentors >>> >>> > However, as there are still packages not using Salsa CI, I wonder is >>> > it straightforward enough for everyone? >>> > >>> >>> I think the best solution would be to make it opt-in rather than >>> opt-out? >>> >>> i think the barrier is likely to be "i didnt know you could do that?" >>> rather than "how do i use that?" >> >> Salsa CI is and has always been opt-in. > > oops - i meant the oppposite, ie make people have to opt out of having > it run, rather than have to enable it Is it possible to configure Salsa so instead of using the GitLab default of .gitlab-ci.yml it uses debian/salsa-ci.yml if that file exists but otherwise falls back to recipes/debian.yml@salsa-ci-team/pipeline? That seems like a sensible global configuration for Salsa. If we make the default value "debian/salsa-ci.yml" maintainers have to create that file in their packages and some may not know about it. Using "recipes/debian.yml@salsa-ci-team/pipeline" as the default value make things just work, but for fine tuning the maintainer have to manually override the configuration to use debian/salsa-ci.yml. I note that having bare git repository with only debian/ in them (no upstream source code) allows for using the default GitLab behaviour of a .gitlab-ci.yml. /Simon
Attachment:
signature.asc
Description: PGP signature