Skip to content

Fixes for version change, tag pipelines and parent pipeline results

What does this MR do and why?

Describe in detail what your merge request does and why.

This is a follow-up of !880 (merged)

With this MR:

  1. We do not run the generate stage jobs on version update and tag pipelines.
  2. Wait for child pipeline to finish before registering the result of parent pipeline.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

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

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Sanad Liaquat

Merge request reports