Skip to content

Create a trigger update branch

DJ Mountney requested to merge create-update-trigger-branch into master

What does this MR do?

Keeps a separate branch in sync with master that we can trigger test pipelines against from other projects.

We use a separate branch, so that failures aren't raised as broken master issues.

  • This branch should be updated everytime there is a push to master
  • We can additionally schedule a daily pipeline so that if there is an failure during the push pipeline (network, or git locking), we don't always need to wait for the next push to restore.

The alternative (which we use for some of the projects), is to fork this chart to a mirror project, and runner triggers there. For the moment I think that is less ideal as it requires us to setup additional kubernetes clusters.

Related issues

Part of #2824 (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

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 omnibus-gitlab opened
Edited by DJ Mountney

Merge request reports