-
Bug
-
Resolution: Unresolved
-
Major
-
None
when using a job that is a generic one (e.g. deployment) while defined in the pipeline to deploy to different instances (different parameters) always only the latest build of this job is shown instead of the single instances that where executed.
Voting for this one. Dynamic downstream jobs are essential and invaluable in a complex CI environment. I know that on initial rendering of the view there's no way to know what the downstream job is if it contains a variable. However, once that job has run, there is a specific downstream job which could be added to the pipeline view...no??
This is a show-stopper for me so a fix would be greatly appreciated!