GitLab/pipeline conversion

= Steps for migrating a pipelinelib repo =


 * Read the entry for the repo in integration/config/zuul/layout.yaml.
 * If it has stages other than,  ,  , or  , then get help from Release Engineering. Otherwise proceed.
 * Use pipeline-to-gitlab to convert  into  :
 * Perform any desired cleanup on the generated file, such as renaming jobs and stages, removing redundant jobs, etc.
 * Commit and push new  to GitLab.

= Differences between Gerrit pipelines and Gitlab CI pipelines =

= Changes to publishing container images =

If your project intends to publish an image to be used in production, it must be built using Kokkuri and Blubber and the project added to the gitlab-trusted-runners project.

Pipelinelib published images with a timestamped tag. Kokkuri uses the SHA1 of the commit that triggered the pipeline.

Registry paths for images are different when published from GitLab.

In the simplest terms, if your GitLab repo is at, you can publish container images under   and below.

You will need to update image paths in the places where you use them (most likely in the operations/deployment-charts repo). Use CodeSearch to search for the old image name.

You may want to change when an image is published (e.g., so that it's not every time there's a merge into the default branch). For example, you could change the rules in  so that image build/publish only happens when a commit is tagged.