ci/farm-rules: re-add "run every container and build job when a farm gets re-enabled"

Turns out I was right the first time, I was just missing that this
should only be done in MRs, which @daniels added in 16527f6ffd.

Without this, a "farm re-enable" pipeline will run all the jobs for that
farm, but will have none of the container & build jobs to support these
tests.

This reverts commit 1c3097225a.

Fixes: 1c3097225a ("ci: don't run everything just because a farm gets re-enabled")
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25243>
This commit is contained in:
Eric Engestrom
2023-09-15 12:09:43 +01:00
committed by Marge Bot
parent 67c7f391b3
commit 83d856d4bc
2 changed files with 13 additions and 3 deletions

View File

@@ -156,7 +156,7 @@ include:
# When to automatically run the CI for build jobs
.build-rules:
rules:
# Don't run when disabling a farm
# Run when re-enabling a disabled farm, but not when disabling it
- !reference [.disable-farm-mr-rules, rules]
# If any files affecting the pipeline are changed, build/test jobs run
# automatically once all dependency jobs have passed
@@ -200,7 +200,7 @@ include:
.container-rules:
rules:
# Don't run when disabling a farm
# Run when re-enabling a disabled farm, but not when disabling it
- !reference [.disable-farm-mr-rules, rules]
# Run pipeline by default in the main project if any CI pipeline
# configuration files were changed, to ensure docker images are up to date