CruiseControl.NET : BitKeeper Source Control Block
This page last changed on Sep 11, 2008 by williams.
BitKeeper Configuration Examples
example using bkd
<sourcecontrol type="bitkeeper"> <workingDirectory>c:\build\dev-1.0</workingDirectory> <autoGetSource>true</autoGetSource> <cloneTo>..\Source</cloneTo> </sourcecontrol>
Configuration Elements
| Node | Description | Type | Required | Default |
|---|---|---|---|---|
| executable | Absolute, DOS-style, path to bk.exe | string | false | c:\Program Files\BitKeeper\bk.exe |
| workingDirectory | Absolute, DOS-style, path to permanent BK repository | string | true | none |
| autoGetSource | Automatically pull latest source into permanent BK repository | bool | false | true |
| tagOnSuccess | Add BK tag on successful build | bool | false | false |
| cloneTo | Make a clone of the permanent BK repository into the designated path | string | false | none |
| fileHistory | Include history of each file, rather than just ChangeSets | bool | false | false |
| timeout | Sets the timeout period for the source control operation. See Timeout Configuration for details. | Timeout | 10 minutes | false |
| issueUrlBuilder | Converts the comment (or parts from it) into an url pointing to the issue for this build. See Issue Builder for more details |
Group | N/A | false |
 | SSH Access Not Supported Your permanent BK repository must have a parent accessed via bkd or the local filesystem; ssh access is not supported at this time. |
Contributions
- BitKeeper support added by Harold L Hunt II of StarNet Communications Corp.
