-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Enhancement] Add extra docker tags specifically for different builds #1762
Labels
Comments
Would be great to get this done in the 2.0 timeframe. |
[Triage] For the tag with build number in it, we could activate it when there will be a release candidate coming to avoid too many images. |
Update 20220609: |
This is complete and can be closed for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have seen an issue today were IM committed a change during code freeze time:
opensearch-project/index-management#311
This triggers a new build in jenkins, although we have separate links for tarball, docker only has one tag
1.3.0
and get overwritten.I propose we have separate tags for docker based on builds.
Ex:
latest
: always pointing latest1.3.0
: pointing to the latest version in 1.3.01.3.0.1234
: pointing to the version with build number 1234 in 1.3.0This way we can for sure lock all the artifacts to a specific version and will not overwrite without backups.
Thanks.
The text was updated successfully, but these errors were encountered: