From adfe29cb46ca7e8c5b8ea30dc31f3244e5fe2e91 Mon Sep 17 00:00:00 2001 From: Eric Engestrom Date: Wed, 16 Apr 2025 15:06:19 +0200 Subject: [PATCH] ci: give high priority to post-merge jobs as well Right now, `deploy-docs` (updating the docs.mesa3d.org website) is the only job that can exist in that pipeline (along with `alpine/x86_64_build`, but that job is always a no-op). Right now this job can get stuck for a long time waiting for a runner, but it's very short, and we kinda want the website to be updated quickly. Part-of: --- .gitlab-ci.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index d73c9e47434..33c58003c4d 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -47,6 +47,10 @@ workflow: DEQP_RUNNER_MAX_FAILS: 40 # post-merge pipeline - if: &is-post-merge $GITLAB_USER_LOGIN == "marge-bot" && $CI_PIPELINE_SOURCE == "push" + variables: + FDO_RUNNER_JOB_PRIORITY_TAG_X86_64: priority:high + FDO_RUNNER_JOB_PRIORITY_TAG_X86_64_KVM: priority:high-kvm + FDO_RUNNER_JOB_PRIORITY_TAG_AARCH64: priority:high-aarch64 # Pre-merge pipeline - if: &is-pre-merge $CI_PIPELINE_SOURCE == "merge_request_event" # Push to a branch on a fork