IBM DevOps Code ClearCase: Difference between revisions

Revision as of 15:15, 15 April 2024

Revision as of 14:11, 17 April 2024

Line 29:

'''IBM DevOps Code ClearCase (also known as IBM Rational ClearCase)''' is a family of [[computer software]] tools that supports [[software configuration management]] (SCM) of [[source code]] and other [[software development]] assets. It also supports design-data management of electronic design artifacts, thus enabling hardware and software co-development. ClearCase includes [[revision control]] and forms the basis for configuration management at large and medium-sized businesses, accommodating projects with hundreds or thousands of developers. It is developed by [[IBM]].

ClearCase supports two configuration management models: UCM (Unified Change Management) and base ClearCase. UCM provides an out-of-the-box model while base ClearCase provides a basic infrastructure (UCM is built on base ClearCase). Both can be configuredcustomized to support a wide variety of needs.

ClearCase can accommodate large binary files, a large numbersnumber of files, and large repository sizes. It supports branching, and labeling,. andIt versioningenables the correct merging of refactored files by versioning directories. It also supports extensive process automation and enforcement using triggers, attributes, hyperlinks, and other metadata. It uses the '''MultiVersion File System''' ('''MVFS'''), which is a [[virtual file system]] that displaystransparently specificdetermines which versions of datafiles stored.and Indirectories particular,should itbe supportsin ''dynamicthe views''workspace whichand canorchestrates showfile anaccess arbitraryand combinationlifecycle. ofThe localMVFS is used in LAN deployments for dynamic views and remotein filesLAN or WAN deployments for automatic views.<ref>{{cite web

|url=http://www.agsrhichome.bnl.gov/Controls/doc/ClearCaseEnv/2003.06/ccase/doc/all/cc_admin/view-admin4.htm

|title= The Multiversion File System

Line 45:

}}

</ref>

ClearCase also provides authoritative build auditing, which generates metadata for each build artifact, including the context of the build and a bill of materials of files (including the exact version) referenced during the build. This metadata is used for generating SBOMs (Software Bill of Materials) and is important in regulated environments where artifact traceability is essential. ClearCase includes an implementation of 'make' that integrates with the authoritative build auditing mechanism to ensure build correctness without timestamps and automatic sharing of build artifacts across views (workspaces).

== History ==

Line 52 ⟶ 54:

== Infrastructure ==

The [[database]] system that ClearCase uses is [[RDM Embedded]] from Raima. In ClearCase terminology, an individual database is called a ''VOB'' ('''V'''ersioned '''O'''bject '''B'''ase). On this layer, maintenance takes place using Raima tooling. Around this layer, a set of interfaces with accompanying tools are used to manage the physical database system, which requires specific [[Database administrator]] skills.

The most important service is the Atria ___location Broker Daemon (ALBD), which manages all (LAN) communication between computers. Beginning with version 7, the server platform runs Websphere Application Server with a server application called the Change Management Server (CM Server), which served ClearCase clients via the HTTP Protocol. (Before version 7 there was a web service by which users could access ClearCase via their browsers.) CM server has since been replaced by the ClearCase Remote Client Wide-Area Network Server (CCRC WAN server), which continues to be based on Websphere Application Server.