> On 09 Oct 2015, at 15:54, Daniel Beck <[email protected]> wrote: > > > On 09.10.2015, at 10:19, Victor Martinez <[email protected]> > wrote: > >> In order to support the workflow plugin those dependent modules should be >> part of every plugin? If that's the case, is there any planning to add those >> features as part of the jenkins core? I like the idea of reducing the >> dependencies between plugins in order to use the Configuration as Code >> paradigm without worrying about those dependent plugins > > Adding to what Jesse wrote: It should be fairly trivial to read the plugin > dependencies from the HPI files and recursively (transitive dependencies) add > them to your installation. I think I even did that as a bash script once.
Thus guys you are proposing to rewrite the dependencies resolution mechanism of maven and friends in bash ? Because I agree that for one dependency it works but in a real world when you have several dozen of plugins to deploy how many transitive dependencies will you have ? How will you resolve conflicts/constraints betweens dependencies ? >From my point of view we have nowadays no solution to propose such service if >jenkins server isn’t started. The only solution is to start it and have it >connected to internet and then to use jerkins-cli to correctly install the >required plugins. To come back the the workflow mandatory dependency to add in all compatible plugins I don’t really like it. It just smells bad. I understand that its not a core feature, it has a different lifecycle. This library will never be able to have a 2.0 version with backward incompatible changes without breaking several dozen or hundred of plugins (I cannot imagine you may non intentionnaly integrate such incompatible changes - clirr is your friend). I would have preferred (I think) a dedicated workflow library/plugin hosting all the integrations with all dependencies as optional. Arnaud -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C698FA26-D972-419B-9AB5-67C114A6CD18%40gmail.com. For more options, visit https://groups.google.com/d/optout.
