Skip to content


Subversion checkout URL

You can clone with
Download ZIP
CCNet Extensions for
C# Visual Basic C++ JavaScript

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.


CCNet Extensions

These extensions use Amazons AWS services and BuildMachine.Net services. The project is used to improve integration of CCNet with BuildMachine.Net. Please see http://www.BuildMachine.Net for more information.

Built against CCNet 1.6

Assembly file:

Copy into ccnet or plugin folder under ccnet to use.

See Sample.CCNET.config for sample usages

Update your ccnet.exe.config to point the plugin location to the build output (or have the build copy the dll to the ccnet plugin folder)

<add key="PluginLocation" value="S:\...\AnalysisUK.BuildMachine.CCNetExtensions\bin\Debug"/>

Start ccnet from command line using the StartCCNET.bat file in the solution folder, this uses the Sample.CCNET.config file.

Attach to the CCNET process.


WebServiceLabeller - Gets the label from a BuildMachine.Net webservice.
SimpleDBLabeller - Gets the label from a SimpleDB Database

S3BuildPublisher - Publishes builds to S3

SnsPublisher - Creates a build notification

SimpleDBState - Stores CCNet state in a SimpleDB database
WebServiceState - Stores CCNet state using a BuildMachine.Net webserivce

SqsTrigger - Triggers a build when a message is places on a AWS SQS queue.


Requires Amazon AWS Access Key, Secret key and SQS queue Url to be set in the ccnet.config (see Sample.CCNET.config) file.

To Create a SQS queue use the build.proj file (See "Using Build.proj file with AWS" notes below).

The create the Queue:
MSBuild build.proj /t:CreateTestQueue

To test the queue trigger use:
MSBuild build.proj /t:SendSQSMessage

Sample usage:

  <name>Sample SQS Triggered Project</name>

      <awsAccessKey>** Your Access Key here **</awsAccessKey>
      <awsSecretAccessKey>** Your Secret Access Key here</awsSecretAccessKey>
      <queueUrl>** Your aws SQS Queue Url here **</queueUrl>

Using Build.proj file with AWS:
When first using the build.proj file for use with AWS you need to store your AWS keys using the StoreKeys target, setting the AwsAccessKeyId and AwsSecretAccessKey, this stores the keys in a encrypted container on the machine. 
The keys can then be removed from the build.proj file so you don't accidentally check them into source control.

To store keys:
MSBuild build.proj /t:StoreKeys
Something went wrong with that request. Please try again.