Skip to content

Add test cases to verify fork MR merge train pipeline

What does this MR do and why?

Add test cases to verify fork MR master branch and merge train pipeline

Related: #34040 (closed)

The test cases being added in the MR:

  1. merge train pipeline for MR targeting master
  2. merge train pipeline for a MR targeting stable branch
  3. merged results pipeline created from a fork project - source branch == master
  4. merged results pipeline created from a fork project - source branch ~= feature branch
  5. merge train pipeline for 3 and 4 above.
  6. merge train pipeline for expedited MR.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

With this change, I was able to validate the pipeline changes in !159378 (merged). It caught an error by failing the following spec:

Screenshot_2024-07-22_at_6.54.23_PM

How to set up and validate locally

The test can run locally with bundle exec rspec spec/dot_gitlab_ci/job_dependency_spec.rb. Please note the entire test takes about 8 minutes to run so it remains quarantined in CI.

Edited by Jennifer Li

Merge request reports

Loading