Why don't you handle the result codes in your job? Meaning just intercept the result code and change it to 0 if the build is only unstable. Yes, it is an ugly solution...
On Thursday, November 22, 2012 10:40:19 AM UTC-5, Egle wrote: > > Hi, > > I am trying to set up a following flow if builds: > build( "A" ) > build( "B" ) > build( "C" ) > > Now I get "FATAL: null" error and stack trace in console if build B is > unstable. So the flow does not execute job C. Is there a way to configure a > flow that it would only terminate if the performed builds are failing and > not becoming unstable? > > Thanks, > Egle >