For this example, we are going to assume we are using a single Subversion repository for our source control system and we have a job set up to call the ant target "dist".

• Add the following target to your ant build.xml

build.xml

<project name="test-build">
  <property environment="env" />
  <target name="dist">
    <echo message="Building pipeline ${env.CRUISE_PIPELINE_NAME}"
          file="deploy-${env.CRUISE_REVISION}.txt" />
  </target>
</project>

• Now, when Cruise runs the 'my-app' pipeline on revision 123, the file deploy-123.txt will be created, with the following content:

deploy-123.txt

Building pipeline my-app

For this example we are going to assume we are using a Subversion repository containing the code and a Mercurial repository containing configuration scripts.

• Ensure the pipeline materials look like this

<pipeline name="multiple-materials">
  <materials>
    <svn url="..." dest="code" />
    <hg url="..." dest="configuration/latest" />
  </materials>
  ...
</pipeline>

• Add the following target to your ant build.xml

build.xml

<project name="my-app">
  <property environment="env" />
  <target name="dist">
    <echo message="Building pipeline ${env.CRUISE_PIPELINE_NAME}"
          file="deploy-${env.CRUISE_REVISION_CODE}.txt" />
    <echo message="Configuration version: ${env.CRUISE_REVISION_CONFIGURATION_LATEST}"
          file="deploy-${env.CRUISE_REVISION_CODE}.txt"
          append="true" />
  </target>
</project>

• Now, when Cruise runs the 'my-app' pipeline with the code at revision '123' and the configuration at revision '59cab75ccf231b9e338c96cff0f4adad5cb7d335', the file deploy-123.txt will be created with the following content:

deploy-123.txt

Building pipeline my-app
Configuration version: 59cab75ccf231b9e338c96cff0f4adad5cb7d335