-
Bug
-
Resolution: Duplicate
-
Minor
-
Jenkins 2.32.2
Linux master, Windows slave
Pipeline 2.5
Pipeline Groovy 2.27
Pipeline Job 2.10
Pipeline Nodes and Processes 2.9
Pipeline Stage 2.2
I have two Windows slaves. When I run pipeline jobs on these slaves I get tons of error messages
Cannot contact Windows7: java.io.IOException: Remote call on Channel to /172.17.xxx.xxx failed
Yet the job finishes successfully. A minimal example to reproduce is
node('windows') {
stage('Test') {
sh '''
for ((i=0; i < 100; i++)); do
echo $i
sleep 1
done
'''
}
}
Executing the same shell script via a freestyle job on the same Windows slave works without any error messages therefore it's very likely that this is a bug in the pipeline implementation.
Restarting slaves and master doesn't change anything. I also couldn't find any more information in log files (or I am looking at the wrong place)
- duplicates
-
-
- Resolved
-
-
JENKINS-47791 Eliminate ProcessLiveness
-
- Resolved
-
[JENKINS-42405] “Could not initialize class ProcessLiveness$LibC” running sh on Windows
Thorsten Meinl
created issue -
Thorsten Meinl
made changes -
| Labels | New: regression |
| Component/s | New: durable-task-plugin [ 18622 ] | |
| Component/s | Original: pipeline [ 21692 ] | |
| Labels | Original: regression | New: windows |
| Summary | Original: Lots of remote channel errors with pipelines and Windows slaves | New: “Could not initialize class ProcessLiveness$LibC” running sh on Windows |
| Link |
New:
This issue duplicates |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
| Link |
New:
This issue duplicates |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: In Review [ 10005 ] | New: Resolved [ 5 ] |