Use security path in ProjectChangeset (!1252) · Merge requests · GitLab.org / release-tools

Robert Speicher requested to merge rs-changeset-security-path into master Oct 28, 2020

Between auto-deploy commits only being available in the Security mirror, and including security fixes directly into the auto-deploy process, we would fail to create QA issues when one of the referenced commits only existed in the Security mirror.

This change updates the ProjectChangeset class to use the project's security_path, which should allow the verify_refs! check to pass.

The corresponding spec used fixtures with the Canonical path, so we've simply updated them manually.

This should resolve gitlab-com/gl-infra/delivery#841 (comment 436934466) and https://sentry.gitlab.net/gitlab/release-tools/issues/2126821/.

Use security path in ProjectChangeset

Merge request reports