Tool Mentor: Building with Rational Team Concert
Create and manage builds.

Synopsis

Builds are created, qualified, and promoted.

Value

Builds should be regularly created and tested against the development stream, and potentially in different test environments.

Pre-requisites

The build evironment must be installed and configured.

1. Install build tools

 See Installing the Build System Toolkit .

2. Learn about build environment

See Getting started with builds and About Rational Team Concert Build

3. Configure build environment

Some important decisions are:

  • Whether builds are automatically scheduled, or triggered, or manually requested.
  • Whether to have a code snapshot for every build
  • Whether to have streams for parallel development or for promoting changes to staging environments such as for "System Test" or "User Acceptance".
See Rational Team Concert Build setup variations.

Configure your build environment.  See A typical Rational Team Concert Build setup and Best practices.

Set up streams and flow rules. See Choosing a stream strategy.  See Creating streams
 and Managing Parallel Development.
If you want a snapshot of the code for each build, see Dedicated build workspaces.

Set up a build.  See Setting up a build.  This includes creating a build definition and a build engine.



Install the Build System Toolkit. Understand the basics of builds.  Decide how to configure your build environment. 

Steps

Perform the following steps.

For more information on this topic, see Building with Rational Team Concdert.

1. Schedule team build

.

See Requesting builds

2. Review build results


See Viewing build status and Viewing build results .

3. Qualify/promote changes

Many oganizations will have various staging environments after development, such as "System Test" or "User Acceptance Test".

Once a build confirms that your code changes work correctly, flow them to the next stages in accordance with your process.

See Understanding and modifying change flows.