Skip to content

Commit

Permalink
ci(web-server): limit workflow concurrency to avoid GHA rate limits
Browse files Browse the repository at this point in the history
There seems to be an issue currently where concurrent builds cause the
Docker GHA cache exporter to trip over GitHub throttling limits.

Background reading:

- buildx failed with: error: failed to solve: blob not found #422
docker/build-push-action#422

- Copy from previous stage fails #681
docker/buildx#681

- GHA export cache fails with mode=max #2276
moby/buildkit#2276

Try to work around this by limiting the overall concurrency to 1 for
this workflow.
  • Loading branch information
PiDelport committed Sep 2, 2021
1 parent 7f21365 commit 0ff2643
Showing 1 changed file with 14 additions and 0 deletions.
14 changes: 14 additions & 0 deletions .github/workflows/web-server.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,20 @@ defaults:
run:
working-directory: web-server

# There seems to be an issue currently where concurrent builds cause the Docker GHA cache exporter
# to trip over GitHub throttling limits.
#
# Background reading:
#
# - buildx failed with: error: failed to solve: blob not found #422 https://github.com/docker/build-push-action/issues/422
# - Copy from previous stage fails #681 https://github.com/docker/buildx/issues/681
# - GHA export cache fails with mode=max #2276 https://github.com/moby/buildkit/issues/2276
#
# Try to work around this by limiting the overall concurrency to 1 for this workflow.
#
# Docs: https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#concurrency
concurrency: workflow-${{ github.workflow }}

jobs:
build:
runs-on: ubuntu-latest
Expand Down

0 comments on commit 0ff2643

Please sign in to comment.