Skip to main content
Version: QB12

Working with ClearCase

Specify cleartool command location​

QuickBuild utilizes the cleartool command to interact with ClearCase. If this command is not in system path, you will need to specify location of the command by configuring ClearCase plugin as below:

Further more, Cleartool location can be specified on a per-node basis by following below steps:

  1. Open ClearCase plugin setting page and define the cleartool path property as:

    ${node.getAttribute("cleartoolPath")}

  2. For each node that does not have cleartool on system path, define the user attribute cleartoolPath to point to the actual cleartool path like below:

Please note that in above example, the cleartoolPath user attribute is just for demonstration purpose. You can use any other user attribute name.

Proof build support​

For general concept of proof build, refer to proof build. Here we explain how to set up ClearCase repository to support proof build.

Test proof build as administrator​

Since proof build set up is a bit tricky, we first set up proof build for the administrator account and make sure it works before we proceed to enable it for all developers. To set up proof build for administrator, please follow below steps:

  1. Login as administrator and download user agent by switching to My tab.
  2. Install and start user agent on your own desktop. For testing purpose, please start the agent as a foreground process. On windows, this can be done by running agent.bat ; on Unix platforms, this can be done by running agent.sh console
  3. Set up a test configuration on QuickBuild server, define a ClearCase repository, and enable the proof build option in advanced section like below:
  4. Make sure the cleartool command exist in the system path of both server machine and your desktop. If not, please follow the section Specify cleartool command location to tell QuickBuild location of cleartool command.
  5. Add a repository/checkout step into step execution graph and have it checkout from the repository defined above.

Now proof build has been enabled for your account, please try to checkout and edit some file inside the local view path specified above, and then run the test configuration. If set up correctly, your local change will be picked up and reflected in the build result. A local change tab will also appear to display your uncommitted changes after build finishes. Your uncommitted changes will be committed automatically if build is successful.

Enable proof build for all developers​

Now that we have a concept of how proof build works. In order to get proof build works for all developers, we need to parameterize various proof build properties, so that different properties can be used for different developers. To do this, you will need to:

  1. Define configuration variables like below:

  2. Script various properties in proof build section to make use of above variables like below:

    Property NameProperty Value
    Local View Path${vars.get("localViewPath")}
    Update Conditionvars.get("update").asBoolean()
    Checkin Conditionbuild.successful && vars.get("commit").asBoolean()
    Checkin Comment${vars.get("comment")}

In this way, various proof build properties will be prompted when your developer run the build. Once they've been input by your developer for the first time, the values will be remembered for subsequent triggers for that user.

At last we suggest to set up the configuration to enable concurrent builds so that multiple builds in the same configuration can run concurrently. This is vital to get fast feedback in case multiple developers are requesting proof builds in the same time.

Limitations​

Please be aware of below limitations when use this repository:

  1. Directory operations, file deletions and file renamging in ClearCase are not detected as changes due to limitation of the cleartool command.
  2. Newly branched files are detected as added files.
  3. Changes are only detected on current branch. For example, if file1 goes through version main/2 , main/3 , main/branch1/1 , main/branch1/2 between two builds, only changes for main/branch1/1 and main/branch1/2 are detected.
Last updated on