color coding of build failure message

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

color coding of build failure message

sankarr
Like to request an enhancement to the reporting of failure message for builds. This applies to both email messages and the console output[raw]. When there are multiple builds in one Hudson project, it becomes difficult to scan through the whole message log and locate the error. If this is color coded, it will be easier for the recepient to locate the error.

We are using Hudson Text finder for reporting build failures. it will be nice to highlight / color code few lines above and few lines below the actual build error.

Is there an env variable to limit the number of log message lines that get sent out in email notifications?

thanks
Sankar
Reply | Threaded
Open this post in threaded view
|

RE: color coding of build failure message

Paul Sander-2
I personally find that color-coding log output and email notifications is more trouble than it's worth, particularly if there is some automated analysis done to the log.  Instead, I write a filter to remove the known uninteresting messages from a log.  This leaves the interesting and unexpected output.  The filtered output can in turn have highlighting added if desired.

Keep in mind that color coding makes life more difficult for our color-blind colleagues.  Various email user agents do various ugly things to messages that don't comply strictly with various standards like printable ASCII or RTF that don't explicitly support color or if displayed in windows that don't agree on standard color codes.  That sort of thing should be taylored to the individual users' tastes anyway.

> -----Original Message-----
> From: sankarr [mailto:[hidden email]]
> Sent: Tuesday, July 07, 2009 6:08 PM
> To: [hidden email]
> Subject: color coding of build failure message
>
>
> Like to request an enhancement to the reporting of failure message for
> builds. This applies to both email messages and the console
> output[raw].
> When there are multiple builds in one Hudson project, it
> becomes difficult
> to scan through the whole message log and locate the error.
> If this is color
> coded, it will be easier for the recepient to locate the error.
>
> We are using Hudson Text finder for reporting build failures.
> it will be
> nice to highlight / color code few lines above and few lines below the
> actual build error.
>
> Is there an env variable to limit the number of log message
> lines that get
> sent out in email notifications?
>
> thanks
> Sankar
>
> --
> View this message in context:
> http://www.nabble.com/color-coding-of-build-failure-message-tp
> 24383868p24383868.html
> Sent from the Hudson users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: color coding of build failure message

Kohsuke Kawaguchi
Administrator

Issue #NNNN discusses adding the annotation support to console output,
much like how changelogs can be annotated by plugins. So hopefully this
will allow colorization, folding, and so on.

Paul Sander wrote:

> I personally find that color-coding log output and email notifications is more trouble than it's worth, particularly if there is some automated analysis done to the log.  Instead, I write a filter to remove the known uninteresting messages from a log.  This leaves the interesting and unexpected output.  The filtered output can in turn have highlighting added if desired.
>
> Keep in mind that color coding makes life more difficult for our color-blind colleagues.  Various email user agents do various ugly things to messages that don't comply strictly with various standards like printable ASCII or RTF that don't explicitly support color or if displayed in windows that don't agree on standard color codes.  That sort of thing should be taylored to the individual users' tastes anyway.
>
>> -----Original Message-----
>> From: sankarr [mailto:[hidden email]]
>> Sent: Tuesday, July 07, 2009 6:08 PM
>> To: [hidden email]
>> Subject: color coding of build failure message
>>
>>
>> Like to request an enhancement to the reporting of failure message for
>> builds. This applies to both email messages and the console
>> output[raw].
>> When there are multiple builds in one Hudson project, it
>> becomes difficult
>> to scan through the whole message log and locate the error.
>> If this is color
>> coded, it will be easier for the recepient to locate the error.
>>
>> We are using Hudson Text finder for reporting build failures.
>> it will be
>> nice to highlight / color code few lines above and few lines below the
>> actual build error.
>>
>> Is there an env variable to limit the number of log message
>> lines that get
>> sent out in email notifications?
>>
>> thanks
>> Sankar
>>
>> --
>> View this message in context:
>> http://www.nabble.com/color-coding-of-build-failure-message-tp
>> 24383868p24383868.html
>> Sent from the Hudson users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
> ---------------------------------------------------------------------
> 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
Reply | Threaded
Open this post in threaded view
|

Re: color coding of build failure message

Michael Donohue
I think Kohsuke meant to include a reference to issue 2137

-Michael
(646) 833-8884


On Wed, Jul 8, 2009 at 8:59 PM, Kohsuke Kawaguchi <[hidden email]> wrote:

Issue #NNNN discusses adding the annotation support to console output,
much like how changelogs can be annotated by plugins. So hopefully this
will allow colorization, folding, and so on.

Paul Sander wrote:
> I personally find that color-coding log output and email notifications is more trouble than it's worth, particularly if there is some automated analysis done to the log.  Instead, I write a filter to remove the known uninteresting messages from a log.  This leaves the interesting and unexpected output.  The filtered output can in turn have highlighting added if desired.
>
> Keep in mind that color coding makes life more difficult for our color-blind colleagues.  Various email user agents do various ugly things to messages that don't comply strictly with various standards like printable ASCII or RTF that don't explicitly support color or if displayed in windows that don't agree on standard color codes.  That sort of thing should be taylored to the individual users' tastes anyway.
>
>> -----Original Message-----
>> From: sankarr [mailto:[hidden email]]
>> Sent: Tuesday, July 07, 2009 6:08 PM
>> To: [hidden email]
>> Subject: color coding of build failure message
>>
>>
>> Like to request an enhancement to the reporting of failure message for
>> builds. This applies to both email messages and the console
>> output[raw].
>> When there are multiple builds in one Hudson project, it
>> becomes difficult
>> to scan through the whole message log and locate the error.
>> If this is color
>> coded, it will be easier for the recepient to locate the error.
>>
>> We are using Hudson Text finder for reporting build failures.
>> it will be
>> nice to highlight / color code few lines above and few lines below the
>> actual build error.
>>
>> Is there an env variable to limit the number of log message
>> lines that get
>> sent out in email notifications?
>>
>> thanks
>> Sankar
>>
>> --
>> View this message in context:
>> http://www.nabble.com/color-coding-of-build-failure-message-tp
>> 24383868p24383868.html
>> Sent from the Hudson users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


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