Merge ~virtustom/ubuntu-docker-images/+git/utils:main into ~ubuntu-docker-images/ubuntu-docker-images/+git/utils:main
Status: | Merged |
---|---|
Merged at revision: | 6e96720a18a891cbc5b00c61225f8168ba8d398a |
Proposed branch: | ~virtustom/ubuntu-docker-images/+git/utils:main |
Merge into: | ~ubuntu-docker-images/ubuntu-docker-images/+git/utils:main |
Diff against target: |
62 lines (+42/-1) 1 file modified
tag-images.sh (+42/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Sergio Durigan Junior | Approve | ||
Thomas Bechtold | Approve | ||
Canonical Server | Pending | ||
Review via email:
|
Commit message
tag-images.sh: Tag latest/edge shorthand tags
Currently we don't update latest/edge shorthand tags. There's a plan
to implement tagging similar to snaps[1]. In the meantime, update
latest/edge tags according to the following rules:
If the repository is 'lts',
set both 'latest' and 'edge' tags to the latest LTS release.
If the repository is 'ubuntu',
set 'latest' tag to the latest stable release and
set 'edge' tag to the devel release.
[1] https:/
Description of the change
JIRA issue: https:/
Valentin has more plans with regard to tagging channels similar to snaps, but he agreed that in the meantime the rules for tagging edge/latest are fine. I think it's not pretty (opinions welcome!).
I've tested it in my personal Docker Hub repository (https:/
21.10
impish
impish-21.10_edge
20.04_edge
20.04_candidate
20.04_beta
20.04_stable
20.04
focal-20.04_edge
18.04_stable
bionic
bionic-18.04_edge
hirsute-21.04_edge
and command line (code changed to accept ubuvirtus):
./tag-images.sh -r docker -n ubuvirtus -- ubuntu
When I change the added comparison to check for 'ubuvirtus' instead of 'ubuntu', the output is:
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/edge (source tag: impish-21.10_edge) (on docker)
I: Not adding stable/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/latest (source tag: hirsute-21.04_edge) (on docker)
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
When I change the added comparison to check for 'ubuvirtus' instead of 'lts', the output is:
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/
I: Invoking multi-arch tagger for ubuvirtus/latest (source tag: focal-20.04_edge) (on docker)
I: Invoking multi-arch tagger for ubuvirtus/edge (source tag: focal-20.04_edge) (on docker)
I: Invoking multi-arch tagger for ubuvirtus/
I: Not adding stable/
Thanks for the MP, Tomasz.
I'm leaving a few comments regarding style, and that's the only reason why I'm marking this as "Needs Fixing". But otherwise, I don't have anything particular to add to the code. I just would like to point out that this code is relying heavily on "distro-info", so you will need to stay on top of it and make sure that it's up-to-date as soon as a new release is out.
Thanks.