CI: Use fast-ci by default?!
I think that it's a bit unfortunate that many simple MRs like documentation changes or small refactorings result in so much unnecessary CI work. Therefore I'd like to suggest that the reduced CI pipeline which can currently be enabled via the fast-ci
label is made the default. MRs that need more thorough checking could get the old CI behaviour via a new label named e.g. full-ci
or thorough-ci
. Marge Bot should also continue using the "full CI" mode.
Advantages:
- Good patches and bad patches that fail on all platforms use less CI capacity. (3 jobs vs 11 for the "Full-build" stage)
- MRs using the default CI configuration are less likely to fail due to spurious CI failures.
Disadvantages:
- Some platform-specific problems are detected only at the Marge-Bot stage and require triage to pinpoint the responsible MR.
I'd expect that a few tweaks to the fast-ci
job selection could eventually reduce the number of failures that make it to the Marge-Bot stage.