Manual upload completely bypasses the dependency handling. On Sunday 5 June 2016, <[email protected]> wrote:
> Please note that if you have installed plugins manually by downloading the > .jpi file into the $JENKINS_HOME/plugins folder before starting jenkins, > then dependency resolution is not automatically performed at jenkins > startup. > So if you install plugin A, you must also install plugin B or else jenkins > might fail at startup > > Not sure how it works if you manually upload plugin A, and it requires > plugin B... > > > Le samedi 4 juin 2016 15:35:20 UTC+2, Baptiste Mathus a écrit : >> >> Using the plugin manager, asking for a plugin installation will trigger >> the installation of its (plugin) dependencies. >> >> If it does not, then it's probably a bug in that plugin, and you want to >> file it. >> >> 2016-06-03 17:09 GMT+02:00 Robert Kruck <[email protected]>: >> >>> Does the Jenkins "Manage Plugins" page display a warning, if a Jenkins >>> Plugin has a missing dependency? >>> >>> Example: If *Jenkins Plugin "A"* requires *Jenkins Plugin "B"* as a >>> dependency, and I installed Jenkins Plugin "A" * only*, would a warning >>> about the missing *Jenkins Plugin "B"* appear in the Jenkins "Manage >>> Plugins" page? >>> >>> I have researched this issue for some time on the internet - at present >>> it appears that some Jenkins plugins have this sort of automated dependency >>> checking, but others don't. >>> >>> Please advise; I was thinking of making a spreadsheet to show the >>> dependencies of the Jenkins Plugins we currently use - but if Jenkins has >>> automated dependency checking for all its Plugins, such a spreadsheet would >>> obviously be a waste of time. >>> >>> -- >>> 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/d8b2f1ad-0cfc-4197-9876-2c534b46807b%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/d8b2f1ad-0cfc-4197-9876-2c534b46807b%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > 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] > <javascript:_e(%7B%7D,'cvml','jenkinsci-users%[email protected]');> > . > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/b256faa8-c990-4aff-87a1-6c2a566c019f%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/b256faa8-c990-4aff-87a1-6c2a566c019f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Sent from my phone -- 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/CA%2BnPnMyz8-2zQhm_WxUgxePC00rF%3DRwPsEqAe0s8pn65Q6b8%3Dg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
