> On 25. Aug 2017, at 20:17, Thad Guidry <[email protected]> wrote: > > I only used the plugin manager and didn't manually drop in plugins.
What you describe is a frequent symptom of people _not_ using the built-in ways to install plugins, so that was a reasonable guess (in fact, copying over plugins from one system to another -- if you've done that -- is exactly that). Installing and updating plugins via built-in plugin manager ensures dependencies are always satisfied (or it tells you loudly when not). > The only issue then is to help users know which plugins are missing much more > clearly. Showing only the classnames versus also providing the actual label > names from https://plugins.jenkins.io Labels (or plugins.jenkins.io URLs) may actually be unknown to Jenkins (dependency on a plugin not on an update site), but it should be possible in most cases. > or even better, providing a one click download and install option for those > reported missing in the warning box by the login. (forgot what its was called) Right now, due to larger dependency trees, some plugins reported missing might not actually be (just unloadable due to dependency issues upstream), and installing unconditionally may change the installed version to the newest (or, in rare cases, one actually incompatible with the current version of Jenkins, and yes, that's as stupid as it seems). Not impossible, just more work to integrate. Could you file an Improvement in Jira for these? Project is JENKINS, component is core. -- 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/6DA070E9-8719-4DE3-B1DC-A62AC059F82D%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
