~virtustom/ubuntu-docker-images/+git/utils:feature-a

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

2211442... by Tomáš Virtus on 2022-03-04

feature a

b407383... by Athos Ribeiro on 2022-02-04

Add script to pull snap squashfs artifacts from LP

Signed-off-by: Athos Ribeiro <email address hidden>

af73524... by Athos Ribeiro on 2022-01-20

Add Dockerfile to run image tagger

This patch adds a Dockerfile which installs all needed dependencies to
run the image tagger. This should also serve as documentation on how to
properly set one's environment to run the image tagger scripts.

Signed-off-by: Athos Ribeiro <email address hidden>

7d0db42... by Sergio Durigan Junior on 2021-11-03

Improve error reporting when tagging

It's currently somewhat cumbersome to diagnose when an error happens
during the multi-arch tagging process. I thought I'd improve this by
saving the (possible) error message returned by the registry in a file
and then displaying it if appropriate.

A simpler option would be to pass "-o /dev/stderr" when invoking curl,
but I'm afraid that we might pollute the output with some unforseen
string being returned by the registry.

Signed-off-by: Sergio Durigan Junior <email address hidden>

6e96720... by Tomáš Virtus on 2021-09-27

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://snapcraft.io/docs/release-management

e8797c0... by Tomáš Virtus on 2021-09-23

tag-images.sh: Tag devel release with XX.YY_edge

We do not want to tag devel releases with stable/beta/candidate tags
(so called inherited tags), but we still want XX.YY_edge implict tag
alongside XX.YY and $release_name tags.

37c304a... by Tomáš Virtus on 2021-09-23

tag-images.sh: Fix checks for existing tags

Checks for existing tags currently use word regex. E.g. to check
whether tag 'impish' exists, we do

  grep -Fwq impish <<< "${IMAGE_TAGS[@]}"

But that also matches impish-21.10_edge tag, because '-' (dash) is a
word boundary.

Change the checks to match regex on full lines.

dce5193... by Athos Ribeiro on 2021-08-02

Fix Go manifest builder

github.com/golang/pkgsite, the upstream for pkg.go.dev, had its frontend
refactored since the current golang-manifest-builder.py was written.
This patch adjusts the script to properly parse the new package unit
page to fetch the package repository.

Signed-off-by: Athos Ribeiro <email address hidden>

6a46571... by Sergio Durigan Junior on 2021-07-26

tag-images.sh: Set DRY_RUN=0

This is needed because "-eq" doesn't work otherwise, which will lead
to errors when invoking the script without --dry-run.

Signed-off-by: Sergio Durigan Junior <email address hidden>

7469a2d... by Thomas Bechtold on 2021-07-15

tag-images.sh: add --tag-filter to tag only a specific _edge tag

Currently the tag-images.sh script interates over all the given _edge
tags from the given images in the given namespace and adds the needed
tags (eg. _beta, _candidate or _stable). That's not always
wanted. Eg. when using the script in a CI pipeline where a job does
only update a specific image (eg. the "impish-21.10_edge" tagged
image), the script should only add the additional tags to that tagged
image.
With the new parameter, that's possible.
Assuming there are multiple _edge tags (eg. "impish-21.10_edge" and
"hirsute-21.04_edge") for a given image and --tag-filter is set to
"impish", the script will now only add the extra tags to the image
that is tagged with "impish-21.10_edge" .

Note: --tag-filter only works when the given IMAGE is a base
image (means that IMAGE must be "ubuntu").