Re: Hudson Text-Finder

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Hudson Text-Finder

Kohsuke Kawaguchi
Administrator

You can use the text finder plugin to mark otherwise successful build as
a failure, but not the other way around.

The easy solution for you is to run Ant like:

   ant ... || true

to make it always return 0, then use text finder to mark the build as a
failure.

Ronald Paloschi wrote:

> Hello,
>
> A few days ago I started using Hudson to replace Luntbuild at my company.
> Well, We develop C++ applications and build it using ant scripts. It all
> went OK.
> But I needed a different way to analize the results of my builds and
> then I found your plugin.
> As my ant scripts are doing a lot of work, they always return NONZERO to
> the console, and even using text-finder, the build always fail.
>
> Im using Hudson 1.238 and text finder 1.2,
>
> Thanks in advance.
>
> []'s
> Ronald
>
>


--
Kohsuke Kawaguchi
http://weblogs.java.net/blog/kohsuke/

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Hudson Text-Finder

Adam Purkiss
Would it be worth having the opposite plugin - i.e. text finder for pass and make the last thing you do in ant echo a success message.... hmmmm maybe not a great idea unless you are sure that nothing else will display the text and you are sure nothing else can have gone wrong if the text is displayed. Or of course have a flag that if checked marks a build a success unless the specified text is not found, but then you have to be damn sure about what you are looking for?
 
Just a thought






> Date: Wed, 30 Jul 2008 16:58:22 -0700

> From: [hidden email]
> To: [hidden email]; [hidden email]
> Subject: Re: Hudson Text-Finder
>
>
> You can use the text finder plugin to mark otherwise successful build as
> a failure, but not the other way around.
>
> The easy solution for you is to run Ant like:
>
> ant ... || true
>
> to make it always return 0, then use text finder to mark the build as a
> failure.
>
> Ronald Paloschi wrote:
> > Hello,
> >
> > A few days ago I started using Hudson to replace Luntbuild at my company.
> > Well, We develop C++ applications and build it using ant scripts. It all
> > went OK.
> > But I needed a different way to analize the results of my builds and
> > then I found your plugin.
> > As my ant scripts are doing a lot of work, they always return NONZERO to
> > the console, and even using text-finder, the build always fail.
> >
> > Im using Hudson 1.238 and text finder 1.2,
> >
> > Thanks in advance.
> >
> > []'s
> > Ronald
> >
> >
>
>
> --
> Kohsuke Kawaguchi
> http://weblogs.java.net/blog/kohsuke/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>



Reply | Threaded
Open this post in threaded view
|

Re: Hudson Text-Finder

Tom Larrow
I think it would be better to have a more robust text-finder plugin.  Just the other day I was looking for a way of marking a build unstable if certain words appeared in the logs.  In particular what I was trying to do was catch if there were any warnings thrown when the Javadoc was built, and if there were, the build would be marked unstable.  Both so that people wouldn't trust the javadoc for that build, and so that the developer who made the most recent commit could get an email that he made the build unstable, and fix the comments in his code which would fix the javadoc)

 With Text-Finder, all I could do was mark it as broken.  Kind of extreme to mark it as broken, but it was the only thing the Text-Finder plugin allowed.

-Tom Larrow

On Wed, Jul 30, 2008 at 8:04 PM, Adam Purkiss <[hidden email]> wrote:
Would it be worth having the opposite plugin - i.e. text finder for pass and make the last thing you do in ant echo a success message.... hmmmm maybe not a great idea unless you are sure that nothing else will display the text and you are sure nothing else can have gone wrong if the text is displayed. Or of course have a flag that if checked marks a build a success unless the specified text is not found, but then you have to be damn sure about what you are looking for?
 
Just a thought






> Date: Wed, 30 Jul 2008 16:58:22 -0700
> From: [hidden email]
> To: [hidden email]; [hidden email]
> Subject: Re: Hudson Text-Finder

