Skip to content

Update MR Merge Train Failure Messages

What does this MR do and why?

This MR updates copy for failure reasons on merge trains so that when MRs are removed from merge trains the failure messages are more informative and provides a link to helpful documentation.

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.

For Workflow:Rules

Before After
Screenshot_2024-07-04_at_1.41.09_PM Screenshot_2024-07-04_at_1.41.27_PM

For Rules(Job Rules)

Before After
Screenshot_2024-07-04_at_1.40.47_PM Screenshot_2024-07-04_at_1.42.05_PM

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Follow the docs to enable merge trains
  2. Make a few MRs on the train with long sleeps
  3. Add another MR to the train with a configuration that won't run. for instance, have the commit message say draft with the rule:
workflow:
  rules:
    - if: $CI_COMMIT_MESSAGE =~ /-draft$/
      when: never
  1. Observe that the other MRs queued on the train were kicked off the train with the message.

Related to #391460

Edited by Vlad Wolanyk

Merge request reports