Requesting dependency, personal, and preview builds

You can change build properties, request a build preview, and request a personal dependency build that is isolated from your team build and that runs on a workspace that you specify.

Before you begin

Restriction: You can request a preview build or a personal build, but not both.
An administrator can change the personal dependency build options in Jazz™ Team Server. For more information, see Setting up personal dependency build options.

About this task

If you use z/OS® system, you can also request a dependency build from the Engineering Workflow Management Interactive System Productivity Facility (ISPF) client. For more information, see Managing source code with the ISPF client.

Procedure

  1. In the Team Artifacts view, expand the project folder.
  2. Expand the Builds node, right-click the build definition, and select Request Build. The Request Build wizard opens.
  3. Optional: If you do not want to use the default build engine, expand Build Options and select the build engine to run the build with.
  4. Optional: To indicate a user name and password for the build, expand Build Agent Authentication Override. For more information about build agent authentication, see Security for the Rational Build Agent.
  5. Expand Dependency Build Options.
    Note: If you have been using either the full or binary rebuilds for dependency builds, note that these options are no longer available.
    • Select either Build workspace or Build subset.
    • Optional: To build only those items that changed since the last successful build, select Build changed items only.
    • To request a personal build that does not impact the build definition status and that runs on a repository workspace that you specify, do these steps:
      • Select the Personal Build check box. The personal build options are enabled.
      • In the Repository workspace field, browse to the repository workspace where you checked in the changes that you want to build.
      • Type the load directory and resource prefix in the appropriate fields.
      • Optional: If an HFS build is enabled in the build definition, you need to specify an HFS output directory to the personal build.
      • Optional: Select Perform full minimum load to load all items to your personal build resource that recently changed or that depend on items that changed since the last successful build.
      • If you request an IBM® i personal build, either select or clear the Append load and object libraries from the build definition check box.
    • Optional: If you want to see a preview of the build, select Preview build. A preview is only a preview. Nothing is actually built.
  6. Optional: To modify the library list that this build uses, expand Build Properties and add a search path build property. The build properties that you specify override any build properties that you specified in the build definition or build engine.
    Note: You cannot change required build properties. You specify required build properties when you define a build.
    You can use the following properties:
    team.enterprise.build.dependency.forceChangeSetAnalysis
    This property forces change set analysis when it is possible. Change set analysis looks at the list of files that have changed since the previous successful team build and their impacts, in order to build them. if this property is set to true and if the previous build used a subset, then a full analysis will not be performed. It implies that some programs, which are not in the scope of the first subset, might not be rebuilt. It can be a desired behavior for the use case of managing partial impacts with a subset.
    team.enterprise.build.dependency.forceFullAnalysis
    This property forces a full analysis upon the preprocessing. It should be used only when you want to resynchronize code changes and binary files. Such is the case, for example, after several subset builds and the use of the team.enterprise.build.dependency.forceChangeSetAnalysis property.
    team.enterprise.build.forcelocal
    With this property, the build generates a macrodef.xml file that uses Ant local variables. It requires a build toolkit from Rational Team Concert™ 6.0.1 or later, which contains a version of Ant that supports local variables. It is useful to generate a more readable Ant script. It is recommended to set this property if you meet the requirements.
    team.enterprise.build.ignoreBuildPathChanges
    If this property is set to true, there will be no rebuild after your SYSLIB is augmented. It is useful when a dependency set calculation detects unresolved files because their paths have changed.
    team.enterprise.build.ignoreAlwaysLoadDuringFullAnalysis
    With this property, all the files of the stream are not scanned upon a full analysis. A full analysis always occurs when a subset is used during a build. You should use this property if you never use the Always Load properties on the files in your stream.
    repositoryAddress
    This property sets the address of the server that is used by the build process. It is useful if you run the server on a machine that is not accessible by a DNS entry. Therefore, you provide the IP address as https://[fully qualified hostname]:9443/ccm.
  7. In the After submitting the request field, indicate whether to show builds of the requested type, show build queue, or do nothing.
  8. Click Submit.

Results

After you click Submit, a Builds view shows information about the build.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki