Hi All
We have a job today that generate's 0-n number of http calls to start various different builds on the same job. I wanted to avoid doing that. Playing with different options i found that i can add a build step to trigger builds on another project and add a parameter factory which can launch a job for every properties file found. This will work great for us. I can change the scripts to generate properties file instead of http calls. However one thing that is missing is being able to see the downstream view or build graph.
So i was curious if i am missing some thing in how i am configuring my job that i do not see the downstream view or if there is a way to use post build action for downstream job trigger and achieve what i mentioned above. I did notice that if i enable the current job to be blocking on the builds it calls then the build graph shows up but not the downstream job. However i want to avoid making this job a blocking job.