Content deleted Content added
m Typo/general fixes, replaced: Enterprize → Enterprise |
m Added new release version, release date, and download doc link. Thanks |
||
| (32 intermediate revisions by 16 users not shown) | |||
Line 1:
{{Short description|
{{Infobox software| name = ClearCase
| logo = [[File:
| author = [[Atria Software]]
| developer = [[IBM]]
| released = {{Start date and age|1992}}
| latest_release_version =
| latest_release_date = {{release date and age|
| latest_preview_version =
| latest_preview_date =
| operating_system = {{plainlist|
* [[IBM AIX|AIX]], [[HP-UX]], [[Linux
* [[z/OS]] (limited client)<ref>{{cite web|url=https://www.ibm.com/docs/en/
|title=Installing and using z/OS Extensions|website=[[IBM]] }}</ref>
}}
| programming_language =
Line 19:
* HP-UX: [[IA-64]]
* Linux: [[IA-32]], [[x86-64]], [[ppc64]], [[ppc64]]le, [[Linux on IBM Z|IBM Z]]
* Solaris: [[SPARC]], x86-64
* Windows: IA-32, x86-64
}}
| genre = [[Software configuration management]]
| license = IBM [[Software license|EULA]]
| website = {{URL|https://www.ibm.com/products/
}}
'''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
ClearCase can accommodate large binary files, a large
|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 ⟶ 44:
}}
</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 can be 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 ==
ClearCase was developed by [[Atria Software]] and first released in 1992<ref>{{cite web | url = https://www.findarticles.com/p/articles/mi_m0SMG/is_n13_v12/ai_12606942 | archive-url = https://web.archive.org/web/20090802071539/https://www.findarticles.com/p/articles/mi_m0SMG/is_n13_v12/ai_12606942 | url-status = dead | archive-date = 2009-08-02 | title = ClearCase - Atria Software Inc.'s software configuration management system - New Products: Development Tools - Brief Article - Product Announcement | publisher = Software Magazine | date = September 15, 1992 | access-date = 2007-12-01 }}</ref> on Unix and later on [[Windows]]. Some of the Atria developers had worked on an earlier, similar system: ''DSEE'' ([[Apollo Domain|Domain]] Software Engineering Environment) from [[Apollo Computer]]. After [[Hewlett-Packard]] bought [[Apollo Computer]] in 1989, those developers left to form Atria.<ref>{{cite web | url = http://www.cmcrossroads.com/cgi-bin/cmwiki/view/CM/HistoryOfCM | title = Key dates in Hardware/Software Configuration Management History | publisher = CM Crossroads LLC | year = 2007 }}</ref><ref>{{cite web | url = https://www.findarticles.com/p/articles/mi_m0SMG/is_n8_v15/ai_17338017 | archive-url = https://web.archive.org/web/20090802063953/https://www.findarticles.com/p/articles/mi_m0SMG/is_n8_v15/ai_17338017 | url-status = dead | archive-date = 2009-08-02 | title = Complex development earns Atria an IS role; hot Unix vendor's move to Windows and NT opens IS doors - Company Profile | author = Michael Bucken | date = August 1995 | publisher = Software Magazine }}</ref><ref>{{cite newsgroup | url = http://lists.gnu.org/archive/html/info-cvs/2004-12/msg00237.html | title = Re: cvs vs. clearcase? | author = Andrew DeFaria | date = December 21, 2004 }}</ref> Atria later merged with [[Pure Software]] to form PureAtria
{{cite web
|url=https://www.hcltech.com/newsfeed/partnership-growth-and-innovation
DSEE introduced many concepts that were adopted by ClearCase. The Apollo Domain file system allowed special handler programs to intervene during file access. DSEE made use of this feature to invisibly substitute a versioned copy when a particular file was opened.<ref>{{cite web |url = https://web.archive.org/web/20070224072638/https://www.findarticles.com/p/articles/mi_m0HPJ/is_n3_v42/ai_10916486 |title = DSEE: a software configuration management tool |author = David c. Lubkin |date = June 1991 |publisher = Hewlett-Packard Journal |access-date = July 17, 2010 }}</ref> With the versioning specification resident in the user environment, all accesses to versioned files were redirected, including such mundane accesses as printing, viewing in a generic text editor etc.▼
|title=A partnership for growth and innovation
|publisher=HCL
DSEE relied heavily on a file that described all the software modules and their dependencies. The file had to be generated manually, which was a major impediment to its use in large systems. However, once generated, it enabled DSEE to calculate the optimum way to perform a build, re-using all modules that had previously been processed and whose version specifications matched the specifications for the build.▼
|date=November 17, 2016
}}
DSEE also introduced the "version spec," which was called a "thread." This was a list of possible versions that could be in the user environment or in a build. A major innovation was the use of build signatures and software release signatures in the thread. The items in a thread might thus be:▼
</ref> with HCL Technologies that will allow for accelerated development.
* Any copies reserved for editing (i.e. checked out)▼
* The latest version (usually for developers only)▼
* A branched version of a file (a version on an alternate line of development).▼
* A labeled version (for developers working on a particular revision level)▼
* The version used in build XYZ.▼
* The version used in software release x.y.z.▼
Threads were processed from top to bottom for each file. A developer thread might have "reserved" at the top, followed by a labeled version. For a fix to an existing release, the thread would be "reserved", then the release signature.▼
In the absence of the invisible file redirection of the Apollo Domain file system, ClearCase uses the virtual file system provided by the [[MultiVersion File System|MVFS]] feature that is described below. The "thread" concept corresponds to the ''dynamic view''. Support for derived objects in a view is similar to DSEE's concept.▼
== Infrastructure ==
The [[database]] system that ClearCase uses is
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.
Line 74 ⟶ 66:
== Views ==
A distinguishing feature of ClearCase is the [[MultiVersion File System]] (MVFS), a proprietary [[networked filesystem]] which can
ClearCase also supports snapshot views, which are copies of repository data. As opposed to dynamic views, snapshot views are maintained on a local (OS-specific) file system and do not require network access. 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 synchronized with the VOB when a connection is reestablished. This mode of operation is similar to that of CVS (Concurrent Versions System) software.
Line 126 ⟶ 118:
ClearCase MultiSite enables developers at different locations to use the same ClearCase versioned object base (VOB). Each ___location (site) has its own copy (replica) of the VOB. Data synchronization via any protocol can be unidirectional or bidirectional. Synchronization patterns can be one-to-one (two replicas exchange data), ring (round-robin synchronization), one-to-many (replication from a “hub” VOB) or many-to-many (each replica exchanges data with all other replicas).
== DSEE ==
▲DSEE (Domain Software Engineering Environment) introduced many concepts that were adopted by ClearCase. The Apollo Domain file system allowed special handler programs to intervene during file access. DSEE made use of this feature to invisibly substitute a versioned copy when a particular file was opened.<ref>{{cite web |url = https://www.findarticles.com/p/articles/mi_m0HPJ/is_n3_v42/ai_10916486 |archive-url = https://web.archive.org/web/20070224072638/https://www.findarticles.com/p/articles/mi_m0HPJ/is_n3_v42/ai_10916486 |url-status = dead |archive-date = 2007-02-24 |title = DSEE: a software configuration management tool |author = David c. Lubkin |date = June 1991 |publisher = Hewlett-Packard Journal |access-date = July 17, 2010 }}</ref> With the versioning specification resident in the user environment, all accesses to versioned files were redirected, including such mundane accesses as printing, viewing in a generic text editor etc.
▲DSEE relied heavily on a file that described all the software modules and their dependencies. The file had to be generated manually, which was a major impediment to its use in large systems. However, once generated, it enabled DSEE to calculate the optimum way to perform a build, re-using all modules that had previously been processed and whose version specifications matched the specifications for the build.
▲DSEE also introduced the "version spec," which was called a "thread." This was a list of possible versions that could be in the user environment or in a build. A major innovation was the use of build signatures and software release signatures in the thread. The items in a thread might thus be:
▲* Any copies reserved for editing (i.e. checked out)
▲* The latest version (usually for developers only)
▲* A branched version of a file (a version on an alternate line of development).
▲* A labeled version (for developers working on a particular revision level)
▲* The version used in build XYZ.
▲* The version used in software release x.y.z.
▲Threads were processed from top to bottom for each file. A developer thread might have "reserved" at the top, followed by a labeled version. For a fix to an existing release, the thread would be "reserved", then the release signature.
▲In the absence of the invisible file redirection of the Apollo Domain file system, ClearCase uses the virtual file system provided by the [[MultiVersion File System|MVFS]] feature that is described below. The "thread" concept corresponds to the ''dynamic view''. Support for derived objects in a view is similar to DSEE's concept.
== Releases ==
V11.0.0 (March 2024) release and succeeding fix pack releases.<ref>{{Cite web |date=2024-07-15 |title=New features and other changes in IBM DevOps Code ClearCase version 11.0.0.x |url=https://www.ibm.com/support/pages/node/7116220 |access-date=2024-09-05 |website=www.ibm.com |language=en}}</ref>
V10.0.0 (December 2022) and succeeding fix pack releases: ▼
V10.0.1 (October 2023) release and succeeding fix pack releases.<ref>{{Cite web |date=2024-07-15 |title=New features and other changes in Rational ClearCase version 10.0.1.x |url=https://www.ibm.com/support/pages/node/6956257 |access-date=2024-09-05 |website=www.ibm.com |language=en}}</ref>
V10.0.0 (December 2022) and succeeding fix pack releases.<ref>{{Cite web |date=2023-01-31 |title=New features and other changes in Rational ClearCase version 10.0.0.x |url=https://www.ibm.com/support/pages/node/6621241 |access-date=2024-09-05 |website=www.ibm.com |language=en}}</ref>
V9.1.0 (December 2020) and succeeding fix pack releases.<ref>{{Cite web |date=2024-07-15 |title=New features and other changes in Rational ClearCase version 9.1.0.x |url=https://www.ibm.com/support/pages/node/6254804 |access-date=2024-09-05 |website=www.ibm.com |language=en}}</ref>
V9.0.2 (January 2020) and succeeding fix pack releases.<ref>{{Cite web |date=2023-10-03 |title=New features and other changes in Rational ClearCase version 9.0.2.x |url=https://www.ibm.com/support/pages/node/1087828 |access-date=2024-09-05 |website=www.ibm.com |language=en}}</ref>
V9.0.1 (June 2017) and succeeding fix pack releases.<ref>{{Cite web |date=2022-07-25 |title=New features and other changes in Rational ClearCase version 9.0.1.x |url=https://www.ibm.com/support/pages/node/558057 |access-date=2024-09-05 |website=www.ibm.com |language=en}}</ref>
V8.0.1 (June 2013) and succeeding fix pack releases.<ref>{{Cite web |date=2020-12-18 |title=What's new in ClearCase |url=https://www.ibm.com/support/pages/node/615821 |access-date=2024-09-05 |website=www.ibm.com |language=en}}</ref>
== See also ==
Line 177 ⟶ 172:
== External links ==
* {{Official website|
{{Version control software}}
| |||