int128 / int128/gradle-ssh-plugin
Execute command not ended - Task frozen
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 325
- Forks
- 59
- Avg merge
- 5h 29m
- Merged PRs (30d)
- 6
Description
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
- org.hidetake:gradle-ssh-plugin:2.9.0
- Red Hat
- Java 7
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the installWorkaround task in a Jenkins pipeline, focusing on the ssh.run block and the final execute call. Compare its behavior with the other tasks that use the same structure and inspect the plugin's available logging or trace output. Done means the cause of the stalled task is identified and the completion or timeout behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100