Help documentation

Quick pipeline setup

Introduction

After you've entered your license information, clicking on the Current Activities tab will take you to the "Add new pipeline" page.

There are only four things you must choose on this screen. They are:

  1. Your pipeline name
  2. Your pipeline group
  3. Which builder you want to use (Cruise supports Ant, NAnt and Rake natively, and can run any other command using the Exec builder)
  4. Your Source Control Management (SCM) type (currently Cruise supports Subversion, Mercurial, Git and Perforce)
  5. Your SCM details. Refer to the Configuration Reference section for more details.

See the Managing pipelines documentation for editing these settings following the creation of your pipeline.

Pipeline group settings

Pipeline group is used to group multiple pipelines together. You can specify permissions based on pipeline group. Please refer to enabling security for more information.

Builder settings

You cannot customize the working directory using the quick pipeline setup. To do this you will need to edit the configuration manually on the Administration screen.

Exec builder

The Exec builder allows you to run any command present in the command line. You need to enter the command to run.

Ant builder

The ant builder allows you to run an ant script. Cruise does not include Ant and so you must ensure that it is already on the command path. By default it will use build.xml in the agent's working directory as the build file. If you want to customize the build file or build target, click the edit link to change the defaults.

NAnt builder

The NAnt builder allows you to run a NAnt script. Cruise does not include NAnt and so you must ensure that it is already on the command path. By default it will use default.build as build file in the agent's working directory. If you want to customize the build file or build target, click the edit link to change the defaults.

Rake builder

The Rake builder allows you to run a ruby rake build. Cruise does not include ruby or rake and so you must ensure that it is correctly installed on the agents. Cruise will assume the standard rakefile exists in the working directory of the agent.