Skip to content

Run jest predictive even when CI rules changes occur

David Dieulivol requested to merge ddieulivol-jest_predictive into master

Context

Closes #443512 (closed)

What does this MR do and why?

Run Jest predictive jobs even when we change the rules.gitlab-ci.yml.

Rationale: Probably around 99% of the changes we make to rules.gitlab-ci.yml are not related to frontend changes, and therefore could happen without running a full Jest suite.

I did keep frontend.gitlab-ci.yml, because I think it would give valuable feedback to have a full Jest suite in those cases (and whenever it's changed, it's probably with high probability we'll want a full Jest suite running).

How to review

I find the diff messy, so I would recommend reviewing by commit:

  • The first two commits are refactorings that should not cause issues
  • The last commit is really what this MR is about: running predictive Jest jobs when we change the rules.gitlab-ci.yml instead of full Jest jobs.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by David Dieulivol

Merge request reports