I think those two lines are independent of one another. The line: Build step 'Execute Windows batch command' marked build as failure
hints that the batch script returned a failure code to its calling environment. I believe the default exit value for a batch script is the exit value of the last command executed in that script. If you want to ignore that last return value, add EXIT 0 to the end of the first batch script so that it will always return success. Mark Waite On Thu, Apr 16, 2015 at 2:39 PM Victoria Wei Lei <[email protected]> wrote: > Mark, > > the particular step is to call two processes by window batch command, > those processes are successfully running after I set BUILD_ID=dontKillMe. > Jenkins job was still marked as failure: > > Process leaked file descriptors. See > http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for > more information > Build step 'Execute Windows batch command' marked build as failure > > > Thanks > On Thursday, April 16, 2015 at 3:21:03 PM UTC-5, Mark Waite wrote: > >> I'm surprised if a process leaking a file descriptor would cause a build >> step to fail. I've never seen it fail in any of the cases where it was >> reported on my jobs. >> >> You may want to confirm that the build step did not fail, independent of >> whether or not there was a leaked file descriptor. If you're building on >> Unix, be sure that the build step reports success (exit 0 from a shell >> script, etc.). >> >> Mark Waite >> >> On Thu, Apr 16, 2015 at 1:49 PM Victoria Wei Lei <[email protected]> >> wrote: >> > if it is hard to get rid of "Process leaked file descriptors", is there >>> anyway I can make Jenkins ignore this failure step (or don't fail it), so >>> I can move on next step. >>> I am looking at Conditional buildstep plugin, but not able to figure >>> out how this plugin work and whether it is the right plugin to achieve >>> above goal? >>> >>> Please help. >>> Thanks >>> Victoria >>> >>> On Tuesday, April 14, 2015 at 3:34:39 PM UTC-5, Victoria Wei Lei wrote: >>>> >>>> I need to invoke two window processes in order to start our test after >>>> Jenkins build is down. They were normally killed after being brought up, >>>> and I receive "Process leaked file descriptors". I found someone suggest to >>>> do "set BUILD_ID=dontKillMe " before calling my command to start processes. >>>> Good news is that the processes are able to stay. Bad news is "Process >>>> leaked file descriptors" still occur and mark Jenkins job failed, hence, I >>>> can't execute any test steps afterwards >>>> >>>> Any input will be highly appreciated. >>>> >>> -- >>> 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 [email protected]. >> >> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/2db1326a-066f-4cfe-9adc-3d5b814dad11%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/2db1326a-066f-4cfe-9adc-3d5b814dad11%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEe%3DaBvjTzkU6EHcQ349t4JF5oa%3D7H%3DgJMr978AB6DcQA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
