Hi indeed this was added in 1.6, http://confluence.public.thoughtworks.org/pages/createpage.action?spaceKey=CCNET&title=CCNET-1902&linkCreation=true&fromPageId=36536835
with kind regards Ruben Willems On 2 September 2011 12:41, Sam <[email protected]> wrote: > Hi, > > On CCNet version 1.6.7981.1, if I try to force a build on a stopped > project from either the Dashboard or from the CCTray application, I > get the following: > > There was an exception trying to carry out your request. > > Exception Message > > Request processing has failed on the remote server: Project is > stopping / stopped - unable to start integration > > Exception Full Details > > ThoughtWorks.CruiseControl.Remote.CommunicationsException: Request > processing has failed on the remote server: > Project is stopping / stopped - unable to start integration > at > > ThoughtWorks.CruiseControl.Remote.CruiseServerClient.ValidateResponse(Response > response) > at > ThoughtWorks.CruiseControl.Remote.CruiseServerClient.ForceBuild(String > projectName, List`1 parameters, BuildCondition condition) > at > ThoughtWorks.CruiseControl.Remote.CruiseServerClient.ForceBuild(String > projectName, List`1 parameters) > at > > ThoughtWorks.CruiseControl.WebDashboard.ServerConnection.ServerAggregatingCruiseManagerWrapper.ForceBuild(IProjectSpecifier > projectSpecifier, String sessionToken, Dictionary`2 parameters) > at > > ThoughtWorks.CruiseControl.WebDashboard.Dashboard.VelocityProjectGridAction.ForceBuildIfNecessary(IRequest > request) > at > > ThoughtWorks.CruiseControl.WebDashboard.Dashboard.VelocityProjectGridAction.GenerateView(ProjectStatusListAndExceptions > projectStatusListAndExceptions, String actionName, ICruiseRequest > request, IServerSpecifier serverSpecifier) > at > > ThoughtWorks.CruiseControl.WebDashboard.Dashboard.VelocityProjectGridAction.Execute(String > actionName, IServerSpecifier serverSpecifier, ICruiseRequest request) > at > > ThoughtWorks.CruiseControl.WebDashboard.Plugins.ServerReport.ServerReportServerPlugin.Execute(ICruiseRequest > request) > at > > ThoughtWorks.CruiseControl.WebDashboard.MVC.Cruise.ServerCheckingProxyAction.Execute(ICruiseRequest > cruiseRequest) > at > > ThoughtWorks.CruiseControl.WebDashboard.MVC.Cruise.CruiseActionProxyAction.Execute(IRequest > request) > at > > ThoughtWorks.CruiseControl.WebDashboard.MVC.Cruise.ExceptionCatchingActionProxy.Execute(IRequest > request) > > I believe that in CCNet version 1.4, you could force build a stopped > project just fine, and after the build completes, the project would be > in the Running (started) state. > > So, is this a bug? It seems like this was intentionally added in CCNet > 1.6, given that there is a new CommunicationsException class. > > Cheers, > ~Sam. > > On Aug 31, 2:21 pm, Ruben Willems <[email protected]> wrote: > > Hi > > > > From head : stopping a project will prevent any triggers to make a build > > happen, > > it will not prevent a force build. > > > > with kind regards > > Ruben Willems > > > > On 8 July 2011 10:21, JayFleming <[email protected]> wrote: > > > > > > > > > > > > > > > > > Hi all, > > > > > I just want to check that this what I should expect to be seeing... > > > We have a project (with a ForceBuild setting on a nightly schedule > > > trigger) that has been stopped due to the project being locked down at > > > the end of release...however on forcing a build from the dashboard > > > this morning, two build runs were completed. It looks like CCNet > > > performed the force build as well as the scheduled build that it > > > "missed" last night...is this expected? > > > > > Surely a stop should result in builds being queued as well as run, the > > > current behaviour seems more like a "pause" than a "stop"? > > > > > Cheers, > > > Jay >
