Investigate public CI job times and look for improvements
Open
Nobody has claimed this yet.
Test
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
CI takes a decent amount of time, we may be able to improve it:
- Check queue times of 1ES/dnceng pools vs. AzDO hosted agents.
- Look at Windows vs. Linux jobs.
- Add tag to our platforms to show up better in the build analysis tab for summaries: https://dev.azure.com/dnceng/public/_build?definitionId=1099&view=ms.vss-pipelineanalytics-web.new-build-definition-pipeline-analytics-view-cardmetrics
- Look for trends over time or between release branches and the main branch.
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 public Azure DevOps build analytics link in the issue. Compare queue times for 1ES/dnceng pools and AzDO hosted agents, Windows versus Linux jobs, and release branches versus main, then review whether platform tags improve build-analysis summaries. Done means the trends and actionable improvement opportunities are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100