Dashboard > CruiseControl.NET Community > Community > Blog
Blog Log In View a printable version of the current page.

Added by Mike Roberts , last edited by Vivek Arora on Sep 07, 2005  (view change)
Labels: 
(None)

CruiseControl.NET is an excellent tool for accomplishing continuous integration. A difficult part however seems to be configuring the tool by editing the ccnet.config file! Can't we have a GUI wrapping the config file and encapsulating the schema from the end-user? Apologies if I'm missing something and if such a tool is already published then an insight would be appreciated!!!

Viv

I agree. The config files are difficult to work with. At the very least, a proper Schema document so that we can take advantage of VS.NET's intellisense when editing the file.

I am fairly new to Cruise Control and I am trying to upgrade the Cruise Control machines where I work to CC 1.2 and cannot get anything to work.  I have used the windows installer on my local machine, and wanted to run through and test the features before upgrading our true CC machines.  We have read up about the breaking changes and made fixes (as we have seen appropriate) to the ccnet.config file to avert any problems inside the config file.  However after the automated install, I cannot find the web address to connect the CC Tray or the Web Dashboard to despite its auto-set up.  Furthermore when I run the ccservice.exe file, I get the service to run for about 1 second before it automatically shuts down.   How do I:

Fix the service so it doesn't shut down? Find where I should have my web page look to find the default page to display the Web Dashboard?  How do I connect my web browser to the default Farm Report for example? Connect to my local machine with CC Tray so I can take a look at what is running when we finally get the application working correctly? I have read through the upgrade documentation and it is NOT helping whatsoever.  Thank you for your time, Kurt

  1. Before starting to use CCService, make sure that everything is set up and configured correctly using the console executableccnet.exe. It is considerably easier to debug configuration issues using the console version of CCNet than it is using CCService. The console version of CCNet writes its output directly to the console window, so it is much easier to see what the server is doing. CCService, by default, uses the Event Log and the ccnet.log instead.
  2. Once you have ascertained that the CCNet server is working, you need to start by configuring CCService. If you open the ccnet.service.exe.config file, you need to change the value of the ccnet.config setting to point to the location of your ccnet.config file.
  3. Now you are ready to install the service. Installing a................

LOCATION OF DOC: http://confluence.public.thoughtworks.org/display/CCNET/The+Server+Service+Application\\

So the conclusion - read ALL documentation material - it is pretty good and helpful.

I have the same need as Robert.  Could somebody answer it.

Thx

Steve

Hello
 
Would it be possible to ad a "postfix" tag? So that the following format would be possible: 1.0-[buildnumber]-alpha
 
Thank's
Robert Posted by infopex at Feb 28, 2007 02:19

There is a CCnetConfig utility out there. Granted Intellisense would be much appreciated.

http://www.codeplex.com/ccnetconfig

Powered by a free Atlassian Confluence Open Source Project / Non-profit License granted to ThoughtWorks, Inc.. Evaluate Confluence today.
Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators