color coding of build failure line

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

color coding of build failure line

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.

In the following example log below, I am referring to the line
make[1]: *** [abcd] Error 1

-------------- log -------------------------------------
[views] $ /usr/local/bin/perl /tmp/hudson7865361453634142528.sh
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
Archiving artifacts
Recording fingerprints
[WARNINGS] Parsing warnings in console log...
[WARNINGS] Found 2024 annotations (4 new, 0 high, 2024 normal, 0 low)
[WARNINGS] Not changing build status, since no threshold has been exceeded
Checking console output
/projects/test_hudson/jobs/run/builds/2009-07-02_11-00-18/log:
make[1]: *** [abcd] Error 1
Email was triggered for: Failure
There are 1 triggered emails.
Sending email for trigger: Failure
Reply | Threaded
Open this post in threaded view
|

Re: color coding of build failure line

issue_police
Hi,

This is a friendly reminder that the 'issues' list is only used for
automatic e-mail notification from the issue tracker, and not meant
for interactive discussion. Please request an observer role for the
project and add the comment to the issue, or please redirect your
e-mails to the 'users' list.

(this is an automatically generated message, and if you have a comment
about this bot itself, please contact [hidden email]

----
Java.net issue tracker auto responder

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