> On 17. Aug 2017, at 21:37, Thad Guidry <[email protected]> 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. 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. -- 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/A9855EA6-8F05-4E66-8B7D-FF5546097563%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
