Skip to content

ci: Run less jobs upon CI changes

Rémy Coutable requested to merge 412895-re-evaluate-what-jobs-we-want-to-run-for-ci-changes-2 into master

What does this MR do and why?

Second attempt at !122119 (merged), which was reverted with !122966 (merged) due to #414760 (closed).

This changes the strategy to not run everything when any CI config files are changed. We're very reactive when CI config is broken and fixes is usually to revert the change right away, so there's no need to run everything for any CI config change.

Though, maybe we should incentivize to add pipeline:run-all-rspec before merging MRs that touch any CI config file?

Note: There are still jobs that will run when a dependent CI config file is changed, but otherwise, this would reduce the cases where we run a lot of jobs just because a .gitlab/ci/**/* file was changed.

Testing

Testing the broken use-case of #414760 (closed) with !123135 (closed).

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #412895

Edited by Rémy Coutable

Merge request reports