Skip to content

Do not create monthly pipeline in dry-run mode

Dat Tang requested to merge dattang/do-not-create-monthly-pipeline-in-dry-run-mode into master

What does this MR do and why?

Describe in detail what your merge request does and why.

Content

  • Do not create monthly pipeline in dry-run mode

When being in dry-run mode, do not call the API to create a new monthly release pipeline, but return a fake pipeline. This allows us to test generating a monthly release issue in dry-mode without creating a new pipeline.

This implementation learns from the security pipeline.

This is done to unblock @madelacruz when testing the monthly release automation.

Ref: gitlab-com/gl-infra/delivery#20510 (closed)

Testing

  • Manually change monthly_release_pipeline? method to return true
  • Run
SLACK_TEST='true' TEST='true' LOG_LEVEL=trace bundle exec rake "release:issue["17.4.0"]"

  • It should print out the whole monthly release issue, with many lines mentioning the fake pipeline, like this:

      - [ ] Start the `monthly_release_finalize:start` job in the monthly release pipeline: https://example.com/foo/bar/-/pipelines/1
Edited by Dat Tang

Merge request reports