Make auto-update pipeline jobs identifiable by title and make failure more accurate (build "number")
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
This is not very browsable:
You can't tell, but these have different origin-job branches, and the failures are because go-images doesn't have a slot for those branches to fit in. All these jobs are working properly.
We can use ##vso[build.updatebuildnumber]build number to change the title that shows up on that list to clarify the origin branch, and be more careful about how go-infra's dockerupdatepr cmd handles specific error conditions to make this job list much better.
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 Azure Pipelines build logging command linked in the issue and the go-infra dockerupdatepr command. Trace how origin-job branches and go-images slot failures are represented, then verify that build titles identify the origin branch and that failure reporting distinguishes unavailable slots from actual job failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, docker, go
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100