From ad5bb38d7079f7ed7617b0960554665e902c6cef Mon Sep 17 00:00:00 2001 From: Wolfgang Walther Date: Tue, 21 May 2024 20:42:54 +0200 Subject: [PATCH] ci: Don't cancel previous runs for tag pipelines Those create annoying "cancelled" notifications which looks like CI on main was failing. It's not, though. By just disabling the cancel-in-progress setting, but keeping the group intact, this should queue multiple tag jobs / tag workflows behind each other and still avoids the underlying problem which occurs when running them in parallel. --- .github/workflows/ci.yaml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml index 37b5a8687..be982fa3a 100644 --- a/.github/workflows/ci.yaml +++ b/.github/workflows/ci.yaml @@ -13,7 +13,8 @@ concurrency: # Terminate all previous runs of the same workflow for the same tag, but never # cancel for the main / release branch pipelines. group: ci-${{ (github.ref_type == 'tag' && github.ref) || github.run_id }} - cancel-in-progress: true + # TODO: Enable this once https://github.com/orgs/community/discussions/13015 is solved + cancel-in-progress: false jobs: check: @@ -110,7 +111,8 @@ jobs: concurrency: # Never tag outdated commits on the main branch by skipping superseded commits group: ci-tag-${{ (github.ref == 'refs/heads/main' && github.ref) || github.run_id }} - cancel-in-progress: true + # TODO: Enable this once https://github.com/orgs/community/discussions/13015 is solved + cancel-in-progress: false if: | vars.RELEASE_ENABLED && startsWith(github.ref, 'refs/heads/') &&