Thank for those answers and suggestions to solve those dependencies. I can somehow wrap that functionality but as long as I use the puppet jenkins module I'm a bit exposed since it doesn't support those transitive dependencies (https://github.com/jenkinsci/puppet-jenkins/tree/master) at the moment.
I thought the ssh-agent plugin will be independent of those plugin dependencies since it was released more than 3 years ago and suddenly there was an unexpected new dependency with another plugin library. Maybe it was my bad since I didn't review those plugin dependencies but I wasn't expected it will a change. On the other hand since the workflow plugin is an active plugin and being in development actively, I wonder whether that particular dependency won't affect it. Besides of that, what's the Jenkins strategy about the Workflow plugin? If it will be the standard process, shouldn't it be part of the core? IMO, it will help to avoid those new dependency transitive libraries. Thanks again On Friday, 9 October 2015 16:04:21 UTC+2, Jesse Glick wrote: > > On Fri, Oct 9, 2015 at 9:54 AM, Daniel Beck <[email protected] > <javascript:>> wrote: > > read the plugin dependencies from the HPI files and recursively > (transitive dependencies) add them to your installation > > Yes, you can do that. I tend to recommend instead that the tool > building the image flag these as errors, and suggest additions to the > plugin list (ideally also showing the newest version available from > the update center, like `mvn dependency:show-dependency-updates` would > do). That way your image is always built deterministically and > explicitly from sources. If you ignore the update center and just add > the newest version transitively required, you also get determinism, > though it is then not obvious from looking at config sources what the > final plugin list will be, which can make debugging issues harder. > -- 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/62fe5365-ff94-4d2a-94bc-ab2b44d164fa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
