-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
If I have a pipeline job (formerly workflow) Foo, that then triggers another pipeline job Bar, it does not get reflected in the delivery pipeline view. Job Bar is triggered as a build step in my job, for example:
Job Foo:
stage('Building') { println 'Triggering Bar' build 'Bar' }
Job Bar:
node('master') { stage('Child job stage') { println 'Doing stuff in child job' } }
Only the Foo pipeline job and its steps are displayed in the delivery pipeline view:
In this case, both Foo and Bar should have appeared as separate entities on the delivery pipeline view.
martinmine
JENKINS-34040covers the support of visualizing a single pipeline script as a delivery pipeline. I think it makes more sense to add features as we go along. If all possible scenarios would have been expected to be supported, development would still be ongoing and for a foreseeable future.You can select to show multiple pipelines in the same view, but that does not mean that they have any relation as such. Here's an example of a delivery pipeline view showing multiple pipelines in the same view: https://www.slideshare.net/tommysdk/continuous-delivery-of-microservices/33
The most feedback I've got from users using Jenkins pipelines is that the entire pipeline is covered in one definition, therefore we started to implement support for that. I understand your use case and it could possibly be solved. However, with regards to how the piplines and cps executions work it is not as trivial to resolve as for upstream/downstream jobs.