Proposed Feature

Add a push-tag or push-image step for images and a push-tag step for repositories

Edit(@krancour): Further discussion in this thread will be limited to images. Pushing git tags has been broken out to a separate issue. See #5737.

Motivation

This would allow to release tags only for versions that have been properly tested (promoted in a testing environment), the following pattern :

You can also look at the following reddit discussion

Two warehouses:

• A, which subscribe using the NewestBuild strategy
• B, which subscribe using the SemVer strategy

1. Artifact (git or image) is pulled from warehouse A using the NewestBuild strategy (ex: reference fe80c...)
2. Artifact is promoted to a testing environment
3. Artifact is tested with an AnalysisRun
4. If the AnalysisRun is valid, push a tag to git repo/image repo (ex: reference 1.0.2)
5. That artifact (1.0.2) is retrieved using the SemVer stategy
6. Artifact is promoted to as staging environment
7. ...
8. Artifact is promoted to a production environment

Suggested Implementation

A couple important points :

• Make sure that there is a way to specify and/or automatically determine and set what will be the (name) of the tag that will be pushed to git/image registry.
• Make sure that the push-tag can happen after an AnalysisRun.
• For image registries, we could create either a push-image or push-tag but the most important bit is the ability to tag the image that has been tested.