Nice-to-have: Release-Tools should indicate to me desired number of Packages to be published
Proposal
Over the course of time, Packages that are made by Distribution is ever changing. Mostly due to changes to EOL policies with various OS's, but also because some packages, specifically CentOS7, are reused with other package management OS's such as Scientific Linux, or the addition of new OS's. Currently there's no cohesive connection between release-tools and what Distribution builds, which makes validation of how many packages we publish a manual process. Over time, we started by validating this manually, and we used to list each package name to expect for manual comparison. This is cumbersome and becomes out of date in a matter of just a few weeks. Most recently we changed to simply counting packages, so we modified our release procedure to instruct ourselves on how to do such. This still requires manual work and is error prone and questionable because we in Delivery are not entirely connected to the "why" portion. Let's see if we can release ourselves from this and put this work inside of release-tools.
Solutions?
- Release tools, during the publish stage, can count how many jobs it's hit the play button for, and with special logic, indicate to us how many packages are expected.
- Release tools, could wait until the publish step is done, and perform a search on the packages server itself, and report back that all expected packages are available
- ...