Pipeline health: Check version numbers
Open
Nobody has claimed this yet.
automation
- Dominant language
- MDX
- Stars
- 98
- Forks
- 298
- Avg merge
- 14h 38m
- Merged PRs (30d)
- 38
Description
It's quite frequent to find that the pipeline version numbers on dev look stable. This is bad as people running new code will have reports saying that they are running the previous stable version.
We should be able to check for this on the pipeline health page and throw a failure there.
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 at the pipeline health page identified in the issue and trace how its existing health checks report failures. Determine how version numbers on dev should be compared with the stable versions, then verify that a matching version produces a visible failure on the page.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100