BUILD-10457 Include BUILD_NAME in promote check context for unique checks per build

[tomverin]

Problem

When multiple promote jobs run in parallel (e.g. in a monorepo with consolidated matrix builds), they all write to the same GitHub commit status check. The check context was repox-${GITHUB_REF_NAME}, which is identical for all promote jobs in the same workflow run.

Consequences:

• Only one promote result is visible — the last job to finish overwrites all others
• The check description shows empty or wrong build info (e.g. "Latest promoted build of '' from branch 'refs/pull/64/merge'")
• Downstream scripts that read promote checks (e.g. release workflows) cannot distinguish promoted artifacts per project
• Developers cannot see which capabilities were promoted and their versions

Example: In sonarqube-unification, a consolidated workflow builds 6 capabilities in parallel (entitlements, organizations, template, unified-core, users, integration-bindings). Each runs the promote action with its own BUILD_NAME (e.g. sonarqube-unification-template, sonarqube-unification-entitlements). All 6 write to repox-64/merge and only one survives.

Solution

Make check_context a parameter of github_notify_promotion() and call it twice from promote():

1. repox-${BUILD_NAME}-${GITHUB_REF_NAME} — unique context per build (e.g. repox-sonarqube-unification-template-64/merge)
2. repox-${GITHUB_REF_NAME} — legacy context for backward compatibility (deprecated)

This way each parallel promote job creates its own distinct check, while the old check context is also written so that existing downstream scripts continue to work during a migration period.

Backward compatibility

• Single-build repos: Both checks are written. Scripts matching repox or promote (e.g. sonarqube-unification's resolve.py) continue to work unchanged.
• Multi-build monorepos: Each build gets its own unique check; no more overwrites. The legacy check still gets overwritten (expected — it's deprecated), but the unique checks are preserved.

Testing

• All 31 shellspec tests pass
• Shellcheck passes

[hashicorp-vault-sonar-prod]

BUILD-10457

[Copilot]

Pull request overview

Updates the GitHub commit status “context” used by promote.sh so parallel promote jobs don’t overwrite each other’s status check.

Changes:

• Adds a computed checkContext variable that includes BUILD_NAME
• Uses checkContext when posting the GitHub commit status
• Documents the reason for the new context format in-code

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

SonarQube reviewer guide

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 Dependency risks

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud