[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.
pull/942/head
Amir Zarrinkafsh 2020-04-29 13:05:41 +10:00 committed by GitHub
parent c9efae05ad
commit f781d63b2c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions

View File

@ -61,11 +61,15 @@ steps:
- label: ":linux: Deploy AUR" - label: ":linux: Deploy AUR"
command: ".buildkite/steps/aurpackages.sh | buildkite-agent pipeline upload" command: ".buildkite/steps/aurpackages.sh | buildkite-agent pipeline upload"
concurrency: 1
concurrency_group: "aur"
depends_on: ~ depends_on: ~
if: build.tag != null || build.branch == "master" && build.env("CI_BYPASS") != "true" if: build.tag != null || build.branch == "master" && build.env("CI_BYPASS") != "true"
- label: ":book: Deploy Documentation" - label: ":book: Deploy Documentation"
command: "syncdoc.sh" command: "syncdoc.sh"
concurrency: 1
concurrency_group: "documentation"
depends_on: ~ depends_on: ~
agents: agents:
upload: "fast" upload: "fast"