After auto updating to 1.522 today ALL our Ivy Plugin jobs fail to load:
7/07/2013 7:43:08 PM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading job isbook-r-7-9-0
java.lang.NoSuchFieldError: triggers
at
hudson.ivy.AbstractIvyProject.createTransientActions(AbstractIvyProject
:52 AM UTC+12, flx wrote:
>
> On 09/12/2012 11:46 PM, Darren Rowley wrote:
> > yes exactly..
>
> so why not using a groovy postbuild script? See Example 4 on the wiki
> https://wiki.jenkins-ci.org/display/JENKINS/Groovy+Postbuild+Plugin
>
> Felix
>
yes exactly..
On Thursday, September 13, 2012 9:26:40 AM UTC+12, Nicolas De loof wrote:
>
> so, you want the build to keep running until completion, but be UNSTABLE
> (or worst) cause it took too much time ?
>
> 2012/9/12 Darren Rowley >
>
>> As I said in my original
timeout+Plugin
> Domi
>
> On 11.09.2012, at 03:48, Darren Rowley >
> wrote:
>
> > Is there any way to mark a build as unstable if it takes too long? I'm
> aware of the build timeout plugin but that appears to actually abort the
> build. I don't want
Is there any way to mark a build as unstable if it takes too long? I'm
aware of the build timeout plugin but that appears to actually abort the
build. I don't want the build to be aborted I just want the job to become
unstable.
I guess I could do this we a groovy post build action but just won
