> On 26.11.2016, at 00:05, Victor Martinez <[email protected]> > wrote: > > unfortunately Jenkins plugins are a bit evil as their dependencies are not > updated accordingly when using any Configuration Management tool
Good point. I think it depends on how these tools implement plugin installation. IIRC the CLI command can be terrible in "URL" mode, as is modifying plugins/ directly. That said, dependency resolution in Jenkins just installs whatever is the newest version, which I'm pretty sure you don't want either -- so there's little that Jenkins can do. Or can it? How would this need to work to be less problematic, with the caveat that Jenkins update sites will not be able to serve a list of plugin versions for the foreseeable future, and only offer the newest ones (and therefore will only install newest versions when resolving dependencies)? Note that all regular dependency metadata is stored in the plugin ZIP file, so I'm kind of surprised config management tools haven't gotten this worked out. Sure, it's not as easy as just wrapping a one-line CLI command, but it's not an unsurmountable challenge. What am I missing? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/D8E6E694-DEB4-4076-A29B-50BC2D486006%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
