I'm pretty sure Daniel didn't say to not use the plugin manager. He said that IF you don't use it, then you need to make sure all the dependencies are handled correctly on your own. The plugin manager does that for you, but just dropping hpi files into JENKINS_HOME is not expected to work if you don't provide all the dependencies yourself.
On Fri, Aug 25, 2017, 09:01 Thad Guidry <thadgui...@gmail.com> wrote: > On Fri, Aug 25, 2017 at 2:15 AM Daniel Beck <m...@beckweb.net> wrote: > >> >> > On 17. Aug 2017, at 21:37, Thad Guidry <thadgui...@gmail.com> wrote: >> > >> > My suggestion to the Dev team is to get the full Pipeline Plugin suite >> into the RPM's going forward. That will alleviate a lot of headache I >> think for most folks doing standard CI/CD since many have already converted >> to Pipeline for that, such as us at Ericsson. >> > >> >> Just going through the setup wizard will install the Pipeline suite. >> >> > I did. It did not completely, which is why they problem surfaced. > > >> If you bypass that, and also don't use the plugin manager in Jenkins in >> Jenkins, but rather populate JENKINS_HOME/plugins manually, you're expected >> to know what you're doing -- mostly parsing the dependencies of plugins, >> and ensuring they're all satisfied. >> >> > Dude, SERIOUSLY ? Make sure to tell other users not to use the plugin > manager that took Jenkins developers about 2 years to build up and that > gets feature tested multiple times per day and prior to release. Let's > also make sure we make it harder for Jenkins admins and throw out software > solutions to make their lives easier...besides they really enjoy parsing > XML files themselves rather than sipping Mimosa's on the beach. > > Daniel, please respect all the effort that Jenkins open source developers > put into the software. Your better than that, you work for the 1 > institution that supports Jenkins and has good respect and contributes > directly to features that Jenkins provides. Cloudbees. > > -Thad > +ThadGuidry <https://www.google.com/+ThadGuidry> > > -- > 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 jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/CAChbWaNjhi67AEPZzbCG0HnyiGCsZPxeOfodiT5fm8vJ_99tfA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CAChbWaNjhi67AEPZzbCG0HnyiGCsZPxeOfodiT5fm8vJ_99tfA%40mail.gmail.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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVe4rj3fh%2BSMG9Kh-76y0piffXPNbU%3Ds4d-22Us8X84X3w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
