Server Application Config File¶
Various aspects of the CruiseControl.NET Server are configured in the application configuration file. The name of this file depends on how you are running the server:- If you are running the Console Application, the application config file is called ccnet.exe.config.
- If you are running the Windows Service Application, the application config file is called ccservice.exe.config
For most installations the default settings in this file will be appropriate.
This file is a standard .NET application config file. Parts of it that are specific to CruiseControl.NET are as follows:
XSL File configuration¶
The section defines what xsl files are included for transforming the build file for reporting behaviour within the server. If you want to include extra xsl files (for example if you have your own build behaviours), then add them here.
Remoting Configuration¶
The CruiseControl.NET Server can open a remoting server port so that other applications in the CCNet suite can communicate with it ([CCTray], [Web Dashboard]). By default CCNet listens on port 21234, but this can be changed under the section.
(i) You'll need to change this value if you want to run multiple CruiseControl.NET servers on 1 machine
Logging Configuration¶
Logging of the Server activities (not the build logs themselves) is implemented using .NET Tracing, and this is configurable in the section of the application config file. In this section you can change log level (the section), and where log data is sent to (the section).
If you are using a in the section, then you can configure the server log file name there. This same file name should be set as the value for the key in the section. This value is used when remote applications request to see the server log file. The number of lines returned from the end of the server log file to the remote application is specified by the value.
warning
Note that with some log levels certain potentially sensitive details may be logged, including source control passwords. Make sure you check your log file and set the log level appropriately.
Service Specific Settings¶
If you are running the console application, you have the option of passing in various arguments on the command line. If however you are using the Service application you can't do this, but there are extra options you can set in the section of the config file, as follows:| Key | Equivalent startup parameter in [The Server Console Application] |
| ccnet.config | config |
| remoting | remoting |
General Configuration Settings¶
The table below describes general configuration settings that are in the appSettings section of the application configuration file.| Key | Description | Default Value |
| WatchConfigFile | Turns on/off monitoring of the ccnet.config file for changes. By default, the CCNet server will monitor this file and will automatically restart the server and reload the updated configuration settings. Setting this value to false will disable this feature. | True |
| PluginLocation | An optional location to search for plugins. The server applications will always look in the application folder for any plugin definitions. This settings allows an extra folder to be specified for plugins. | None |
| DataDrive | The main data drive used by CruiseControl.NET. This is used for checking the amount of free disk space. | C: |
| ShadowCopy | Whether shadow copying should be enabled or not. Shadow-copying is required for hot-swapping, but does have a performance hit (i.e. when the files are copied.) Additionally some older OSs do not allow this option. | On |
| cacheTime | The amount of time (in seconds) a build log will be cached for before it is expired. The minimum allowed value is 10 seconds. | 5 minutes |