On Wed, Nov 23, 2022 at 09:17:41AM +0100, IOhannes m zmölnig (Debian GNU|Linux) wrote: > i noticed that sonic-pi has a CI pipeline schedule [1], which builds > sonic-pi each day at 8:30CET. > > CI rulez, but is there any specific reason to keep building the same package > day after day? > this seems like a waste of resources to me: even though sonic-pi is rather > quick to build (i think the entire pipeline takes about 15min), it piles up. > also, each build creates artifacts worth ~290MB (compressed), and the last > 28 artifacts are kept.
I don't think this is too much resources and if Salsa is overloaded, Debian should have enough money to scale it up. > the last change to sonic-pi was about 100 days ago. since then sonic-pi has > been built a hundred times without anyone making anybody the wiser. > afaict, the pipeline failed a couple of times, but was this ever monitored? Although the package has not changed, many of its dependencies have changed and I want to know if it still builds and works correctly through the use of autopkgtests. For example, see this other package: https://salsa.debian.org/ha-team/gfs2-utils/-/pipelines It failed building recently and I was able do compare the versions of dependencies to see that pkg-config was updated and than make a fix based on that change. If the daily build was not there I would only notice this on the next package update many months later and it would be harder to fix. > so here's my question/plea: can we stop scheduled pipelines in general? and > in the odd case that a scheduled pipeline is something you *really* need, > would it be possible to also set up a schedule (on the personal calendar of > the maintainer who deemed the schedule absolutely necessary) to reevaluate > and eventually remove the scheduled pipeline? Another problem is that Salsa CI is noisy and sometimes fails for other reasons. Maybe there is a way to configure the notifications so only I will receive them? -- Valentin
