From 50f9bec3ce4424afb508be81ef0fe31e2b8b1fc2 Mon Sep 17 00:00:00 2001 From: Eric Engestrom Date: Tue, 12 Nov 2024 14:53:01 +0100 Subject: [PATCH] ci: raise priority of release manager pipelines KernelCI jobs have priority 44 and are very long-running jobs (and there might be an issue with the KernelCI that makes it create hundreds of jobs, @sergi is looking into that). While bumping to 45+ would be enough to allow Mesa release staging pipelines to run despite the KernelCI, during the CI meeting with @sergi and @mupuf it was determined that the Mesa releases are an important enough operation to warrant being a higher priority than user forks pipelines, so priority 70 was picked (still under the 75 of Marge pipelines). Cc: mesa-stable Part-of: --- .gitlab-ci.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index dfd1b0645a1..0b2ddef746e 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -54,7 +54,7 @@ workflow: # pipeline for direct pushes that bypassed the CI - if: &is-direct-push $CI_PROJECT_NAMESPACE == "mesa" && $CI_PIPELINE_SOURCE == "push" && $GITLAB_USER_LOGIN != "marge-bot" variables: - JOB_PRIORITY: 40 + JOB_PRIORITY: 70 variables: