Creating source and target builds for promotion
A promotion definition uses source and target dependency build definitions to determine where the source code, build outputs, and build maps will move to or from.
- Create a source dependency build definition for the location
that the source files are saved. You can use one of the following build templates:
- IBM® i Dependency Build - Rational® Build Agent
- z/OS® Dependency Build - Rational Build Agent
- Dependency Build - Rational Build Agent (Deprecated)
- Create a target dependency build definition for the location
where the source files and build outputs will be promoted. Note: The target dependency build definition must be the same build template type as the source dependency build definition. For example, you cannot use a z/OS Dependency Build - Rational Build Agent for your source definition and Dependency Build - Rational Build Agent (Deprecated) for your target definition.The target dependency build definition will likely be identical to the source dependency build definition except for the build workspace and a different data set prefix (the high-level qualifier) on z/OS systems or library on IBM i systems.
- Build the source by requesting a build using the source dependency build definition.