-
Bug
-
Resolution: Unresolved
-
Critical
-
Jenkins 1.6.16
Workflow 1.8
Windows 8.1 Slaves
Batch steps that succeed are hanging, more frequently since the upgrade to Jenkins 1.6.16 + WF 1.7; I think this is recent, I do not recall encountering such issues with Jenkins 1.6.09 + WF 1.5. This is highly problematic for workflow scripts that rely on large numbers of batch steps. Note, the slave nodes in question may be considered "high-latency" with response times occasionally in seconds.
Reproduced 2 out of 4 times using the following test idiom, increasing the below loop to 1000 will probably make it a 100% reproduction, parallelizing anecdotally seems to increase reproduction:
node('slave') { for( int i = 0; i < 100; ++i ) { echo "i=${i}" bat *<some batch step that takes variable time to run, eg scm or make>* } }
- is duplicated by
-
JENKINS-33164 Pipeline bat stuck on Windows Server 2012
- Open
- is related to
-
JENKINS-27419 dos "exit" command not functioning correctly
- Resolved
-
JENKINS-31769 sh steps on slaves randomly hang when complete
- Resolved
-
JENKINS-28604 Parallel step with node blocks for the same agent will create 2nd executor on single-executor slaves
- Resolved
- links to