![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
delivery-pipeline |
|
Created:
|
20/Mar/14 9:09 PM
|
|
Description:
|
I am just getting started learning about building Delivery Pipelines using this plugin, but I really like it so far.
However, we have a lot of maven projects that build shared libraries. These shared libraries contribute to most of our other top level projects (web applications).
I want to create a pipeline view for each of web application projects since they are each unique and will have unique downstream delivery pipeline phases (deploy to dev, test, deploy to stage, test, deliver). But if select the WAR project as the initial project for my pipeline, it doesn't show the implicit upstream dependencies and I'd love to see which ones of those contributed to the "kick-off" of my WAR project.
The beauty of Maven with Jenkins is that it can implicitly trigger builds without having to manually configure the relationships. It would be nice to see pipeline views take advantage of the implicit Maven relationships.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Jeff VIncent
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
