summaryrefslogtreecommitdiff
path: root/config.sub
diff options
context:
space:
mode:
authorDouglas Wilson <douglas.wilson@gmail.com>2021-03-18 09:29:28 +0000
committerMatthew Pickering <matthewtpickering@gmail.com>2021-06-23 07:48:59 +0000
commit10a5659a68dac07abcffc6e7b069a9870292580c (patch)
tree6817d9594d521902fd15c1bc82f0d31e00f67768 /config.sub
parent8fba28ec51f9aaaa396b8afb2a3ba8984eabe38e (diff)
downloadhaskell-wip/no-ci-cancel.tar.gz
ci: Don't allow the nightly pipeline to be interrupted.wip/no-ci-cancel
Since 58cfcc65 the default for jobs has been "interruptible", this means that when new commits are pushed to a branch which already has a running pipeline then the old pipelines for this branch are cancelled. This includes the master branch, and in particular, new commits merged to the master branch will cancel the nightly job. The semantics of pipeline cancelling are actually a bit more complicated though. The interruptible flag is *per job*, but once a pipeline has run *any* non-interruptible job, then the whole pipeline is considered non-interruptible (ref https://gitlab.com/gitlab-org/gitlab/-/issues/32837). This leads to the hack in this MR where by default all jobs are `interruptible: True`, but for pipelines we definitely want to run, there is a dummy job which happens first, which is `interreuptible: False`. This has the effect of dirtying the whole pipeline and preventing another push to master from cancelling it. For now, this patch solves the immediate problem of making sure nightly jobs are not cancelled. In the future, we may want to enable this job also for the master branch, making that change might mean we need more CI capacity than currently available. [skip ci] Ticket: #19554 Co-authored-by: Matthew Pickering <matthewtpickering@gmail.com>
Diffstat (limited to 'config.sub')
0 files changed, 0 insertions, 0 deletions