Configuring Build Steps

Skip to end of metadata
Go to start of metadata
You are viewing documentation of TeamCity 6.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.
Search

Searching TeamCity 6.0.x Documentation

Table of Contents

When creating a build configuration it is important to configure the sequence of build steps to be executed. Each build step is represented by a build runner and provides integration with a specific build or test tool. You can add as many build steps to your build configuration as needed. For example, call a NAnt script before compiling VS solutions.

Build steps are invoked sequentially. If a build step fails the rest are not executed.
A build step failure can be caused by:

  • A build process has returned exit code other than 0, and Fail build if condition "build process exit code is not zero" is enabled in the General Settings of build configuration. (This behaviour doesn't apply to NUnit, MSTest, FxCop, Duplicates (.NET) runners).

In the end, the build gets merged status and the output goes into the same build log.
For the details on configuring individual build steps, refer to:



See also:

Concepts: Build Runner

Labels:

build build Delete
configuration configuration Delete
runner runner Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.