Dynamic triggered subprojects not showing in the graph

[Bill Matzen]

We've got a Delivery Pipeline whose Initial Job is triggered by a source control commit, and dynamically triggers other CI jobs based on the specifics of the commit details.  So one time it might trigger CI job A, another time CI job B, another time maybe both or neither.  In any case, these jobs that are being triggered aren't showing up in the graph. In the build history, looking at the Initial Job details, I do see the subproject listed ("Subprojects triggered but not blocked for..."), so I know there's a connection there.  I'm just not sure how Delivery Pipeline walks these relationships, and why it might be missing these.  I have another Delivery Pipeline (with a different Initial Job) that does show the downstream projects, and so I compared the configuration of the two Initial Jobs to see what is different.  While they both use "Trigger/call builds on other projects", in one case (downstream shows properly in the graph) the "Projects to build" is hard coded. In the other case (downstream doesn't show in the graph), "Projects to build" contains a variable ("${JobsToRun}") which is resolved at runtime. Also in this second case, it is triggered as a conditional step (so that "Trigger/call builds on other projects" only runs if ${JobsToRun} is not empty).  I'd love to get this working, as it would be a great way to show a diagram of each code commit and the CI jobs that get kicked off.

Thanks,
Bill

[Shanish]

+1

Using a variable for "Project to Build", which populate in runtime.

בתאריך יום רביעי, 12 באוקטובר 2016 בשעה 18:23:46 UTC+3, מאת Bill Matzen: