If you do not have existing build tools or scripts, learn about build basics and write at least one simple build script before you attempt to set up a Jazz-based build.
The Build System Toolkit contains the Jazz Build Engine and a toolkit of Ant tasks called buildtoolkit. Jazz Build Engine is a continuous build loop that runs builds on a build machine. The Jazz Build Engine performs three primary functions:
You do not have to use the Jazz Build Engine to perform these functions if you have another build system or engine that you prefer to run your builds. Tasks in the buildtoolkit can perform each of these functions. Typically, you can invoke the buildtoolkit tasks from your selected build engine or within your build scripts. You can use buildtoolkit tasks to perform various tasks, including getting the next build request, starting a build, completing a build, and publishing logs.
You can find an example build script that does not use the Jazz Build Engine at installdir/buildsystem/buildtoolkit/examples/standalone, where installdir is the Build System Toolkit installation directory .
The Jazz Team Build uses a build request queue for request processing. A request gets in the queue in one of the following ways:
In most scenarios, the Jazz Build Engine and the getNextRequest task handle these two requests the same way.
When you set up a build that does not use the Jazz Build Engine, you need to create build definition and build engine objects in Rational Team Concert™. When you create the build definition, you typically select the Generic template. If you do not plan to use the Jazz scheduler, you should not include the Schedule configuration when you create the build definition. If you do not plan to process Jazz Team Build requests, when you create the build engine, in the Build Request Processing section, clear the Build engine process polls for requests check box.
Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug