|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
If you install plugins via Chef (directly dropping entries into $JENKINS_HOME/plugins/*.jpi) then it is your obligation to ensure that all dependencies are met. Currently Jenkins core does not enforce plugin dependencies at startup time (though a proposal to do so is filed).
I am not sure about the CLI and REST interfaces to install/update named plugins. Probably they ought to force upgrades of dependent plugins. If this is not the behavior you see, please file a core bug about it.