Skip to content

Always sync to the artifact registry when pipelines run on dev

John Jarvis requested to merge jarv/sync-non-tagged into master

What does this MR do?

For https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/17161

Registry has a different release process for the SaaS than autdeploy builds. A version bump is done on a branch (e.g. !1269 (merged)), then uploaded to the dev registry on the build server (e.g. https://dev.gitlab.org/gitlab/charts/components/images/-/pipelines/269073 )

Previously, we had a conditional to only sync to the artifact registry on tagged builds on dev, which doesn't cover us here resulting in an image that is pushed to dev, but not the artifact registry.

Given we only mirror protected branches, with this change we will sync not only tagged builds, but builds on the following branches:

*-auto-deploy-*
*-stable
*-stable-ee
master

Related issues

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

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Integration tests added to GitLab QA
  • The impact any change in container size has should be evaluated
Edited by John Jarvis

Merge request reports