Skip to content
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.

:latest tag management #16

Open
euank opened this issue Jan 18, 2018 · 2 comments
Open

:latest tag management #16

euank opened this issue Jan 18, 2018 · 2 comments

Comments

@euank
Copy link
Contributor

euank commented Jan 18, 2018

I believe in the past this repository had a manually triggered Jenkins job which would mirror master to latest as a sort of 'promotion' / 'release'.
Do you recall if that was the case and if there were any more details there @colhom?

We should likely set something like that up agian since latest is quite out of date at this point.

Note that we shouldn't mirror master quite yet since #15 should be resolved first to avoid regressions on latest.

@whereisaaron
Copy link

When an image it promoted/release to 'latest', can it also be tagged with a version? With version tags, users can pull version tagged images that won't be subject to potentially breaking changes like #15.

I suggest tagging them with the version of awscli they contain, since this the only purpose of the container. But really, any version tag to maintain an invariant image would be enormously helpful.

@euank
Copy link
Contributor Author

euank commented Jan 23, 2018

I agree that immutable versioned tags should be published as well.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants