According to our traces, the last "execute" script "workaroundScript" is performed and finished with exit 0
Nevertheless we never see the result of the next println task "End of Gradle task"
And few minutes later a Jenkins timeout appears and the pipeline is noted "in error".
However the job has been done correctly.
We have also other tasks, with the same structure and they are running without any problem.
Do you have an idea how to understand this kind of problem ? Where can we found "traces" or log ?
Hi
In a Jenkins pipeline, we "call" a gradlew to execute a "installWorkaround" task. This task is defined as followed:
task installWorkaround { doLast { description 'Install workaround task **' println "\n ===> Install workaround for cluster ${cluster}" ssh.run { session(remotes.role('bootstrap')) { execute "cd ${targetDir}; chmod 755 ./$workaroundScript" execute "cd ${targetDir}; ./${workaroundScript} ${cluster}" println "\n\nEnd of Gradle task installWorkaround\n\n" } } } }
According to our traces, the last "execute" script "workaroundScript" is performed and finished with exit 0 Nevertheless we never see the result of the next println task "End of Gradle task" And few minutes later a Jenkins timeout appears and the pipeline is noted "in error". However the job has been done correctly. We have also other tasks, with the same structure and they are running without any problem.
Do you have an idea how to understand this kind of problem ? Where can we found "traces" or log ?
Environment info