Re: Jenkins 2.0RC windows Batch file fail
Issue created and band-aid pull request submitted. As stated in the pull
request while troubleshooting the issue reverting a change in how Jenkins
logs batch command output back to older code allows code to function as
expected. I have the example job in the bug running one a min for 3+ hours
now with no failure. Revert back to 1.9 release of durable-task-plugin I
am lucky to get 10 strait working.
https://issues.jenkins-ci.org/browse/JENKINS-34150
https://github.com/jenkinsci/durable-task-plugin/pull/20
On Monday, April 11, 2016 at 1:59:10 PM UTC-4, Daniel Beck wrote:
>
>
> On 11.04.2016, at 19:11, Daniel Daugherty > 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/5d755baa-6822-424d-b5c9-9f3109324c82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Jenkins 2.0RC windows Batch file fail
On 11.04.2016, at 19:11, Daniel Daugherty 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.
Jenkins 2.0RC windows Batch file fail
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.
Daniel D.
--
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/44f2430e-36f8-447a-9e26-deffd2cf2b9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
