You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Test] Key exclusive concurrency group on --env-file, not build id (#9949)
Exclusive smoke steps (--exclusive) are serialized via a Buildkite
concurrency group. Keying it on BUILDKITE_BUILD_ID only serializes steps
within one build, so two exclusive builds targeting the same server (a
re-triggered run, or a deploy-and-test command racing a manual run) can run
server-mutating tests concurrently and corrupt each other.
Key the group on a hash of the --env-file value instead, so all exclusive
runs against the same target serialize regardless of which build triggered
them. Fall back to the build id when no --env-file is given (each build
isolated, as before).
0 commit comments