|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I completely agree. I started using Jenkins Friday. On Friday my goal was to get Jenkins working with 1 project. That one project has 2 dependencies on other projects, one of which is dependent on the other. So a simple linear relationship. It's shocking to me that on the first day of using Jenkins I already needed to extend the functionality of it just to have Jenkins be dependent on another project.
Navigating plugins can be a daunting task, especially when you're brand new to a tool. Which ones are good? Which ones are waay too complicated? Which one might break Jenkins? Who knows?
At the very least Jenkins needs something out of the box to support dependencies. Some base functionality, since I just can't imagine that organizations at some point aren't going to need a project that has dependencies on other projects. I wound up installing Copy Artifact, and that works fine. Why can't it, or some other plugin made for dependencies be included in Jenkins?
The OP is right though. There's far more complex dependency use cases that need to be addressed. Dependencies are simply a wide spread need that should come in the box.