decentraland / builder / 36749737352

57%

master: 57%

Pull #3511

github

fix: give each deploy path its own concurrency group

One group for the whole workflow meant a release and a push could never run at
the same time, and GitHub keeps only one pending run per group: a release
waiting behind a push deploy was cancelled outright when the next push landed.
A cancelled run deploys nothing and reports no failure, which is the failure
this migration is most prone to.

Serialising them here was never what protected the KV record. The broker takes
a lease per environment and record before it writes, and answers
`rollout_in_progress` with a Retry-After that the action already treats as
retryable, so two deploys reaching the write at once resolve on their own.

Pushes keep a shared group, where a newer commit superseding a pending older
one is the wanted behaviour. Releases are keyed by tag and promotions by
environment, so neither can cancel the other.

2637 of 5727 branches covered (46.05%)

Branch coverage included in aggregate %.

7631 of 12288 relevant lines covered (62.1%)

37.27 hits per line