[#CCNET-1228] Report "internal error" in project report, or provide dashboard access to logfile.

CruiseControl .NET

Report "internal error" in project report, or provide dashboard access to logfile.

Created: 25/Aug/08 09:40 AM Updated: 25/Aug/08 11:13 AM

Component/s:

None

Affects Version/s:

1.4

Fix Version/s:

None

Original Estimate:	Unknown	Remaining Estimate:	Unknown	Time Spent:	Unknown
Environment:	Windows Server 2003

Description

« Hide

I switched a CCnet server from using my own domain account to a restricted user, but forgot about path issues. My builds would silently fail as they could no longer find Subversion (svn.exe).

I edited my .config to use the full path, but got another error, the restricted user didn't have access to that executable.

Both of these errors showed up as "INTERNAL ERROR"s in the ccnet.log:

2008-08-25 10:27:25,406 [my-project:ERROR] INTERNAL ERROR: Unable to execute file [C:\Program Files\Subversion\bin\svn.exe]. The file may not exist or may not be executable.

Despite this error, the builds themselves still showed green, though the "last build" time wasn't being updated.

It would be great if these sorts of internal errors could actually break the build and show up in the dashboard, instead of being kinda silent things.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Ross Patterson [25/Aug/08 11:07 AM]

The server log is already available from the dashboard. On the Servers and Project Report pages, there's a "View Server Log" link in the left-side navigation pane.

[ Permlink | « Hide ]

Ross Patterson [25/Aug/08 11:13 AM]

I think in this case, there was no build to fail. CCNET doesn't start a build until it decides that the trigger conditions exist, and that may include checking for modifications, which is where I expect this blew up. I agree that there should have been some place for you to recognize that something was wrong (besides the aforementioned server log), but right now there isn't.