I have a Jenkins pipleine script with stages staging in dev env, running tests and staging in sys environment. So staging in dev envrionment is working perfectly alright ,the following commands are also working sh "node -v" echo "${env.path}" sh "npm install -g r2d2-node"
Then i change my node to windows to run my automation scripts on a windows remote slave and change back the node to linux ( till here its successful). Then when staging into syst environment , i have the exact same commands sh "node -v" sh "npm install -g r2d2-node"
which is getting stuck. basically at every shell command its getting stuck and i am ending up with the below error.
process apparently never started in /opt/ltsapps/jenkins/workspace/UI/some_Pipeline@tmp/durable-568d9f2c
(running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
So i saw multiple solutions in stackover flow, majority of them directed to updating the durable-task plugin which i did. Currently my plug in version is at 1.35.
question from:
https://stackoverflow.com/questions/66052750/shell-command-not-executing-stuck-after-changing-the-node-from-windows-to-linu 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…