I've tracked down why builds appear out or order on the
webdashboard... well nearly, I still need some help...
- if you 'touch' a build log file ( rename the file and rename it back
again ) this causes builds to appear out of order. ( Perhaps having
our buildlogs unprotected (r/w) on a network drive have been touched
inadvertently by other users. )
Trying to track this down I get to this code below, which I have
modifed and expanded to make clearer...
I cannot step into this code, but this is where it gets the log files
out of order...
cruiseManager.GetBuildNames(projectSpecifier.ProjectName)
Can anybody shed any light on this?...
a) Why can't I step into this code.
b) Why are the buildnames ordered by access time / modifed time?
c) What would be a solution to this - I might be able to do to get
this working - sure I could sort buildnames but will that cause other
issues?
Here is the culript...
WebDashboard\ServerConnection\ServerAggregatingCruiseManagerWrapper.cs
namespace ThoughtWorks.CruiseControl.WebDashboard.ServerConnection
{
public class ServerAggregatingCruiseManagerWrapper :
ICruiseManagerWrapper, IFarmService
public IBuildSpecifier[] GetBuildSpecifiers(IProjectSpecifier
projectSpecifier)
{
ICruiseManager cruiseManager = GetCruiseManager(projectSpecifier);
String[] buildNames = cruiseManager.GetBuildNames
(projectSpecifier.ProjectName);
return CreateBuildSpecifiers(projectSpecifier, buildNames);
}
Your help greatly appreciated,
Spurtus. ( CCNet version : 1.4.3.4023 )
