In GitLab CI, we solve this by using the pipeline number in the tag. They're always in order, and it is available as a variable anywhere in the pipeline.
We use `git rev-list --count HEAD` on master, which basically gives you the number of commits.
we do this in addition to the sha. best of both worlds!
That is a great idea!
I do this as well — "Upgrade from image b1257 to b1262". As a bonus, you can tell every tag that doesn't fit the b-then-a-build-number naming convention hasn't come from CI.
Oh, I need to start doing that, that's really clever.
I do the same thing with Azure DevOps, as pipelines there also have an incrementing integer ID
Neat! We're using gitlab too and I never thought about this.