Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ctrl_mpexec, pipe_base
-
Labels:
-
Story Points:1
-
Epic Link:
-
Sprint:AP S21-6 (May)
-
Team:Alert Production
-
Urgent?:No
Description
Top-level tasks in a pipeline are given their default name, rather than the name of their label in the pipeline. This means that there may be multiple tasks in a pipeline with the same name, something the original Task framework tries to avoid, and makes task metadata more difficult to interpret.
Modify the pipeline generation code to name top-level tasks according to their label.
All looks good! I'm glad you caught this in the metadata, as I'd bet not using the label for the task name was also doing the wrong thing in other contexts.