-
Bug
-
Resolution: Postponed
-
Minor
-
None
Use case:
Multijob 1 is calling Job X twice, where each call is a different set of parameters.
Issue:
Each repeat of Job X looks the same in the list of the multijob. I would like to be able to give them a label that specifies more detail about why this job is called multiple times. Current workaround is to create a new phase with a name, but you lose concurrency.
Request:
I would like to be able to give the downstream job a label in the Multijob pipeline.