Skip to content

Fix auto deploy pipeline

John Skarbek requested to merge jts/fix-auto-deploy-pipeline into master

What does this MR do?

Due to triggering pipelines operating differernt between the use of CI_JOB_TOKEN and a Trigger Token as discussed here: gitlab-org/gitlab#212784 (closed), the changes in this MR allow for deployer to trigger precisely what we need. While still allowing a pipeline that is triggered via a trigger token to work just as well.

In order to prevent as many jobs as possible from running, we default the AUTO_DEPLOY variable to false, and all jobs utilize this to determine whether or not that should be created as part of a pipeline. The opposite remains true for auto-deploy pipelines where this variable is already properly sent to the trigger.

Dry run results

There should be none. This is a change to the way the CI mechanism works.


Edited by John Skarbek

Merge request reports

Loading