Hi, Le samedi 08 novembre 2025 à 15:31 +0100, Rafael Laboissière a écrit : > Should we add CI pipelines to the Git repositories for our packages at > Salsa.d.o? It seems as simple as adding a debian/salsa-ci.yml file with > the following contents: > > --- > include: > - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml > > However, I have been reluctant to do so because I think it is a waste of > resources, and it is not sustainable to have package builds for every > single commit (or push). Perhaps there are alternative ways, such as > running the CI pipeline under specific conditions, such as when the > debian/changelog file or a CI-specific file is committed, or when a > commit is made in a specific side branch, or according to special > indications in the commit message, etc. Or am I just overly preoccupied > with wasting planet resources? > > What do you think? I personally do not use salsa CI, since I run various tools locally before doing an upload (lintian, piuparts, autopkgtest). Admittedly salsa CI runs even more tools, but I share your concerns about resource usage. To summarize, I’m not against activating salsa CI, but I’m also fine with the statu quo. Best, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ https://www.debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part