Running dependency builds on z/OS and IBM i systems
You can save time and resources by setting up dependency builds. Dependency builds include only those items that changed or depend on changes since the last successful team build.
Dependency builds use Rational® Build Agent build engines that run on System z® or IBM® i.
- You must have a Developer for IBM Enterprise Platforms client access license.
- Jazz® Team Server must be running, and the source code data collection service must be enabled. For details, see Source code data collection service.
- The Build System Toolkit must be installed, and Rational Build Agent build engines must be running on IBM Z or IBM i.
- System definitions must be added to the project area in your Jazz repository. System definitions include data set definitions, libraries, language definitions, translators, and search paths, depending on your operating system.
- Source code data scanning must be enabled on your stream.
Dependency analysis modes
- Full analysis
- Engineering Workflow Management analyzes dependencies on all buildable files (or a subset of buildable files) that are found in the specified repository workspace with the associated system definitions and source code data. While a full analysis provides more accurate dependency analysis results, it requires more time.
- Change set analysis
- Engineering Workflow Management analyzes dependencies on the buildable files from the change sets that are added to the repository workspace. The buildable files that are analyzed include those files from the last successful build, as well as those files that are affected by the change sets. A change set analysis is more efficient and requires less time than a full analysis. However, in certain situations, a full analysis must be run. For example, when search paths are changed in a translator, a full analysis is needed.
Dependency resolution rules
By default, the dependency analysis is based on the name and type (
Include for copybooks) of the files in the stream. However, the
dependent file type that is automatically assigned by the dependency analysis might not match the
type of the file it should resolve to. To avoid unresolved dependencies, it is advised to exclude
this matching rule.
To do so, open a web browser and point to
hostname]:9443/ccm/admin. Go to Advanced Properties. Search
for the Ignore file type when searching for dependencies advanced property
and set it to True.