Tags, Releases and auto-deploy commit churn
Starting March 17th a lot of tags of the form
<gitlab-version>.timestamp+commit have been added, at a rate of a few each day. This is in and of itself not a problem, but it does make it more difficult to find the correct tag for each release of the chart, and disables the tag-list as a list of chart releases. It also adds a lot of cognitive overhead when browsing the history of the repository due to the large amount of leaf commits.
Steps to reproduce
Check https://gitlab.com/gitlab-org/charts/gitlab/-/tags - it has 21 pages, of which 11 are filled with auto-deploy tags.
The tag list is churned a lot
There's a few ways to go, neither of which exclude the other options:
- Create actual Releases in Gitlab for each chart release, so that https://gitlab.com/gitlab-org/charts/gitlab/-/releases can be used instead as an active list of releases, with links to the relevant tags. This also allows for Release artifacts & release notes (e.g. changelog per release), which would allow for better discoverability for each release
- Link to the tag in the changelogs
- Clean-up all but the latest X auto-deploy tags (added benefit of allowing clean-up of the repository, removing 'dangling' HEADs
- Change from tagging all autodeploy-commits to merging these commits onto a single branch, merged with e.g.
--strategy=ourseffectively ignoring the changes of the previous head. Currently, the commits of the tags already contain the information of the tag, so this would only incur the penalty of having to search the history instead of having to search the tags.
- Chart: (tagged version | branch | hash
git rev-parse HEAD) all of 'em
- Platform: N/A
- Kubernetes: N/A
- Helm: N/A