I just found this jira ticket: https://issues.jenkins-ci.org/browse/JENKINS-41339. Using the PATH+EXTENSION=/extension syntax in my System config -> Environment Variables fixed the problem for me.
On Thu, Feb 2, 2017 at 4:27 PM, Guy Knights <[email protected]> wrote: > I upgraded some of my pipeline plugins (there were some groovy module > upgrades I believe, unfortunately I don't have a list of what was upgraded) > and suddenly my build pipelines no longer work and are throwing the > following error: > > Running on master in /var/jenkins_home/jobs/Project1/jobs/API - > Deploy/workspace > [Pipeline] { > [Pipeline] sh > [workspace] Running shell script > nohup: failed to run command ‘sh’: No such file or directory > [Pipeline] } > [Pipeline] // node > [Pipeline] } > [Pipeline] // stage > [Pipeline] End of Pipeline > ERROR: script returned exit code -2 > Finished: FAILURE > > Does anyone know why? > > Thanks, > Guy > -- 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/CANNH9msjy2Lbx8mFZ0_%3D1rPgR5JMUNYPT5Ymvi%3Dt7KugOBEGOg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
