Signing stage failed upon retry: add multi-attempt resilience to internal build
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
In the 1.18.9 release, we hit a problem during the signing stage/job.
https://dev.azure.com/dnceng/internal/_build/results?buildId=2061695&view=logs&j=d911440c-2ed3-5a8b-f345-d20fc603def5&t=b1b7a38e-7453-5487-735d-753ba9208bb1&l=84
##[error]Artifact SigningDetails already exists for build 2061695.
We should include the attempt number (System.JobAttempt, System.StageAttempt?) when possible.
The workaround is to trigger an entirely new build, which takes more time than a retry.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the signing stage/job and the linked internal build log for build 2061695. Check how System.JobAttempt and System.StageAttempt are available during retries and how Artifact SigningDetails is created. Done means a retried signing attempt avoids the duplicate-artifact failure without requiring a new build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100