Skip to content

Move QA image release to a different stage

Balasankar 'Balu' C requested to merge move-qa-release-to-different-stage into master

What does this MR do?

We are moving the publishing of QA Docker images from omnibus-gitlab pipelines to gitlab|gitlab-foss pipelines in gitlab!105177 (merged). The way release of omnibus-gitlab packages and docker images is that publish jobs in the tag pipeline are manual jobs. At the time of publish, release-tools will run all the manual jobs present in the specified stages. For omnibus-gitlab, the stages are specified here. By moving QA release job to a different stage, we prevent release-tools from automatically playing it, while retaining the ability to play it ourselves if the job in GitLab rails pipeline fails for some reason.

Also, we have to mark it to be allowed to fail so that it does not block the release pipeline. This is because ability of a manual job to block a pipeline is tied to allow_failure attribute.

Related issues

Closes: #7333 (closed)

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion

Required

  • Merge Request Title, and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com
  • Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks
  • trigger-package has a green pipeline running against latest commit

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Tests added
  • Integration tests added to GitLab QA
  • Equivalent MR/issue for the GitLab Chart opened
Edited by Robert Marshall

Merge request reports