In comparison view, compute who's responsible for rebuilds
Nobody has claimed this yet.
- Dominant language
- PLpgSQL
- Stars
- 1.6k
- Forks
- 358
- Avg merge
- 20h 30m
- Merged PRs (30d)
- 27
Description
This could be slightly tricky to implement, but I think we have all the information necessary for it. Basically, it seems like there could be another tab in a comparison that accounts for which hashes changed from the previous run, sorted by the number of dependent hashes they changed (ideally with some way to see which dependencies were affected). This would make it much clearer why something caused a mass rebuild, and could also make it obvious that certain packages cause mass rebuilds on Darwin and not Linux or vice versa.
Contributor guide
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 by locating the comparison view and the data exposed for the previous run, then determine how changed hashes and dependent hashes are represented. Define the additional comparison tab, its dependency details, and sorting by affected dependents; done means it explains mass rebuild causes and distinguishes platform-specific effects.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100