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. For more options, visit https://groups.google.com/d/optout.
