|
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 wondering if I am missing a built in setting or plugin. thanks in advance, D. |
|
maybe this helps: https://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin
Domi On 11.09.2012, at 03:48, Darren Rowley <[hidden email]> 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 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 wondering if I am missing a built in setting or plugin. > > thanks in advance, > D. > |
|
I think the OP is aware of that plugin and the main issue seems to be
that the build timeout plugin aborts the build rather than makes it unstable. OP: Perhaps you could update the build timeout plugin to have the option of setting the build to unstable/failed rather than abort? Richard. On Wed, Sep 12, 2012 at 5:36 AM, domi <[hidden email]> wrote: > maybe this helps: https://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin > Domi > > On 11.09.2012, at 03:48, Darren Rowley <[hidden email]> 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 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 wondering if I am missing a built in setting or plugin. >> >> thanks in advance, >> D. >> > |
|
In reply to this post by domi
As I said in my original post I don't think it does as it aborts the build? Are you using it to just what I want? I could see an option..
On Wednesday, September 12, 2012 5:36:32 AM UTC+12, domi wrote: maybe this helps: https://wiki.jenkins-ci.org/ |
|
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 <[hidden email]> As I said in my original post I don't think it does as it aborts the build? Are you using it to just what I want? I could see an option.. |
|
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 ? |
|
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 as I said originally said I thought I would end up doing it this way. Just sometimes it's nicer to do it with a plugin or something built in rather than having a duplicated groovy script pasted into every test. But that's fine...
thanks. d. On Friday, September 14, 2012 7:42:52 AM UTC+12, flx wrote: On 09/12/2012 11:46 PM, Darren Rowley wrote: |
| Powered by Nabble | Edit this page |
