From 2e5a3bde7ee0123e3af5432f45447776ebea90b9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicki=20K=C5=99=C3=AD=C5=BEek?= Date: Mon, 27 Jan 2025 15:30:39 +0100 Subject: [PATCH] Run merged-metadata job for release branches in private repo The prior regex didn't match the actual names we use for release branches in the private repo. This caused the merged-metadata job to not be created upon merging to a release branch, resulting in the private MR not being properly milestoned. Use the correct regex along with protecting the v9.*-release branches in the gitlab UI so that they have access to the token used to perform the required API operations. --- .gitlab-ci.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 8ab95af295..be5c0ed73c 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -1827,6 +1827,6 @@ backports: merged-metadata: <<: *post_merge rules: - - if: '$CI_PIPELINE_SOURCE == "push" && ($CI_COMMIT_REF_NAME =~ /^bind-9.[0-9]+(-sub)?$/ || $CI_COMMIT_REF_NAME =~ /^bind-9.[0-9]+.[0-9]+-release$/ || $CI_COMMIT_REF_NAME == $CI_DEFAULT_BRANCH)' + - if: '$CI_PIPELINE_SOURCE == "push" && ($CI_COMMIT_REF_NAME =~ /^bind-9.[0-9]+(-sub)?$/ || $CI_COMMIT_REF_NAME =~ /^v9.[0-9]+.[0-9]+-release$/ || $CI_COMMIT_REF_NAME == $CI_DEFAULT_BRANCH)' script: - bind9-qa/releng/after_merge.py "$CI_PROJECT_ID" "$MERGE_REQUEST_ID"