MR Artifact Promotion
Hummingbird builds and tests an RPM artifact during a merge request (MR). After merge, the push pipeline promotes that same artifact to release without building it again. The tested image digest is therefore the one consumed by the release pipeline. This flow is in use for RPMs; container promotion is separate work.
RPM flow
flowchart LR
A["MR build and tests<br/>source B, digest D"] --> B["Merge to main<br/>merge commit M"]
B --> C["Promotion PipelineRun<br/>finds passed MR Snapshot"]
C --> D["Component Snapshot<br/>same B and D"]
D --> E["Integration Service<br/>creates Release"]
E --> F["Release Service<br/>checks and publishes RPMs"]
- The promotion PipelineRun reads the two parents of merge commit
Mfrom Git. The second parent,B, is the tested MR head. The pipeline requires a two-parent merge commit; it does not need an MR number or GitLab API lookup. - The artifact lookup Task finds a passed MR Component Snapshot for
Bin live Konflux or KubeArchive. It verifies the linked build PipelineRun, target branch, source repository (including forks), test result, and image digestD. A passed/testor/retestbuild is eligible when the Snapshot and build record the same PaC event. Multiple passed Snapshots for one commit are normal — a/testor/retestrun creates another — and while RPM builds are non-reproducible (HUM-9785) their image digests may differ. Promotion uses the newest eligible Snapshot. - The promotion Task rechecks that evidence and creates a single-Component,
push-event Snapshot with the same source revision
Band image digestD. It recordsM, the source MR Snapshot and build, and the promotion PipelineRun. The Snapshot’stest.appstudio.openshift.io/pipelinerunstarttimeis the promotion PipelineRun’s start time in epoch milliseconds. - Integration Service processes the Component Snapshot and creates the automatic Release. Release Service runs the existing Conforma, signing, and publication checks. The promotion PipelineRun creates no Release or new build attestation. The released RPMs come from the tested OCI artifact.
The promotion Task checks that no IntegrationTestScenario would run on the new Snapshot, so this handoff does not repeat the MR tests. RPM promotion does not create an override Snapshot or update the Global Candidate List: RPMs do not use it for group tests.
For RPM operations, including push pipeline overrides, verifying a promotion, and recovery, see the RPM MR artifact promotion guide.
Ordering and recovery
Before creating a Snapshot, promotion checks whether a newer merge changed the same package. An unrelated package merge does not block it. The Component Snapshot start-time annotation also lets Integration Service apply its existing push Snapshot ordering check. These are the same ordering controls used by push builds; they do not promise a global serial release queue.
A retry uses the same Snapshot name derived from the Component and M. It
reuses an existing live Snapshot only when its identity, digest, provenance,
and original promotion start time match. It never replaces an archived Snapshot
or creates a second one to retry a failed Release.
Promotion stops if required MR evidence is unavailable in both live Konflux and KubeArchive, the source image has expired, a test failed, or a matching IntegrationTestScenario would run. If promotion cannot use the tested artifact, recovery requires an explicit new build and required tests. A failed automatic Release is retried through the release workflow. MR Snapshot retention and Quay image retention are independent; the source image must remain available through merge and release retries.
Relationship to RHEL on Konflux
RHEL on Konflux (RoK) also reuses an MR-tested RPM after merge. Its current MR artifact is an imported Koji draft build, and its release continues through Brew and Errata. Hummingbird creates its RPM artifact in Konflux and uses a Component Snapshot and automatic Release to publish to Pulp. The shared design point is release of the tested artifact without a post-merge rebuild; artifact storage and publication differ.
Container promotion
Container promotion remains in the container epic. Its group tests use the Global Candidate List, so it needs a separate, non-releasing override Snapshot as well as the Component Snapshot used for release. The container path must establish a no-retest handoff and prevent an older override from replacing a newer candidate before rollout.
MR container images also need tag-level expiry instead of the embedded
quay.expires-after label: that label would follow a promoted container image
into release. A set-tag-expiry task should expire the MR tag through Quay
without changing the image; its retention window, Quay access, and Conforma
trust remain open design questions. RPM releases publish the RPMs inside the
OCI artifact, so that label does not appear on released RPMs. The MR source
image must still survive until the RPM release completes.
For Task inputs, permissions, and failure handling, see the Hummingbird tools Task reference.