Understanding the Build Process

If you use the Build Specification build style with your project you can create the programs and other objects in that project using this build process.

Briefly, the build process takes a description of the objects you need to create and the order in which they need to be created and runs the commands required to create those objects. Since the process understands what objects are affected by changes in the project it creates only those objects which need to be created leaving other objects alone.

The description of the objects you want to create is captured in a build specification. This build specification is an XML document that is edited with the IBM® i build specification editor. You will have one of these for each project.

Team builds are driven from a build definition that is defined for a build workspace in the repository. The build definition describes the environment in which the build specification will be processed. Individual developer builds are submitted from your local workspace and use the parameters defined in the build style for the project instead of those defined in the build definition.

When you submit a team build, the build engine takes this build specification, along with parameters from the build definition, and creates an intermediate file which is then executed. This file contains a lower-level description of the commands and dependencies that you defined in the build specification which are suitable for running the build. Running the build produces all the objects that must be created or updated. It also produces a log file describing exactly the steps that the build went through to create those objects.

Please refer to Jazz™.net for more information.


Feedback