Skip to content

Move up release-environments stage in CI

What does this MR do and why?

Currently, release-environments stage is last in the security/gitlab stable branch pipeline, like so: https://gitlab.com/gitlab-org/security/gitlab/-/pipelines/1855702035

However, the bridge job only has one dependency, compile-production-assets. This means we can expedite the job to a much earlier place in the pipeline.

The downstream pipeline job also needs the qa image, so I added the build-qa-image job as a dependency to the bridge job.

Since the next jobs graphql-schema-dump and rspec-all frontend_fixture don't depend on the start-release-environments-security-pipeline, it won't wait until the previous stage job is complete to start, therefore making the start-release-environments-security-pipeline bridge job run in parallel as the rest of the pipeline.

References

Edited by Jenny Kim

Merge request reports

Loading