Re: Build flow "build" function doesn't return a build object if FAILED or UNSTABLE

Hi Christofer, Actually this is exactly what is written aline before (def BUILD_TO_RETURN). The problem is that when build is UNSTABLE or FAILED exception is being thrown without returning from the build method. Regards, Valeriy On Wednesday, December 2, 2015 at 2:41:12 AM UTC+2, Christopher

Re: Build flow "build" function doesn't return a build object if FAILED or UNSTABLE

Hi, >From my experience Build flow do not throw an exception if the build is >aborted, unstable or failed, assuming the build actually started and completed >normally. I assume you have checked what exception was caught. > 3 dec 2015 kl. 10:51 skrev Valeriy Leykin : > >

Re: Build flow "build" function doesn't return a build object if FAILED or UNSTABLE

Hi there, On 01/12/15 14:17, Valeriy Leykin wrote: > I'm using the build flow in my jobs and I would like to get any build > result from build object even if the build is failed or unstable. I haven't used Build Flow, but I would guess that this is a basic scoping problem. BUILD_TO_RETURN is

Build flow "build" function doesn't return a build object if FAILED or UNSTABLE

Hi, I'm using the build flow in my jobs and I would like to get any build result from build object even if the build is failed or unstable. For example: try{ BUILD_TO_RETURN = build(parameters: newparams, job: jobName, quietPeriod : 5); println("Result is: " +