TeamCity
 
You are viewing the documentation for an earlier version of TeamCity.

Configuring Build Steps

Last modified: 20 November 2020

When creating a build configuration, it is important to configure the sequence of build steps to be executed.

Build steps are configured in the Build Steps section of the Build Configuration Settings page. Here, you can:

  • add new steps manually;

  • autodetect steps by scanning the source VCS repository;

  • copy and delete steps;

  • temporarily enable/disable steps.

Each build step is represented by a build runner and provides integration with a specific build or test tool. For example, call a NAnt script before compiling VS solutions. You can add as many build steps to your build configuration as needed.

Build steps are invoked sequentially.

The decision whether to run the next build step may depend on the exit status of the previous build steps, the current build status, or execution conditions.

The build step is considered failed if (1) the build process returned a non-zero exit code and (2) the "Fail build if build process exit code is not zero" build failure condition is enabled (see Build Failure Conditions ); otherwise, the build step is considered successful.

Note that the status of a build step and the build itself can be different. All build steps can be successful, but the build can fail because of another build failure condition – not based on the exit code (like failing a test). On the other hand, if a build step has failed, the build will fail too.

Concepts