>
>
> You can use the text finder plugin to mark otherwise successful build as
> a failure, but not the other way around.
>
> The easy solution for you is to run Ant like:
>
> ant ... || true
>
> to make it always return 0, then use text finder to mark the build as a
> failure.
>
> Ronald Paloschi wrote:
> > Hello,
> >
> > A few days ago I started using Hudson to replace Luntbuild at my company.
> > Well, We develop C++ applications and build it using ant scripts. It all
> > went OK.
> > But I needed a different way to analize the results of my builds and
> > then I found your plugin.
> > As my ant scripts are doing a lot of work, they always return NONZERO to
> > the console, and even using text-finder, the build always fail.
> >

> > Im using Hudson 1.238 and text finder 1.2,
> >
> > Thanks in advance.
> >
> > []'s
> > Ronald
> >
> >
>
>
> --
> Kohsuke Kawaguchi
> http://weblogs.java.net/blog/kohsuke/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>




Reply | Threaded
Open this post in threaded view
|

Re: Hudson Text-Finder

Kohsuke Kawaguchi
Administrator
Tom Larrow wrote:

> I think it would be better to have a more robust text-finder plugin.  Just
> the other day I was looking for a way of marking a build unstable if certain
> words appeared in the logs.  In particular what I was trying to do was catch
> if there were any warnings thrown when the Javadoc was built, and if there
> were, the build would be marked unstable.  Both so that people wouldn't
> trust the javadoc for that build, and so that the developer who made the
> most recent commit could get an email that he made the build unstable, and
> fix the comments in his code which would fix the javadoc)
>
>  With Text-Finder, all I could do was mark it as broken.  Kind of extreme to
> mark it as broken, but it was the only thing the Text-Finder plugin allowed.
Any chance you'd be interested in writing a patch for this?


>
> -Tom Larrow
>
> On Wed, Jul 30, 2008 at 8:04 PM, Adam Purkiss <[hidden email]> wrote:
>
>> Would it be worth having the opposite plugin - i.e. text finder for pass
>> and make the last thing you do in ant echo a success message.... hmmmm maybe
>> not a great idea unless you are sure that nothing else will display the
>> text and you are sure nothing else can have gone wrong if the text is
>> displayed. Or of course have a flag that if checked marks a build a success
>> unless the specified text is not found, but then you have to be damn sure
>> about what you are looking for?
>>
>> Just a thought
>>
>>
>>
>>
>> ------------------------------
>>
>> > Date: Wed, 30 Jul 2008 16:58:22 -0700
>> > From: [hidden email]
>> > To: [hidden email]; [hidden email]
>> > Subject: Re: Hudson Text-Finder
>>
>> >
>> >
>> > You can use the text finder plugin to mark otherwise successful build as
>> > a failure, but not the other way around.
>> >
>> > The easy solution for you is to run Ant like:
>> >
>> > ant ... || true
>> >
>> > to make it always return 0, then use text finder to mark the build as a
>> > failure.
>> >
>> > Ronald Paloschi wrote:
>> > > Hello,
>> > >
>> > > A few days ago I started using Hudson to replace Luntbuild at my
>> company.
>> > > Well, We develop C++ applications and build it using ant scripts. It
>> all
>> > > went OK.
>> > > But I needed a different way to analize the results of my builds and
>> > > then I found your plugin.
>> > > As my ant scripts are doing a lot of work, they always return NONZERO
>> to
>> > > the console, and even using text-finder, the build always fail.
>> > >
>> > > Im using Hudson 1.238 and text finder 1.2,
>> > >
>> > > Thanks in advance.
>> > >
>> > > []'s
>> > > Ronald
>> > >
>> > >
>> >
>> >
>> > --
>> > Kohsuke Kawaguchi
>> > http://weblogs.java.net/blog/kohsuke/
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [hidden email]
>> > For additional commands, e-mail: [hidden email]
>> >
>>
>>
>> ------------------------------
>>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   http://weblogs.java.net/blog/kohsuke/

smime.p7s (4K) Download Attachment