Rational ClearCase
| IBM Rational ClearCase
|
|
|---|---|
|
|
| Basic data
|
|
| developer | IBM |
| operating system | cross-platform |
| category | Configuration management |
| License | proprietary |
| German speaking | Yes |
| www.ibm.com | |
Rational ClearCase is a scalable software for configuration management and contains functions for version management , parallel development , workspace management as well as build and release management . It provides functionalities that are helpful for the creation, updating, generation (build), distribution and reuse of all types of artifacts. ClearCase is available for Linux, Windows, Unix and on mainframe computers (z / OS) and thus enables cross-platform application development. The optional extension Multisite or the use of the ClearCase Remote Client (CCRC) enables parallel software development across geographically distributed environments.
history
ClearCase was developed in 1990 by David Leblang and Howard Spilke, employees of Millennium Teamware , and after around one and a half years of development, it came onto the market in 1992 as Atria ClearCase initially for Unix operating systems. After VAX CMS and Apollo DSEE, ClearCase was the third SCM tool that Leblang had worked on.
Atria Software (originally Atria, renamed for legal reasons) was bought by Pure Software in 1996 and has been known as PureAtria ever since. Rational Software later acquired PureAtria before Rational Software was acquired by IBM in 2003 .
Releases
| Release | Publication date | Remarks |
|---|---|---|
| 9.0 | May 2016 | Thread safety in core libraries, smart card support for the ClearCase remote client, improved Cadence Virtuoso integration |
| 8.0 | October 2011 | |
| 7.1.2 | October 2010 | |
| 7.1.1 | December 2009 | Atomic Commit introduced. |
| 7.1 | December 2008 | Introduction of the IBM Installation Manager , conversion of the web platform to the CM server based on the WebSphere Application Server , introduction of the Java -based CM API and support for UTF-8 . |
particularities
All versioned objects, called artifacts , are stored in ClearCase's own repository , which is called VOB ( Versioned Object Base ). In order to be able to edit certain versions of these artifacts, ClearCase has a mechanism that is implemented using a so-called view (in the sense of a “view” in the VOB). These views behave on the client computer like another file system that is transparent, e.g. B. integrated in the file manager so that versioned and non-versioned files can be accessed in the same way.
ClearCase saves file versions according to the so-called in-line delta storage principle. The changes between individual versions of a file are saved with a special notation within the file itself. In this way, any version can be displayed at the same speed.
In addition to the integration in the file manager, working with versioned files is made easier by integrations with a large number of other products and development environments (Microsoft Visual Studio, Eclipse IDE, Microsoft Word, Code :: Blocks, NetBeans, ...). ClearCase also has integrations with other IBM Rational products such as: B. Rational ClearQuest, Rational Rose , Rational Application Developer , which serve as the basis for the traceability of changes over the entire development process - from the requirement to the corresponding test cases.
In addition, ClearCase offers the option of being used via a browser without installing client-side software. Starting with version 6, an Eclipse- based ClearCase Remote Client (CCRC) is available based on web technology .
In principle, ClearCase supports two different working methods, which are referred to as Base ClearCase and UCM (Unified Change Management). Here, Base ClearCase offers greater flexibility, but requires more effort when implementing the procedure. UCM, which is based on Base ClearCase, supports easier commissioning with a ready-made procedure, which, however, offers less flexibility.
- Integrated software build management (Base ClearCase)
- ClearCase allows the use of “derived objects” with the integrated build tools omake and clearmake . The objects created during compilation can be cached in the view or VOB and reused in the next build, so that the performance of a software build can increase significantly. You can also have a configuration record created during the build , where e.g. B. all files used for the build are saved with the corresponding version information.
- UCM (Unified Change Management)
- Unified Change Management is a process predefined by Rational that generally supports software development. The UCM project usually contains several components , which in turn can comprise several files. The developer works under UCM on his own streams . The work orders (activities) can comprise several files to be changed. Defined statuses (e.g. release status ) are marked by baselines , similar to the label under ClearCase.
Multisite
The extension ClearCase Multisite replicated VOBs stored in the data of the ClearCase system to any number of other locations ( sites ), thus facilitating the work of distributed teams to shared data.
When adding a new location, one or more VOBs are initially transferred to the other location (s) ( replication ). During operation, only the data that has been changed at one of the locations is then regularly sent (synchronized).
In order to be able to control the competitive processing of one version of an artifact, Multisite introduces the principle of mastership . Here, the mastership of a version branch of an artifact is at exactly one location at a time. Only the site that has the mastership can create new versions on this branch. All other locations can (at this point in time) only have read access to this branch in the version tree. Editing of versions on other branches of the same artifact remains unaffected and is still possible at any time. The mastership can be transferred to another person or requested from one location ( Request for Mastership ).
Web links
Individual evidence
- ↑ ClearCase - Atria Software Inc.'s software configuration management system - New Products: Development Tools - Brief Article - Product Announcement . Software magazines. September 15, 1992. Retrieved December 1, 2007.
- ↑ Lawrence M. Fisher: Pure Software To Buy Astria [so stated! correct would be: Atria] In Stock Deal . The New York Times . June 7, 1996. Retrieved December 1, 2007.
- ^ IBM Reports 2003 First-Quarter Results . IBM. April 14, 2003. Retrieved January 9, 2008.
- ↑ Rational ClearCase V9.0.0 . Retrieved December 17, 2016.
- ↑ IBM Japan: IBM Rational ClearCase and IBM Rational ClearQuest V9.0 deliver enterprise collaborative change and configuration management solution enhancements for software and systems development teams , Software Announcement JP16-0125, March 15, 2016.
- ^ Fix list for Rational ClearCase . Retrieved June 29, 2014.
- ^ Brian A. White: Software Configuration Management Strategies and Rational ClearCase , Addison-Wesley, 2000, ISBN 0-201-60478-7 , p. 33.