Gitlab CI: pipelines on master should not be interruptible
From !5086 (comment 339598). @angerman writes:
Ha, this has the nice(not!) side effect of canceling all builds on master now as well. Yikes. When ever something new is pushed to master, we'll cancel all existing builds on master.
I still think we should build all commits on master just for good measure. I think reverting this will not be a good idea, it will just increase load on CI for mostly useless runs. We should rather try to fix this properly and throw those ressources at building each and every commit on master.
Sadly there is https://gitlab.com/gitlab-org/gitlab/-/issues/194023, which indicates we can't trivbially set interruptable with a rule.
This is disappointing. I'm pessimistic that there is a proper solution, but I do have one idea: apparently pipelines are interruptible if and only if an uninterruptible job has not started for that pipeline. So a conditional, uninterruptible no-op job, that runs only on master may solve it. I'll try.