Draft: Bug 41292 - Autopublish CI container images

Merge Info

Related Issues

• #41292 (closed)

Backporting

Timeline

• Immediate: patchset needed as soon as possible
• Next Minor Stable Release: patchset that needs to be verified in nightly before backport
• Eventually: patchset that needs to be verified in alpha before backport
• No Backport (preferred): patchset for the next major stable

Merging

• Merge to tor-browser - !fixups to tor-browser-specific commits, new features, security backports
• Merge to base-browser - !fixups to base-browser-specific commits, new features to be shared with mullvad-browser, and security backports

Issue Tracking

• Link resolved issues with appropriate Release Prep issue for changelog generation

Change Description

I have implemented a CI job that build and publishes the base CI image to our registry. This is convenient whenever we need to change that image, because it will get published on merge. Also, I'd like to regurlarly re-build that image and re-publish it so it stays up to date with the dependencies cc @pierov because this needs to be setup in by a maintainer.

I also did some housekeeping to keep the Containerfile aligned with the style and practices of the Containerfiles in https://gitlab.torproject.org/tpo/tpa/base-images.

@lavamind Would you mind taking a look at the changes? I heavily based myself off of https://gitlab.torproject.org/tpo/tpa/base-images/-/blob/main/.gitlab-ci.yml :)

How Tested

No further testing required. See previous pipeline runs for development tests.