Setting up a build

• Create or obtain a build script.
• Create a build definition that identifies a command that invokes the build script.
• Create a build engine object to represent the machine that runs the defined build.
• Start the build engine process on the build machine. The build engine responds to build requests, runs builds, and publishes results.

• Best practices
  This topic describes best practices that help you effectively set up a Jazz build.
• Jazz Build setup variations
  You can use any build engine to run Jazz builds, but you can simplify your build setup by using the Jazz Build Engine. If you plan to use a different build engine, first set up a simple build with the Jazz Build Engine, so that you can learn basic Jazz build concepts. After you have a basic build working, you can optionally migrate to a different build engine, such as the Build Forge® build engine.
• Dedicated build workspaces
  When you create a build definition, you have the option to create a dedicated repository workspace for the build. Dedicated build workspaces enable you to identify changes and work items that go into a build, and to create snapshots of the build source content.
• Creating a build definition
  You can create Jazz build definitions that are based on various build templates, such as Ant, command line, or Maven. This topic describes how to create and configure a command line definition for a build script. If you create a build definition using the other build templates, the steps are similar.
• Creating a build engine
  You can create a build engine to support one or more build definitions. When you create a build definition, if a build engine does not exist, the system automatically creates a default build engine. You can use the default build engine, or create a new one.
• Component load rules
  You can specify component load rules in a build definition on the Jazz source control page, which only displays if you selected Jazz source control as a Pre-Build option when you created the build definition.
• Ant build toolkit
  The Ant build toolkit is a set of Ant tasks that communicate between a build machine and a Jazz repository. The tasks can perform various operations on a build. For example, you can use Ant tasks to update a build result with progress information. Using the toolkit is optional, but it provides several features that are useful to most builds. You can use the toolkit for any build that can invoke Ant. This topic describes commonly used Ant tasks.
• Build properties
  You can define certain build script properties, such as ECLIPSE_HOME, from the properties of the build definition or build engine.

Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug