Help documentation

Quick pipeline setup

Introduction

After you've entered your license information, clicking on the Pipelines tab will take you to the "Add new pipeline" page. You can also add a pipeline by clicking the

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

  1. Your pipeline name
  2. Your pipeline group
  3. A task you want this pipeline to execute. If you use Ant, NAnt or Rake for scripting, Go provides convenience wrappers for these tools. To use any other scripting tool (e.g: Maven, msbuild, etc.), use the "Custom Command" option to specify the command line syntax for that tool.
  4. Your Source Control Management (SCM) type (currently Go supports Subversion, Mercurial, Git and Perforce). Refer to the Configuration Reference section for more details.

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

Initial task settings

Custom Command

The Custom Command task allows you to run anything on the command line. You need to enter the command to run.

Ant

The Ant task allows you to run an ant script. Go 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.

For this option to work, Ant needs to be installed on the Go Agent(s) and executable by it.

NAnt

The NAnt task allows you to run a NAnt script. Go 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.

For this option to work, NAnt needs to be installed on the Go Agent(s) and executable by it.

Rake

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

For this option to work, Rake needs to be installed on the Go Agent(s) and executable by it.

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.

Also See