Skip to content

fix(pdm/docker): isolate GHA cache scope per image to prevent same repo concurrent builds cache poisoning#480

Draft
thomasLAtLedger wants to merge 1 commit intomainfrom
fix/cache-poisoning-same-repository-concurrent-docker-build
Draft

fix(pdm/docker): isolate GHA cache scope per image to prevent same repo concurrent builds cache poisoning#480
thomasLAtLedger wants to merge 1 commit intomainfrom
fix/cache-poisoning-same-repository-concurrent-docker-build

Conversation

@thomasLAtLedger
Copy link
Copy Markdown
Contributor

Multiple PRs building the same repo concurrently all wrote to the same default buildkit GHA cache scope, causing manifest overwrites and 10GB eviction pressure. Scope cache by image name (+ suffix) so each image gets an isolated bucket while still sharing cache across branches.

Also removes the redundant cache-to from the GOSS build step — the push step immediately overwrites it, so the GOSS write was pure waste.

…ent build collisions

Multiple PRs building the same repo concurrently all wrote to the same
default `buildkit` GHA cache scope, causing manifest overwrites and
10GB eviction pressure. Scope cache by image name (+ suffix) so each
image gets an isolated bucket while still sharing cache across branches.

Also removes the redundant `cache-to` from the GOSS build step — the
push step immediately overwrites it, so the GOSS write was pure waste.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@thomasLAtLedger thomasLAtLedger self-assigned this Apr 30, 2026
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