-
Bug
-
Resolution: Fixed
-
Major
-
None
When using the "parallel" step heavily in a Jenkinsfile pipeline script, the "sh" steps fail with `Pipe not connected`:
[Pipeline] [job:2] sh [job:2] [myapp_jenkins-JAM5PI6ZOUNKGTGYGMINDN4KNK2PFRGQPKWNXCRMGAOHJME4OVZA] Running shell script [job:2] Executing shell script inside container [instance-1] of pod [kubernetes-54877d1afcea4c95afd17243772d03c6-82e3726b74871] [Pipeline] [job:2] } [job:2] Failed in branch job:2 [Pipeline] [job:3] sh [job:3] [myapp_jenkins-JAM5PI6ZOUNKGTGYGMINDN4KNK2PFRGQPKWNXCRMGAOHJME4OVZA] Running shell script [job:3] Executing shell script inside container [instance-1] of pod [kubernetes-54877d1afcea4c95afd17243772d03c6-82e3726b74871] [Pipeline] [job:3] } [job:3] Failed in branch job:3 ... [job:4] Failed in branch job:4 [job:5] Failed in branch job:5 [job:6] Failed in branch job:6 [job:7] Failed in branch job:7 [job:8] Failed in branch job:8 [job:9] Failed in branch job:9 java.io.IOException: Pipe not connected at java.io.PipedOutputStream.write(PipedOutputStream.java:140) at java.io.OutputStream.write(OutputStream.java:75) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:110) ...
jobs 0 and 1 succeed, but all the others continuously fail without any errors, except for "Pipe not connected".
- is blocked by
-
JENKINS-42048 Cannot Connect, PID NumberFormatException
-
- Closed
-