Jump to main content
HCL Logo Product Documentation
Customer Support Community
Customer Support HCLSoftware U Community Forums Customer Idea Portal
DevOps Code ClearCase version 11.0.0
  1. Home icon
  2. Welcome
  3. Managing change and releases

    Learn how to manage change and release in the product.

Product logo

  • Overview

    Learn general information about the product.

  • Installing

    Learn how to install the product.

  • Upgrading and migrating

    Learn how to upgrade and migrate data for the product.

  • Administering

    Learn how to administer the product.

  • Developing

    Learn how to develop software with DevOps Code ClearCase® and ClearCase Remote Client.

  • 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
    • Guide to building software on Windows
  • Integrating

    Learn how to integrate DevOps Code ClearCase® with other products.

  • Tutorials

    Complete tutorials with specific learning objectives for the product.

  • Extending product function

    Learn how to extend the product.

  • Reference

    Review reference information for the product.

  • Glossary
 Feedback

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
  • DevOps Code ClearCase® Guide to Building Software (Linux/UNIX)
  • DevOps Code ClearCase® Guide to Building Software (Windows)
  • Managing software projects
  • Managing software projects
  • About the project manager and project integrator help
  • Creating the directory structure
  • Associating child activity records with a parent activity record
  • Assigning state types to the states of a record type
  • Setting up the base ClearCase integration with Rational ClearQuest
  • About integrating changes
  • Adding DevOps Code ClearCase definitions to a Rational ClearQuest schema
  • The construct_version method source code
  • Creating and using a test element
  • About Diff Merge
  • Creating a new type manager
  • Creating a test element type
  • Other applications of element types
  • Processing files by element type
  • Element types and type managers
  • Using element types to configure a view
  • Writing a type manager program (Linux or the UNIX system)
  • Exit status of a type manager method
  • About element types and file processing
  • File types in a typical project
  • How element types are assigned
  • Icon use by GUI browsers
  • Predefined and user-defined element types
  • Predefined and user-defined type managers
  • How merging works
  • Installing triggers in a VOB on Linux and the UNIX system
  • Setting policies and installing triggers in a DevOps Code ClearCase VOB
  • Common merge scenarios
  • All project work isolated on a branch
  • All project work isolated in a view
  • Using the command line to merge elements
  • Merging directory versions
  • Merging all project work
  • About the Merge Manager
  • Merging a new release of an entire source tree
  • Using the GUI to merge elements
  • Using other merge tools
  • Removing the contributions of some versions
  • Selective merge from a subbranch
  • The construct_version method
  • The create_version method
  • Using different paths or different scripts
  • Using the same script
  • Type manager for manual page source files
  • Creating the type manager directory
  • Implementing a new compare method
  • Inheriting methods from another type manager
  • Script for compare method
  • Testing the type manager
  • About the Version Tree Browser
  • Enabling and disabling automatic associations
  • Using automatic associations
  • Handling an incomplete posting
  • Requesting confirmation of batch completion
  • About code page conversion
  • Configuration parameters for code page conversion
  • The integration code page conversion process
  • The contents of the configuration file
  • Checklist of configuration steps
  • Configuration file use and format
  • Locating the configuration file
  • Overview of the configuration file
  • Summary of configuration parameters
  • Using a shared configuration file and triggers
  • Connecting DevOps Code ClearCase clients and a Rational ClearQuest user database
  • Policy regarding customization and support
  • Defining the Rational ClearQuest user database and database set
  • Debugging and analyzing operations
  • Generating operational information
  • Controlling logged output
  • Producing timing information
  • Defining a batch
  • Editing the configuration file
  • Establishing the Rational ClearQuest Web interface
  • About locally stored information
  • About the Integration Query wizard
  • Establishing DevOps Code ClearCase MultiSite support
  • Overview of the base ClearCase integration with Rational ClearQuest
  • About the configuration file
  • How the integration works
  • About the integration package
  • About enabling a VOB and installing triggers
  • What the integration does
  • Enhancing performance
  • Customizing the integration
  • Planning for the base ClearCase integration with Rational ClearQuest
  • Forcing checkin success before committing associations
  • Allowing use of the graphic user interface (GUI)
  • Allowing multiple associations
  • Controlling query usage
  • Making policy choices
  • Using the association batch feature
  • Controlling and using automatic associations
  • Specifying associations in comment patterns
  • Quick start for evaluations
  • Query support
  • Establishing the schemas
  • Overview of DefineCQSchema
  • Sharing a CQSchema
  • Setting up the Rational ClearQuest user database for base ClearCase
  • Testing the integration
  • Testing the configured connections
  • Troubleshooting the configured connections
  • Tuning automatic association features
  • About trigger versions
  • About defining project views
  • Config spec include files
  • Defining project views
  • Default config spec
  • How config specs work
  • Project environment for sample config specs
  • The standard configuration rules
  • Omitting the standard configuration rules
  • Views for project builds
  • View that uses results of a nightly build
  • Variations that select versions of project libraries
  • View that selects versions that built a particular program
  • Configuring the makefile
  • Fixing bugs in the program
  • Selecting versions that built a set of programs
  • View that selects versions of application subsystems
  • Views for project development
  • View to implement multiple-level branching
  • View to modify an old configuration
  • Omitting the /main/LATEST rule
  • Variation that uses a time rule
  • View for new development on a branch
  • View to restrict changes to a single directory
  • View that uses a time rule
  • Sharing config specs among Linux, the UNIX system, and the Windows system
  • Config spec compilation
  • Paths in config spec element rules
  • Path separators
  • Pitfalls for development of using attributes to select versions
  • Historical view defined by a version label
  • Historical view defined by a time rule
  • View that shows changes of one developer
  • Views to monitor project status
  • View that uses attributes to select versions
  • Comparing baselines
  • About building components
  • Building and testing the components
  • Integrating changes
  • About base DevOps Code ClearCase project management
  • Branches and DevOps Code ClearCase MultiSite
  • Branch names
  • Managing projects in base ClearCase
  • Creating and populating VOBs
  • Creating shared views and standard config specs
  • Using attributes, hyperlinks, triggers, and locks
  • Global types
  • Generating reports
  • Using labels
  • Implementing development policies
  • Integrating changes
  • Planning a branching strategy
  • Setting up the project
  • Recommendations for view names
  • About using DevOps Code ClearCase throughout the development cycle
  • Using DevOps Code ClearCase throughout the development cycle
  • Integration and test
  • Creating baseline 1
  • Creating Baseline 2
  • Final validation: creating Release 2.0
  • Development begins
  • Creating branch types
  • Creating, configuring, and registering views
  • Creating standard config specs
  • Creating project views
  • Project manager and DevOps Code ClearCase administrator
  • Development strategy
  • Use of branches
  • Fixing a final bug
  • Techniques for isolating your work
  • Labeling sources
  • Labeling sources
  • Decommissioning the major branch
  • Restricting use of the main branch
  • Merging from the major branch
  • Merging from the r1_fix branch
  • Integration and test
  • Merging ongoing development work
  • Preparing to merge from the major branch
  • Merging two branches
  • Merging work
  • Project overview
  • Rebuilding from labels
  • Removing the integration view
  • Setting up the test view
  • Wrapping up the project
  • About implementing project development policies
  • Associate changes with change orders
  • Associate project requirements with source files
  • Implementing project development policies
  • Deny access to project data when necessary
  • Good documentation of changes is required
  • Isolate work on release bugs to a branch
  • Label all versions used in key configurations
  • Avoid disrupting the work of other developers
  • Notify team members of relevant changes
  • Prevent use of certain commands
  • Certain branches are shared among DevOps Code ClearCase MultiSite sites
  • Sharing triggers among different types of platform
  • All source files must meet project standards
  • All source files require a progress indicator
  • DevOps Code ClearCase integrations with Rational ClearQuest
  • Managing coexisting integrations
  • Presentation
  • Schema usage with both integrations
  • Understanding the DevOps Code ClearCase integrations with Rational ClearQuest
  • Branching and creating views
  • Using components to organize files
  • Creating and using baselines
  • Differences between UCM and base ClearCase
  • Managing activities
  • Enforcing development policies
  • Choosing between UCM and base ClearCase
  • About the Compare Baselines window
  • Creating and maintaining credentials for Rational ClearQuest database sets
  • About creating feature-specific development streams
  • Creating a feature-specific development stream
  • About deleting activities
  • About deleting baselines
  • About deleting components
  • About deleting projects
  • About deleting streams
  • Description specification
  • Undoing a deliver operation
  • Fixing problems in baselines
  • Fields specification
  • Help files
  • Interface specification for All_Views.prl
  • Importing directories and files from outside DevOps Code ClearCase version control
  • Locking the shared stream
  • Locking and making obsolete the project and streams
  • About making a baseline
  • Making baselines of newly populated components
  • Parameter choosers
  • Parameters specification
  • Bootstrap projects
  • Composite baselines in component-oriented projects
  • Component-oriented Projects
  • Release-oriented projects
  • E-mail notification postoperation trigger script
  • Rightclick specification
  • Using DevOps Code ClearCase Reports (Windows systems only)
  • Configuring shared report directories
  • Customizing DevOps Code ClearCase Reports
  • Default directory structure for DevOps Code ClearCase Reports
  • Date/time chooser
  • Example 1: Adding a column to report output
  • Interface specification
  • Modified report procedure
  • Processing logic
  • Example 2: changing directory organization, description, and output
  • Interface specification
  • Modified report procedure
  • Processing logic
  • Example 3: changing description, parameter types, and output
  • Interface specification
  • Modified report procedure
  • Processing logic
  • Example 4: changing the pop-up menu for right-click handling
  • Changes required
  • Interface specification
  • Modified report procedure
  • Example 5: adding a new command to Report Viewer pop-up menu
  • Interface specification
  • Modified report procedure
  • field_type conventions
  • How DevOps Code ClearCase Reports works
  • Populating the Report Builder tree pane
  • Path chooser
  • Report Procedure interface specifications
  • Report programming examples
  • Run-time processing sequence for Reports programming interface
  • Saving report data
  • Troubleshooting customization
  • Errors in the interface specification
  • Text chooser
  • Type chooser
  • UCM targets chooser
  • Viewing the report
  • What you can customize in DevOps Code ClearCase Reports
  • E-mail notification setup script
  • Tips for sharing scripts
  • Adding UCM support to an existing schema
  • Setting up a Rational ClearQuest user database for UCM
  • Creating users and adding credentials
  • Using parent and child controls
  • Setting the environment (Linux and the UNIX system)
  • Customizing Rational ClearQuest project policies
  • Requirements for enabling custom record types
  • State transition default action requirements for record types
  • Upgrading your schema to the latest UCM package
  • Setting state types
  • About setting up a Rational ClearQuest user database
  • Queries in a Rational ClearQuest schema enabled for UCM
  • Schema enabled for UCM
  • State types
  • Creating and setting an activity in the integration stream (Linux and the UNIX system only)
  • Adding components
  • Resolving baseline conflicts
  • Creating a new baseline
  • Monitoring project status
  • About managing a project
  • Recommending the baseline
  • Testing the baseline
  • Viewing baseline histories
  • Building components
  • Cleaning up the project
  • Querying Rational ClearQuest user databases
  • Finding work that is ready to be delivered
  • Removing unused objects
  • Rebasing the test development stream
  • Associating UCM and Rational ClearQuest objects
  • After making a baseline
  • Composite baselines
  • Making a baseline
  • Recommended baselines
  • Baselines and streams
  • Baselines and their uses
  • Understanding UCM
  • Building components
  • Creating the project
  • Creating a PVOB
  • DevOps Code ClearCase MultiSite consideration
  • Organizing directories and files into components
  • Setting policies
  • Single-stream projects
  • Advance rebase operations
  • Directions of rebase operations
  • Overview of the UCM integration with Rational ClearQuest
  • Setting up the UCM integration with Rational ClearQuest
  • Creating a testing stream
  • Stream hierarchies
  • Assigning work
  • Shared and private work areas
  • Amount of integration
  • Creation of composite baseline descendants
  • Identifying the initial baseline
  • Making a new descendant baseline
  • Defining a baseline naming convention
  • Ongoing baselines
  • Changing to a pure composite baseline
  • Dependency relationships in pure composite baselines
  • Specifying a baseline strategy
  • Whether to use pure composite baselines
  • Identifying a project baseline
  • Planning the project
  • Identifying additional components
  • Organizing components
  • Identifying read-only components
  • Simplify a deliver operation with a rebase operation
  • Defining the directory structure
  • Defining the scope of element types
  • Integration requirement for Rational ClearQuest MultiSite
  • Rational ClearQuest MultiSite requirement
  • Mapping components to projects
  • Mapping system architecture to components
  • Overview of the UnifiedChangeManagement schema
  • Identifying promotion levels to reflect state of development
  • Using the system architecture as the starting point
  • The basic multiple-stream project
  • Single-stream projects
  • Need for parallel releases
  • Planning PVOBs
  • Deciding how many PVOBs to use
  • Mapping PVOBs to Rational ClearQuest user databases
  • Enabling a schema for UCM
  • Deciding which schema to use
  • Sharing changes by a deliver operation
  • Sharing changes by a rebase operation
  • Planning how to use the UCM integration with Rational ClearQuest
  • Alternate targets in the same project
  • Stream configurations and baseline contents
  • Development stream configurations
  • Stream hierarchies
  • Stream hierarchy and default targets
  • The integration stream configuration
  • Stream relationships
  • Read-only streams
  • Coordinating development streams in the same project
  • Choosing a stream strategy
  • Alternate target streams
  • Understanding the role of the administrative VOB
  • Deciding how many VOBs to use
  • Deciding what to place under version control
  • Perform ClearQuest action after changing activity
  • Perform ClearQuest action before changing activity
  • Transition to complete after changing activity
  • Setting policies
  • Modifiable components
  • Perform ClearQuest action after delivery
  • Perform ClearQuest action before delivery
  • Deliver changes from the foundation in addition to changes from the stream
  • Allow interproject deliver to project or stream
  • Allow deliveries that contain changes to missing or non-modifiable components
  • Policies for deliver operations to nondefault targets
  • Require that all source components are visible in the target stream
  • Do not allow deliver to proceed with checkouts in the development stream
  • Policies and interproject deliveries
  • Default promotion level for recommending baselines
  • Allow all users to modify the project
  • Rebase before delivery
  • Allow all users to modify the stream and its baselines
  • Transfer ClearQuest mastership after delivery
  • Transfer ClearQuest mastership before delivery
  • Transition to complete after delivery
  • Assigning activities
  • Capturing final baselines in a composite baseline
  • Creating the dependency relationships for composite baselines in the project
  • Making a baseline from a label
  • Setting a baseline naming template
  • Setting up the project
  • Creating components for storing baseline dependencies
  • Creating components for storing elements
  • Making components from existing VOBs
  • Creating the project
  • Creating a project based on an existing DevOps Code ClearCase configuration
  • Creating a project based on an existing project
  • Creating a project from scratch
  • Creating the project
  • Creating the project from another project
  • Creating an integration view
  • Creating an integration view
  • Disabling the link between a project and a Rational ClearQuest user database
  • Fixing projects that contain linked and unlinked activities
  • Detecting unlinked activities
  • Correcting unlinked activities
  • Defining promotion levels
  • Creating the project VOB
  • Creating the PVOB from an existing DevOps Code ClearCase configuration
  • About setting up the project
  • Migrating activities
  • Changing the project to a different Rational ClearQuest user database
  • Enabling use of the UCM integration with Rational ClearQuest
  • Setting project policies
  • Creating a development stream for testing baselines
  • Working with IBM Rational Suite (Windows)
  • Sharing baselines between sibling streams in different projects
  • Managing multiple projects
  • Composite baselines in release-oriented projects
  • Using a mainline project
  • Merging from a project to a non-UCM branch
  • Delivering work from an integration stream to another project
  • About managing multiple projects
  • Managing a current project and a follow-on project simultaneously
  • Incorporating a patch release into a new version of the project
  • Project uses
  • Migrating unfinished work to a follow-on project
  • Mixing project organizations
  • Using attributes with triggers
  • Using triggers to enforce UCM development policies
  • Delivery setup script
  • Do not allow activities to be created on the integration stream
  • Overview of triggers
  • Preoperation and postoperation triggers
  • Delivery preoperation trigger script
  • Delivery postoperation trigger script
  • Scope of triggers
  • Enforce serial deliver operations
  • Send mail to developers on deliver operations
  • Supported triggers
  • When to use Rational ClearQuest scripts instead of UCM triggers
  • Conflicts between composite baselines
  • Conflicts between a composite baseline and an ordinary baseline
  • Use of multiple user databases
  • Finishing the project configuration
  • Identifying special element types
  • Using mergetype to manage merge behavior
  • Dependency relationships in composite baselines of ordinary components
  • Pure composite baselines
  • Policies for the UCM integration with Rational ClearQuest
  • Components and baselines policies
  • Component modifiability and visibility
  • Default view types
  • Policies for all deliver operations
  • Permissions to modify projects and streams
  • Naming projects that are linked to same user database
  • Recommending a baseline for new components
  • For changing activities
  • Perform ClearQuest action before work on
  • For delivery
  • Disallow submitting records from ClearCase client
  • Allowed record types
  • For submitting records from a DevOps Code ClearCase client
  • For WorkOn
  • Using the predefined UCM-enabled schemas
  • Starting from a baseline
  • Element relocation
  • Overview of the UCM process
  • Monitoring project status
  • The rebase operation
  • Lateral rebase operations
  • Revert rebase operations
  • Summary of rules for rebasing a stream
  • Recommending the baseline
  • Multiple PVOBs and a common administrative VOB
  • Multiple PVOBs and feature levels
  • Planning how to test baselines
  • When to create baselines
  • Using multiple PVOBs
  • Linking activities to Rational ClearQuest records
  • Transferring mastership of the project
  • Changing the project name
  • Changing project policy settings
  • How the UCM integration with Rational ClearQuest is affected by Rational ClearQuest MultiSite
  • Replica and naming requirements
  • Additional uses for UCM triggers
  • Implementing a role-based access control system
  • Role-based preoperation trigger script
  • Using different paths or different scripts
  • Using the same script
  • Sharing triggers among different types of platform
  • Branches and streams
  • Moving from view profiles to UCM
  • Checkpoints and baselines
  • Feature comparison
  • Moving view profile information to UCM
  • Moving work among branches or streams
  • Preparing your view profile project
  • VOBs and components
  • View profiles and UCM
  • ChangeFieldMap
  • CQCC_QUERY_ENABLE
  • CQCC_QUERY_FILTER
  • DefineCQSchema
  • SetQuery
  • SetResultSet
  • To add a component to a stream
  • To add a directory element to a component (Linux and the UNIX system)
  • To add a directory element to a component (Windows)
  • To add DevOps Code ClearCase definitions to and upgrade a Rational ClearQuest schema
  • To start Diff Merge
  • To start the Rational ClearQuest Integration Configuration tool
  • To start the Merge Manager
  • To install and use the type manager
  • To start the Version Tree Browser
  • To start the Integration Query wizard
  • To list triggers installed in a VOB
  • To specify multiple record types
  • To reconfigure your view with the modified config spec
  • To compare two baselines
  • To compare baselines in Component Tree Browser
  • To prepare to merge
  • Setting up the trigger to monitor bug-fixing
  • To change a baseline promotion level
  • To complete remote deliver operations for a development stream
  • To create a composite baseline
  • To create Rational ClearQuest user account profiles
  • To delete an unused object
  • To deliver work between integration streams
  • To find all deliver operations that are in the posted state
  • To edit the view load rules
  • To fix a problem in a new baseline
  • To lock a stream
  • To view baseline history (Linux and the UNIX system)
  • To map record states to state types
  • To make a component modifiable within the project
  • To modify the behavior of a policy
  • To enable a schema to work with UCM
  • To rebase the development stream
  • To rebase an integration stream to baselines of another project
  • To recommend a baseline or set of baselines
  • To add a column of report output
  • To add report procedures to source control
  • To change report conditions and add to output
  • To change reports for parameters
  • To add a new command to reports
  • To set the Report Builder to the customized directory
  • To set default actions for states
  • To synchronize a child stream with project modifiable components
  • To synchronize a view with a new configuration
  • To synchronize a child stream view with new parent stream configuration
  • To attach triggers to existing elements
  • To upgrade the schema
  • To view baseline history (Windows)
  • To make a baseline
  • To make a baseline of one component
  • To make new baselines for all components in the stream
  • To make a baseline for a set of activities
  • To test in a separate development stream
  • To lock and hide an object
  • To see objects that are obsolete
  • To create and assign activities in a Rational ClearQuest user database
  • To create and set an activity
  • To create a baseline by label type
  • To set a baseline naming template
  • To create a pure composite baseline from existing approved baselines
  • To set policies from the Rational ClearQuest client
  • To start a Rational ClearQuest client
  • To create a project
  • To create a project based on an existing project
  • To create an integration view
  • To disable the project and user database link
  • To link unlinked activities at a remote site
  • To make a directory tree within a VOB into a component
  • To define the promotion levels that your project uses
  • To create a PVOB
  • To create a PVOB
  • To migrate source files into a component
  • To enable a project to work with a Rational ClearQuest user database
  • To determine policies in DevOps Code ClearCase control
  • To create a feature-specific development stream
  • To create a development stream
  • To make a VOB into a component
  • To create a component and store it in the VOB
  • To create a multiple-component VOB
  • To start the VOB Creation Wizard (the Windows system)
  • To create a multiple-component VOB (Linux and the UNIX system)
  • To create one component per VOB (Linux and the UNIX system)
  • To create one component per VOB (Windows)
  • To start the VOB Creation Wizard (the Windows system)
  • To start Project Explorer
  • To set up a Rational ClearQuest user database to work with UCM
  • To create a component without a VOB root directory
  • To relocate elements
  • To unlock the stream
  • Moving the view profile information
  • Workflow for creating projects
  • Workflow for making baselines
  • Workflow for recommending baselines
  • DevOps Code ClearCase Guide to building software
  • DevOps Code ClearCase Guide to building software
  • Share: Email
  • Twitter
  • Disclaimer
  • Privacy
  • Terms of use
  • Cookie Preferences