Skip to content

Track additional deployment with auto_deploy_on_security enabled

Robert Speicher requested to merge rs-tracking-on-security-ad into master

eb4dba4d - Use auto_deploy_path when fetching complete deployment SHA

5cca0824 - DeploymentTracker uses auto_deploy_path

41e4407c - Track additional deployment with auto_deploy_on_security enabled

When this flag is enabled, the existing functionality will create a new Deployment record on Security mirrors with the given auto-deploy branch. Unfortunately this means that merge requests in the Canonical project won't be notified, because they're in a different project.

We can't simply create another deployment on Canonical, because the auto-deploy ref won't exist on that project. To work around this, we create a deployment in the Canonical project with master as the ref.

201ade50 - Account for a deploy of a legitimate security release

During a security release, we can't create a Canonical deployment of a SHA that only exists in Security, so we now check that the commit exists before trying to create a deployment for it.

Related to gitlab-com/gl-infra/delivery#1031 (closed)

Merge request reports