Quantcast

getting an uptodate consoleText

classic Classic list List threaded Threaded
5 messages Options
wef
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

getting an uptodate consoleText

wef
Because maven doesn't return reliable error codes (eg on "[ERROR] build failure") in my 'PostBuild Script' I need to

wget $BUILD_URL/consoleText

... and then grep for problems.

Trouble is, I don't always get the whole thing - very often the last chunk is missing.

Doesn't matter if I wait (eg 10 minutes) or have the job print out 20k of rubbish to try and flush ot out - I'm still missing the interesting bit.
Once the job has finished, I can always wget the whole thing - it's just while the job is in flight that I have problems.

Any ideas on how to flush the dang thing out?

Or maybe there's a plug-in to do this?


Thanks in advance


Bob
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: getting an uptodate consoleText

Richard Bywater-2
I think https://wiki.jenkins-ci.org/display/JENKINS/Text-finder+Plugin
might be the plugin you're looking for (spoken like a true Jedi)

Richard.

On Mon, Aug 27, 2012 at 2:51 PM, wef <[hidden email]> wrote:

> Because maven doesn't return reliable error codes (eg on "[ERROR] build
> failure") in my 'PostBuild Script' I need to
>
> wget $BUILD_URL/consoleText
>
> ... and then grep for problems.
>
> Trouble is, I don't always get the whole thing - very often the last chunk
> is missing.
>
> Doesn't matter if I wait (eg 10 minutes) or have the job print out 20k of
> rubbish to try and flush ot out - I'm still missing the interesting bit.
> Once the job has finished, I can always wget the whole thing - it's just
> while the job is in flight that I have problems.
>
> Any ideas on how to flush the dang thing out?
>
> Or maybe there's a plug-in to do this?
>
>
> Thanks in advance
>
>
> Bob
wef
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: getting an uptodate consoleText

wef
Thanks for that - I'll give it a burl once the build server is quiet

On Monday, August 27, 2012 1:14:53 PM UTC+10, Richard Bywater wrote:
I think https://wiki.jenkins-ci.org/display/JENKINS/Text-finder+Plugin
might be the plugin you're looking for (spoken like a true Jedi)

Richard.

On Mon, Aug 27, 2012 at 2:51 PM, wef <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="hje8A1QnEagJ">bob.h...@...> wrote:

> Because maven doesn't return reliable error codes (eg on "[ERROR] build
> failure") in my 'PostBuild Script' I need to
>
> wget $BUILD_URL/consoleText
>
> ... and then grep for problems.
>
> Trouble is, I don't always get the whole thing - very often the last chunk
> is missing.
>
> Doesn't matter if I wait (eg 10 minutes) or have the job print out 20k of
> rubbish to try and flush ot out - I'm still missing the interesting bit.
> Once the job has finished, I can always wget the whole thing - it's just
> while the job is in flight that I have problems.
>
> Any ideas on how to flush the dang thing out?
>
> Or maybe there's a plug-in to do this?
>
>
> Thanks in advance
>
>
> Bob
wef
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: getting an uptodate consoleText

wef
I tried text-finder but it's only available as a 'post-build action' ie after all the post-build steps are finished.

What I think I need is a 'post-build step' that I can insert before other post-build steps to stop the build if it sees an error in the log.

Sorry if I've confused things.

On Monday, August 27, 2012 2:06:43 PM UTC+10, wef wrote:
Thanks for that - I'll give it a burl once the build server is quiet

On Monday, August 27, 2012 1:14:53 PM UTC+10, Richard Bywater wrote:
I think https://wiki.jenkins-ci.org/display/JENKINS/Text-finder+Plugin
might be the plugin you're looking for (spoken like a true Jedi)

Richard.

On Mon, Aug 27, 2012 at 2:51 PM, wef <[hidden email]> wrote:

> Because maven doesn't return reliable error codes (eg on "[ERROR] build
> failure") in my 'PostBuild Script' I need to
>
> wget $BUILD_URL/consoleText
>
> ... and then grep for problems.
>
> Trouble is, I don't always get the whole thing - very often the last chunk
> is missing.
>
> Doesn't matter if I wait (eg 10 minutes) or have the job print out 20k of
> rubbish to try and flush ot out - I'm still missing the interesting bit.
> Once the job has finished, I can always wget the whole thing - it's just
> while the job is in flight that I have problems.
>
> Any ideas on how to flush the dang thing out?
>
> Or maybe there's a plug-in to do this?
>
>
> Thanks in advance
>
>
> Bob
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: getting an uptodate consoleText

David Baird
In reply to this post by wef
Do you think this is related to the bug I reported?

David

On Sunday, August 26, 2012 7:51:08 PM UTC-7, wef wrote:
Because maven doesn't return reliable error codes (eg on "[ERROR] build failure") in my 'PostBuild Script' I need to

wget $BUILD_URL/consoleText

... and then grep for problems.

Trouble is, I don't always get the whole thing - very often the last chunk is missing.

Doesn't matter if I wait (eg 10 minutes) or have the job print out 20k of rubbish to try and flush ot out - I'm still missing the interesting bit.
Once the job has finished, I can always wget the whole thing - it's just while the job is in flight that I have problems.

Any ideas on how to flush the dang thing out?

Or maybe there's a plug-in to do this?


Thanks in advance


Bob
Loading...