History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CCNET-514
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Craig Sutherland
Reporter: Owen Rogers
Votes: 6
Watchers: 5
Operations

If you were logged in you would be able to see more operations.
CruiseControl .NET

Report which task failed through CCTray

Created: 19/Aug/05 04:54 AM   Updated: 25/Jul/10 12:48 PM
Component/s: CCTray
Affects Version/s: 1.0 RC1
Fix Version/s: 1.5.0 CTP

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Issue Links:
Relationship
This issue Relates to:
CCNET-625 Provide more detailed feedback from b... Major Closed
CCNET-158 Ability to tell where in the build pr... Minor Closed
This issue Relates to:
CCNET-1718 breakers are no longer exposed into t... Minor Closed


 Description  « Hide
On 19/08/05, Rory Becker wrote:
> Is it possible to give names to Tasks within Projects so that the
> failing task could be reported within the CCTray tooltip?

 All   Comments   Work Log   Change History      Sort Order:
Owen Rogers [19/Aug/05 04:56 AM]
task names are one option. i've done some work providing a task base class (a la nant) that provides common properties to be inherited by tasks. name is one of them.
however, the simplest thing initially is to come up with some sort of simple summary message describing the failure that can be passed back to cctray via the ProjectStatus DTO.

David Cameron [06/Sep/07 05:59 AM]
All these tasks are about knowing what is happening in the build, and diagnosing failures.

Ruben Willems [28/Apr/09 04:37 AM]
Build status breakdown also shows this info
It should make it rather easy to append the first breaking task to the messages

Craig Sutherland [09/Jun/09 05:16 AM]
Added a message that lists the breaking tasks from the project status snapshot.

pandawood [11/Oct/09 09:51 PM]
This new message seems to be "at the expense of" showing who broke the build?
Was that the intension?

That is, I used to see "Breakers:..." in the CurrentMessage of the XmlStatusReport
After updating to 1.5, instead of seeing breakers, I'm just getting "Failed tasks..."

Ruben Willems [12/Oct/09 01:51 AM]
looking intot his

keeping you posted

Ruben Willems [12/Oct/09 03:25 PM]
http://jira.public.thoughtworks.org/browse/CCNET-1718

it is indeed broken :-(,
fixing it now