Are you using a build-name-setter plugin in this job? For us, we were using it. Having stopped that, we are not seeing this problem. But I am not sure.
On Tuesday, 1 April 2014 23:12:15 UTC-4, Dilip M wrote: > > > > On Wed, Dec 18, 2013 at 2:43 PM, Søren Mollerup <[email protected]>wrote: > >> We've run into a weird problem lately. >> >> A couple of our jobs are sometimes marked as failures in the build >> history, and the trend says it is finished after 0 ms. >> If I examine the console output the build is executed as normal and >> reported as a success and the downstream projects are triggered as well. >> >> The affected jobs are maven jobs, and it seems that both java6 and java7 >> build nodes behave like this once in a while. >> >> Has anyone else experienced this problem, or do anyone have an idea what >> to examine? >> > > WE recently came across this issue with Freestyle job type. > > Jenkins ver. 1.532.2 > Slave.jar version: 2.33 > > > -- 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]. For more options, visit https://groups.google.com/d/optout.
