Add suffix customization options for jobs with name collisions in pipeline execution policy pipelines
Proposal
Related issue: #473189 (closed)
Related merge request: !159858 (merged)
An ultimate customer created a ticket (Internal Link) to describe their need for further customization to modify the suffix that gets appended to jobs with name collisions.
Their description of what they would need is as follows:
We are trying to test stuff with our pipeline execution policies. We have them linked to secure policy frameworks. We have a branching and testing structure setup so that they are tested on projects. What we have found though is that, because our PEP's CI file all have the same job names, that if we attach multiple of them to the same project that the job names become “<JOB_NAME_HERE>-policy-51”. We would prefer not to rename the job names due to some technical items around them. So to be clear, changing my CI file's job names to all be “<JOB_NAME_HERE>-max-policy” is not ideal. What would be preferred is if in the running pipeline, or wherever it is injecting the “-policy-51” string, that it instead injects a custom string like “-max-policy”.
If this is already possible to configure or modify, I'm not finding a way to do it. Please let me know and I will update the documentation accordingly if one exists. Thank you!