CI jobs outside of deployments should be interruptible
What does this MR do and why?
In order to limit the amount of pipeline and CI resources we consume we want to have our CI jobs to be interruptible. Meaning that if you push a new commit in a MR with pipeline running theses will be stopped to avoid duplicate pipeline.
This MR, add the interruptible: true keyword in the default: section so all the jobs are interruptible.
It also update the default workflow to be sure that affect triggered pipelines
auto_cancel:
on_new_commit: interruptibleHowever to address some concerns raised in a previous MR review, we set the deployment pipelines with interruptible: false . This mean that when a deployment job is running it will never be stopped.
Example:
If you push/amend a commit before reaching the completion of deployment-jobs or starting a deployment it will cancel any running jobs including the deployment-jobs and the build of the OCI artifacts.
If you push/amend a commit after starting a deployment, it will cancel any running jobs (possibly the build of OCI if you have start a non-oci deployment) BUT it will not cancel the deployment job itself. So you could always see the status of it even if it will not be reflect in the MR widget
Side note, if you amend a commit most of the time it will lead to a deployment failure as the commit used to deploy will no longer exist
Related reference(s)
Test coverage
CI configuration
Below you can choose test deployment variants to run in this MR's CI.
Click to open to CI configuration
Legend:
| Icon | Meaning | Available values |
|---|---|---|
| Infra Provider |
capd, capo, capm3
|
|
| Bootstrap Provider |
kubeadm (alias kadm), rke2
|
|
| Node OS |
ubuntu, suse
|
|
| Deployment Options |
light-deploy, oci, ha, misc
|
|
| Pipeline Scenarios |
rolling-update, mgmt-rolling-update, k8s-upgrade, sylva-upgrade, sylva-upgrade-from-x.x.X, simple-update, preview, nightly
|
-
:clapper:preview :cloud:capd :rocket:kadm :penguin:ubuntu :tools:oci -
:clapper:preview :cloud:capo :rocket:rke2 :penguin:suse -
:clapper:preview :cloud:capm3 :rocket:rke2 :penguin:ubuntu -
:cloud:capd :rocket:kubeadm :tools:light-deploy :penguin:ubuntu -
:cloud:capd :rocket:rke2 :tools:oci,light-deploy :penguin:suse -
:cloud:capo :rocket:rke2 :tools:oci :penguin:suse -
:cloud:capo :rocket:kadm :tools:oci :penguin:ubuntu -
:cloud:capo :rocket:rke2 :clapper:rolling-update :tools:ha :penguin:ubuntu -
:cloud:capo :rocket:kadm :clapper:k8s-upgrade :penguin:ubuntu -
:cloud:capo :rocket:rke2 :clapper:mgmt-rolling-update :tools:ha,misc :penguin:suse -
:cloud:capo :rocket:rke2 :clapper:sylva-upgrade :tools:misc :penguin:ubuntu -
:cloud:capm3 :rocket:rke2 :penguin:suse -
:cloud:capm3 :rocket:kadm :tools:oci :penguin:ubuntu -
:cloud:capm3 :rocket:kadm :clapper:mgmt-rolling-update :tools:ha,misc :penguin:ubuntu -
:cloud:capm3 :rocket:rke2 :clapper:k8s-upgrade :penguin:suse -
:cloud:capm3 :rocket:kadm :clapper:rolling-update :tools:ha :penguin:ubuntu -
:cloud:capm3 :rocket:rke2 :clapper:sylva-upgrade :tools:misc,ha :penguin:suse -
:cloud:capm3 :rocket:kadm :clapper:rolling-update :tools:ha :penguin:suse
Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.