Update remaining only except to rules in pipeline
What does this MR do?
Related to #5019 (closed)
Following on my previous MRs, this removes the final examples of only
and except
from the Runner pipeline.
The remaining usage of only
/ except
was in relation to releases, and all those are now updated to rules. The release rules were added to .gitlab/ci/_rules.gitlab-ci.yml
.
It's a bit difficult to follow, but most jobs (eventually, after multiple hops) inherited the .docker
template job, and the settings were overrode along the way (sometimes multiple times).
To change all instances to rules, I followed this process:
- Find every
extends:
that addedonly
orexcept
to a job, and then copy that inheritedonly
/except
config directly into the job ("interim"). - Find all the different interim:
only
/except
combinations, and create newrules
for each one. - Replace the interim
only
/except
in every job with a newextends
to the appropriate rule. - A few
.job
sections hadonly
/except
, and those were removed. - Any
.job
sections that wereonly
/except
only were now blank, and completely removed, for example:.release_development:
.release_bleeding_edge:
.release_stable:
Why was this MR needed?
What's the best way to test this MR?
What are the relevant issue numbers?
Edited by Marcel Amirault