Skip to content

Add sync_remotes to security release pipeline

Steve Abrams requested to merge delivery19433-sync-finalize into master

What does this MR do and why?

We are automating the security release final steps with a pipeline. This MR adds the security_release_finalize:sync_remotes job to the security_release:finalize stage.

This job will run the rake task to sync the default branches for security projects after the security release has been published.

We also update the Security::SyncRemotesService to send a success or failure slack notification to f_upcoming_release upon completion of the job. If the job fails, instructions are logged to the job output for how to run the sync using chatops.

Testing

I pushed the branch to the ops instance, commenting out all other security_release_finalize jobs and ran a pipeline targeting the feature branch with TEST: true and SECURITY_RELEASE_PIPELINE: prepare as variables.

The pipeline successfully ran a dry-run of the sync: https://ops.gitlab.net/gitlab-org/release/tools/-/pipelines/2085974

Author Check-list

  • [-] Has documentation been updated?

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

Edited by Steve Abrams

Merge request reports