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

Key: CCNET-137
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Ruben Willems
Reporter: Gunnlaugur Thor Briem
Votes: 0
Watchers: 1
Operations

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

Successful build status indicated on source control failure

Created: 07/Aug/04 07:26 AM   Updated: 25/Jul/10 12:48 PM
Component/s: Builder
Affects Version/s: 0.6.1
Fix Version/s: 1.4.3

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment: Windows 2003 Server, CCNET running as a Windows service, source control is of type multi, containing two vss sourcecontrols configured with autoGetSource="true"
Issue Links:
Relationship
 
This issue Relates to:
CCNET-748 Provide better trigger exception logging Major Closed
CCNET-1113 Proposed changes for handling integra... Minor Closed


 Description  « Hide
In my setup, when the source control fails while checking for modifications, no email is sent and my CCtray just stays green and the CCnet webapp does not indicate any broken build. If the source control keeps failing (e.g. because something (in the ccnet server repository breaks it), then the continuous-integration build is silently broken. That situation is indistinguishable from that in which nothing is being checked in; everything looks green and peachy until I start diving into logs (because I notice that the last CCnet build was the day before yesterday).

The particular failure I'm experiencing this with is from SourceSafe: "Source control operation failed: A writable copy of C:\...\foo.ascx already exists". This appears as a CruiseControlException thrown from ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.Execute(ProcessInfo processInfo)

 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.