On 11.04.2016, at 19:11, Daniel Daugherty <daniel.daughe...@gmail.com> wrote:
> Taking the base install of JenkinsRC I get regular hanging batch commands.
> When I check running tasks the batch has finished but Jenkins is still
> looking for the results. After some investigation I found the batch files
> being run by jenkins. jenkins-main.bat and jenkins-wrap.bat The wrap calls
> main. Once main is complete the wrap should write a the file
> jenkins-result.txt into the job folder. This file is not present when the
> task hangs. If is create a file with a 1 or 0 in it the task complete as
> expected. This failure is not every time but at least 2 out of 10 time it
> will fail.
>
> example build
>
> node{
> echo 'test 123'
> bat 'ping -r 10 127.0.0.1'
> echo 'test done'
> }
>
> It will do the first echo and the ping completes but the eche 'test done'
> never starts. This make Jenkins pipeline unusable for us.
>
Could you file a bug against the 'workflow-plugin' component in JIRA, ideally
with steps to reproduce? As this may be environment dependent, better include
as much as you can. Are you running an antivirus tool that scans the directory
this file should be in?
https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/99F70B5A-6698-4A90-AA7E-2795CF312C2D%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
