Rational ClearCase

Encyclopedia : R : RA : RAT : Rational ClearCase

Rational ClearCase is a software tool for revision control (configuration management, SCM etc) of source code and other software development assets. It is developed by IBM. ClearCase forms the base of version control for many large and medium sized businesses and can handle projects with hundreds or thousands of developers, but the price is quite steep for smaller companies.

Rational supports two types of SCM configurations, UCM (see below), and base ClearCase. UCM provides an out-of-the-box SCM configuration but is fairly rigid. Base ClearCase supplies the basic tools, and can be configured in many different ways.

ClearCase can run in a number of Operating systems including Linux, Solaris and Windows. It can handle large binary files, large numbers of files, and large repository sizes. It handles branching, labeling, and versioning of directories.

Contents

1 History
2 Views
3 Configuration specifications
4 UCM

4.1 Unique features

5 See also
6 External links

History

ClearCase originally derived from a product of Apollo Computers: DSEE (Domain Software Engineering Environment), which was ported to Unix and further developed by Atria Software after Hewlett-Packard bought Apollo. Atria later merged with Pure Software to form PureAtria. That firm merged with Rational Software, which was purchased by IBM. IBM continues to develop and market ClearCase.

Views

Objects under version control in ClearCase are stored with their histories in repositories called VOBs (versioned object base). ClearCase's novelty was in its versioned file system (called MVFS: Multiversion File System), which can be used to mount VOBs as a virtual file system through a dynamic view, selecting a consistent set of versions and allowing for the production of derived objects. The dynamic view allows this to map to a Software Configuration. This was a departure from the repository/sandbox model, allowing for the early management of artifacts (before they are being checked in, and not limited to these first order configuration items).

Alternatively, ClearCase supports snapshot views which are just copies of a directory tree spanning one or several VOBs. Snapshot views do not use a virtual file system to provide access to VOB data. Instead, a snapshot view stores a copy of the VOB data locally on the user's computer. Snapshot views can be used while disconnected from the network and later resynchronized to the VOB when a connection is reestablished. This mode of operation is similar to how the widely-used CVS (Concurrent Versions System) software works.

From the perspective of software on the client computer, a view appears as just another file system. If a file is created in a view by normal OS means (copying or saving from an editor for instance), then ClearCase will create this file as a "view-private" file. It will not be visible in any other view. This allows build systems to operate in the same directory structure as the source code, and ensures that each developer can build completely independently of each other (though if the view is a dynamic one then the normal overhead associated with accessing files over an NFS link applies). A view-private file (or directory for that matter) can be converted into a versioned element at any time, making it visible to other developers.

Each developer typically has one or several views at his disposal. It is sometimes practical to share views between developers, but sharing branches is usually used instead. Having a branch hierarchy is often useful, so an entire development project shares a common development branch, while a smaller team shares a sub-branch, and each developer has his or her private branch. Whenever some change is deemed stable enough for a larger group, it can be merged to the parent branch.

Configuration specifications

Each view is controlled by its associated configuration specification. This is a text file that specifies what elements (files or directories) should be visible in a view, and which versions of these elements. When deciding which version, if any, of an element should be visible, ClearCase traverses the configuration specification line-by-line from top to bottom, stopping when a match is found. A sample configuration specification could look like this:

Show all elements that are checked out to this view, regardless any other rules.

element * CHECKEDOUT

If an element has a version on the 'module2_dev_branch', then the latest
version of this branch shall be the visible version in this view.

element * .../module2_dev_branch/LATEST

For all files named 'somefile', regardless of location, always show the latest version on the main branch.

element .../somefile /main/LATEST

Use a specific version of a specific file. Note: This rule must appear before the next rule to have any effect!

element /vobs/project1/module1/a_header.h /main/proj_dev_branch/my_dev_branch1/14

Show all elements labeled with the tag 'PROJ1_MOD2_LABEL_1' under the 'project1/module1' path.
Furthermore, don't allow any checkouts in this path.

element /vobs/project1/module1/... PROJ1_MOD2_LABEL_1 --nocheckout

Show the 'ANOTHER_LABEL' version of all elements under the 'project1/module2' path.
If an element is checked out, then branch that element from the currently visible version,
and add it to the 'module2_dev_branch' branch.

element /vobs/project1/module2/... ANOTHER_LABEL --mkbranch module2_dev_branch

A configuration specification can also reference other configuration specifications using the 'include' statement.

UCM

Unique features

Configuration Record: When a dynamic view and the omake make utility supplied with clearcase is used for the software build clearcase records all files (and its versions) read during the build time. This process is called build-auditing. The dependency information is stored in a hidden configuration record which can be shown for each derived object. The configuration record can be used to setup another view showing all files that has been read before during the build time. Or you can use the configuration record to apply a label to the files (and versions) that were read during the build.
Build Avoidance: Use of MVFS (Multiversion File System) allows derived objects built in one dynamic view to be automatically "copied over" to another dynamic view requiring "exactly the same" derived object. Two derived objects are deemed to be "exactly same" if they have the same configuration record (ClearCase terminology, also called bill of materials). Shared derived objects will be physically present on the VOB server, and not in the views that reference them. The process of "copying over" is called winking in in ClearCase terminology.
Unix/Windows Interoperability: VOBs hosted on *nix (Solaris, Linux, AIX, HP-UX, Irix primarily) servers can be accessed from views hosted on Windows clients. VOBs hosted on Windows servers can only be accessed by Unix clients with snapshot views. .
Integration With Other Rational Products: Other products (originally) from Rational Software, notably ClearQuest and Rational Rose integrate with ClearCase. ClearCase also integrates with Microsoft VisualStudio and the Eclipse IDE through a plugin.

External links

From Wikipedia, the Free Encyclopedia. Original article here. Support Wikipedia by contributing or donating.
All text is available under the terms of the GNU Free Documentation License See Wikipedia Copyrights for details.