Skip to content

WIP: Add docker image as build artifacts

What does this MR do?

This MR it's the first step toward implementing Automate push/pull of docker image artifacts.

The pipeline artifacts syntax has been extended allowing a new key image which identify the local docker tag that must be pushed as an artifact to the registry.

If such artifact has been configured and pushed to the repository then it will be displayed on the job details page.

In order to avoid image collisions, the artifact image is named $registry_url:$user/$project/pipeline:$build_id

Next steps

  • extending artifacts expirations to docker image
  • allow to customize final docker image name and tag
  • allow to use previously built image in subsequent jobs
  • artifacts uploading via API call instead of naming convention (not sure if really needed)

cc: @ayufan @markpundsack

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

Please see #31542 (moved)

Screenshots (if relevant)

before after

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

#31542 (moved)

Edited by Kamil Trzcińśki

Merge request reports