> On 16. Aug 2017, at 23:09, Thad Guidry <[email protected]> wrote: > > it treats the whole flow-definition as an exception
I expect the log will show errors about unloadable plugins before this error occurs. Those should be clear as to why loading failed. On the Jenkins UI (if it manages to start), it will also show a message about unloadable plugins and the causes on the /manage URL. These might be different to decipher due to potentially wide dependency trees, but if it says "X cannot be loaded because Y is missing", and "Y cannot be loaded because Z is missing", then "Z" is the problem to take care of first. -- 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/621F12EA-6887-4B02-AE2B-EFBB253B0869%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
