From f781d63b2c7de8a4b7cb7944dae28c7c9663739d Mon Sep 17 00:00:00 2001 From: Amir Zarrinkafsh Date: Wed, 29 Apr 2020 13:05:41 +1000 Subject: [PATCH] [CI] Prevent race conditions with appropriate deployment steps (#941) If we have multiple builds to master that intend to deploy AUR packages or documentation, we must ensure that the jobs are locked and executed sequentially, not simultaneously. If they were to run simultaneously this has the ability to cause a race condition when attempting to commit the respective steps. --- .buildkite/deployment.sh | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.buildkite/deployment.sh b/.buildkite/deployment.sh index 8e6e898e7..92e468244 100755 --- a/.buildkite/deployment.sh +++ b/.buildkite/deployment.sh @@ -61,11 +61,15 @@ steps: - label: ":linux: Deploy AUR" command: ".buildkite/steps/aurpackages.sh | buildkite-agent pipeline upload" + concurrency: 1 + concurrency_group: "aur" depends_on: ~ if: build.tag != null || build.branch == "master" && build.env("CI_BYPASS") != "true" - label: ":book: Deploy Documentation" command: "syncdoc.sh" + concurrency: 1 + concurrency_group: "documentation" depends_on: ~ agents: upload: "fast"