The ForceBuildPublisher forces a build on a local or remote build server. It uses .NET Remoting to invoke a forced build on the CruiseControl.NET server at the specified URI.
The forced build runs asynchronously, i.e. the ForceBuildPublisher does not wait for the forced build to finish. The ForceBuildPublisher is a great way to help split the build.
For CruiseControl.NET version 1.0 and later, an alternative to the ForceBuildPublisher is the Project Trigger.
The main difference is that the ForceBuildPublisher is placed in the configuration for the primary project, while the ProjectTrigger is is placed in the configuration for the dependent project.
Configuration Example
<publishers>
<forcebuild>
<project>AcceptanceTestProject</project>
<serverUri>tcp://buildserver2:21234/CruiseManager.rem</serverUri>
<integrationStatus>Success</integrationStatus>
<enforcerName>Forcer</enforcerName>
</forcebuild>
</publishers>
Configuration Elements:
| Node |
Description |
Type |
Required |
Default |
Version |
| project |
The CCNet project to force to build |
string |
true |
n/a |
|
| serverUri |
The URI for the local or remote server managing the project to build. The default value is the default URI for the local build server. |
string |
false |
tcp://localhost:21234/CruiseManager.rem |
|
| integrationStatus |
The condition determining whether or not the remoting call should be made.
The default value is "Success" indicating that the specified build will be forced if the current build was successful. Other legal values are "Exception" or "Failure". |
string |
false |
Success |
|
| enforcerName |
Identification of a ForceBuildPublisher. This value is passed to the CCNetRequestSource attribute of the forced project's build.
|
string
|
false
|
BuildForcer |
|
| description |
If filled in, this will be shown in the buildstage as the process name
|
string
|
false
|
n/a |
|
| dynamicValues |
Any dynamic parameters to be used. See Dynamic Parameters |
Dynamic values array - see Dynamic Parameters |
No |
None |
1.5.0 |
