Skip to content

ci: run deploys one at a time - #51

Merged
Musiker15 merged 1 commit into
mainfrom
ci/deploy-concurrency
Sep 16, 2026
Merged

Musiker15 merged 1 commit into
mainfrom
ci/deploy-concurrency

Conversation

@Musiker15

Copy link
Copy Markdown
Member

Merging several PRs back to back starts one deploy per merge, and those ran in parallel against the same DocumentRoot. On 16.09. six Dependabot merges produced six parallel runs. Two of them failed because another run's post-deploy step had already moved csp-hashes.conf out of the DocumentRoot. The last run was green and the site is fine, but a stale upload finishing last could just as well have won.

This adds a concurrency group to deploy.yml:

  • only one deploy runs at a time
  • cancel-in-progress: false, so a running upload is never interrupted halfway
  • GitHub keeps only the newest waiting run, so the site always ends up on the latest commit

Only the workflow file changes. Merging this triggers a normal deploy of the current main.

Merging several PRs back to back started parallel deploys into the same
DocumentRoot. One run's post-deploy step moved csp-hashes.conf while
another run still needed it, so two of six runs on 16.09. failed.

A concurrency group now queues them. Running deploys are not cancelled,
an interrupted upload would leave a half-updated site.
@github-actions

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@Musiker15
Musiker15 merged commit 6fb1d67 into main Sep 16, 2026
3 checks passed
@Musiker15
Musiker15 deleted the ci/deploy-concurrency branch September 16, 2026 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant