Yes I upgraded some plugins and restarted jenkins a few hours before this happened. But after that several builds of this job went fine, so I'm thinking it must be something else that has triggered the SOE.
Changing the agent declaration in the pipeline script I did using the "Replay" function, which could also be the reason for the SOE. Will test dropping those builds first, and if that doesnt help try to drop whole job and/or downgrade plugins. Den 11 juni 2017 12:51 fm skrev "Dan Tran" <dant...@gmail.com>: > did happen to me due to plugin upgrade, either dashboard or monitor. ended > up to revert both and drop the mulit branch (set the repo scanner to xxx) > and recreate again ( put scanner back to .*) > > did you upgrade? > > -Dan > > must drop the job since your job config.xml is corrupted with tons of > weidr entries relate to the log > -- 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/CABwQARsDer4vfTXSu7U6nB70Ns-7wpqCpP0mQ33pRdPejSyH6Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
