Apply workflow:name value to downstream multi-project pipelines
Release notes
Apply the value of workflow:name (if value provided) to the display of downstream/multi-project pipelines in the upstream pipeline view
Problem to solve
Currently, multi-project pipelines display the name of the target project. This can be confusing if setting up multiple triggers for the same project. The additions of the workflow:name keyword is great for assigning a name that shows up when viewed from the downstream project. However, this does not show up when viewing the upstream pipeline.
My current use case is that I am working on using trigger
to launch a multi-project downstream pipeline to be able to test changes to our CICD templates before releasing. I'm setting up multiple trigger jobs to the same project, using variables to control which step in the pipeline I'm testing (eg: QA release vs UAT release). However, both downstream jobs show up as the same name
So, I tried using the workflow:name
keyword to easily differentiate the downstream pipelines.
However, despite the custom name showing up when I go to the downstream pipeline directly ,
it does not show in the upstream's pipeline view.
Proposal
My proposal is to update the view of the downstream pipelines to show the value of workflow:name, if a value is available.
Intended users
Developers, scum master, release managers, maintainers. Basically anyone that regularly works with or views pipelines could use this feature.
Feature Usage Metrics
Unknown
Does this feature require an audit event?
Unknown. This is an extension of the workflow:name keyword, so whatever auditing that feature already requires.