Managed to find something on stackoverflow which pointed me in the right direction. Apparently we had a really OLD override to PATH defined in our System configuration which I didn't know about. Removing that fixed the problem.
Perhaps the plugin writing out the error could give a short hint towards that as well? Seems that the rule have changed (for the better), but trying to understand why old (more or less misconfigured) systems suddenly fail isn't always that easy. Cheers, Andreas On Monday, June 19, 2017 at 6:44:19 AM UTC+2, Andreas Magnusson wrote: > > After an upgrade of my Jenkins installation (2.65 and all plugins updated) > I cannot for my life get the 'sh' command to work. This is my mini example: > > node('linux') { > sh 'echo $PATH' > } > > and this is the output: > > > Started by user anonymous <http://localhost:8080/user/null>[Pipeline] > nodeRunning on CentOS in /var/lib/jenkins/workspace/pipe[Pipeline] > {[Pipeline] shWarning: JENKINS-41339 probably bogus > PATH=$PATH:/usr/local/bin/:/usr/local/bin/; perhaps you meant to use > ‘PATH+EXTRA=/something/bin’? > [pipe] Running shell script > nohup: failed to run command ‘sh’: No such file or directory[Pipeline] > }[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code > -2 > Finished: FAILURE > > > Does anyone have any idea what I've done wrong? I haven't configured the > CentOS machine in any way, it's just a test slave to try to verify this > behaviour. > > Or do you need anything else from my env to help me, just let me know. > > > /Andreas > > -- 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/31ddc905-cf78-4a3c-941e-0de1788d2904%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.