-
Bug
-
Resolution: Duplicate
-
Critical
-
Jenkins 2.7.1
Durable Task Plugin 1.12
Pipeline 2.4
I've got many nodes running on different Linux distribution and also few windows nodes running with SSH slaves and Cygwin (https://wiki.jenkins-ci.org/display/JENKINS/SSH+slaves+and+Cygwin)
Using the following pipeline script:
_node('linuxHost') {
stage('linuxHost linux')
}
node('windowsHost') {
stage('windowsHost cygwin')
}_
On my windows node I always got an error "ERROR: script returned exit code -1" if my script execution time is greater than about 250ms no matter what the command content is (that's why I'm using a basic sleep for this example). I've got the exact same behavior for all of my windows nodes.
Here are the execution logs:
_Started by user Administrateur Jenkins
[Pipeline] node
Running on linuxHost in /var/jenkins_home/workspace/Unstable/TestShInPipeline
[Pipeline] {
[Pipeline] stage
[Pipeline]
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] node
Running on windowsHost in C:/Users/localuser/jenkins_home/workspace/Unstable/TestShInPipeline
[Pipeline] {
[Pipeline] stage
[Pipeline]
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code -1
Finished: FAILURE_
May be related to JENKINS-32017 ?
It works fine using the same node and the "Execute Shell" build step in a freestyle project.
- duplicates
-
JENKINS-47791 Eliminate ProcessLiveness
- Resolved
- is duplicated by
-
JENKINS-42405 “Could not initialize class ProcessLiveness$LibC” running sh on Windows
- Resolved