Home
Managing change and releases
Learn how to manage change and release in the product.
Guide to building software on Linux and UNIX
Pointers on using HCL VersionVault build tools
Learn how to use VersionVault build tools.
Using config spec time rules
If you use a UCM view, your config spec is generated by HCL VersionVault. Do not add time rules to your config spec.

Managing change and releases
Learn how to manage change and release in the product.
- Managing software projects
- Workflow for creating projects
- Workflow for making baselines
- Workflow for recommending baselines
- Guide to building software on Linux and UNIX
  - HCL VersionVault build concepts
    HCL VersionVault supports makefile based building of software systems and provides a software build environment closely resembling that of the make program.
  - Derived objects and configuration records
    Learn about derived objects and configuration records.
  - Pointers on using HCL VersionVault build tools
    Learn how to use VersionVault build tools.
    - Running clearmake
      You can run clearmake from the command line or from the VersionVault File Browser (xclearcase).
    - A simple clearmake build scenario
      clearmake is designed to let developers in makefile-based build environments continue working in their accustomed manner.
    - Accommodating build avoidance
      Learn about clearmake build avoidance.
    - Declaring source dependencies in makefiles
      To implement build avoidance based on time stamps, standard make variants require you to declare all the source file dependencies of each build target.
    - Build-order dependencies
      In addition to source dependencies, makefiles also contain build-order dependencies.
    - Problems with forced builds
      Understand the problems with forced builds.
    - How clearmake interprets double-colon rules
      Double-colon rules are a special kind of makefile construct that allows several independent rules for one target, each with a possibly different build script.
    - Continuing to work during a build
      As your build progresses, other developers continue to work on their files and might check in new versions of elements that your build uses.
    - Using config spec time rules
      If you use a UCM view, your config spec is generated by HCL VersionVault. Do not add time rules to your config spec.
      - Inappropriate use of time rules
        It is important to know the correct use of time rules.
    - Build sessions, subsessions, and hierarchical builds
      Learn about HCL VersionVault build auditing.
    - Build auditing and background processes
      If some conditions are met, HCL VersionVault build programs audit background processes correctly.
    - Working with incremental update tools
      The design of the build auditing capability makes it ideal for use with tools that build derived objects from scratch.
    - Adding a version string or time stamp to an executable
      You can incorporate a version string and/or time stamp into a C-language compiled executable using simple techniques.
  - Working with DOs and configuration records
    You can perform operations on derived objects and configuration records.
  - clearmake makefiles and BOS files
    The HCL VersionVault build program, clearmake can process makefiles.
  - Using clearmake compatibility modes
    clearmake is designed for compatibility with existing make programs, which minimizes the changes you need to make to your makefiles.
  - Using HCL VersionVault to build C++ programs
    Use clearmake effectively with C++ programs built with various compilers.
  - Using HCL VersionVault build tools with Java
    The build behavior of Java tools causes various problems for clearmake. Understand the problems and some possible solutions to resolve them.
  - Setting up a parallel build
    Learn the process to set up and run builds that use several hosts in the local area network.
  - Building software for multiple platforms
    Learn how to address the challenge of using a single source tree to develop an application for a variety of hardware and software platforms.
  - Setting up a build on a non-VersionVault host
    There is a technique to create configuration records for a build that involves HCL VersionVault data, but is performed on a non-VersionVault host.
- Guide to building software on Windows

Using config spec time rules

If you use a UCM view, your config spec is generated by HCL VersionVault. Do not add time rules to your config spec.

Using the reference time facility described in Continuing to work during a build, clearmake blocks out potentially incompatible source-level changes that take place after your build begins. For example, if a rule contains a remote branch type and a synchronization takes place during a build, clearmake uses the latest version of the remote files that were checked in before the time lock. If, however, an incompatible change has already taken place, VersionVault allows you to block out recently created versions.

A typical VersionVault development strategy is for each team member to work in a separate view, but to have all the views use the same config spec. In this way, the entire team works on the same branch. As long as a source file remains checked out, its changes are isolated to a single view; when a developer checks in a new version, the entire team sees it on the dedicated branch.

This incremental integration strategy is often very effective. But suppose that the recently checked-in version of another user causes your builds to start failing. Through an exchange of e-mail, you trace the problem to header file project_base.h, checked in at 11:18 A.M. today. You and other team members can reconfigure your views to roll back that one element to a safe version:

element project_base.h .../onyx_port/LATEST -time 5-Mar.11:00

If many interdependent files have been revised, you can roll back the view for all checked-in elements:

element * .../onyx_port/LATEST -time 5-Mar.11:00

For a complete description of time rules, see the config_spec reference page.