Checking out an element

If you use ClearCase® for source control management, you need to check out an element (a Functional Test script, a Functional Test project, an object map or a Java™ file) before you modify it.

Before you begin

About this task

You can check out an entire project or one or more files at a time.

A snapshot view contains copies of ClearCase versions and other file system objects in a directory tree. If you modify an element without checking it out of a snapshot view, for example, you edit a file from the file system, this version of the file is hijacked. The hijacked file appears under Details of <scriptname> with the warning symbol ( ) next to it. You can convert the hijacked files to check them out and work on the file when you check out an element.

If you use ClearCase Multisite and want to modify or create a test asset, you must request mastership when you check out or check in a test asset. When you check out or check in a test asset, and you are using ClearCase multisite, HCL OneTest™ UI displays the Request Mastership check box in the appropriate dialog box if a test element is not mastered locally.

To check out an element:

Procedure

From the Solution Explorer, select the project or file.
Right-click the selected project or file, and then click Check Out.
Clear the check box of any element you do not want to check out.
To check out a file reserved, do the following:
A reserved checkout gives you the exclusive right to check in the element when you are done. With an unreserved checkout, you may need to merge your changes at checkin time, if someone else checked in the same element before you did.
1. Click Options ().
2. Click Reserved to reserve a checkout.
3. Click OK.
Click Check Out to check out a file or project.
If an element is hijacked, under Some of the files in selection have been hijacked, take one of the following steps:
When you update a snapshot view, ClearCase compares the current size and last-modified time stamp of a non-checked-out file with the size and time stamp that it stored in the view database. If either value is different from the value in the view database, ClearCase considers the file hijacked.
- Click Convert hijacked files to checkout to check out the hijacked version of this file and continue working on the hijacked version. When you check in this file, ClearCase replaces the version in the VOB with the hijacked version
- Click Replace hijacked files (save each hijacked file to a file with a _keep extension) to check out the version of this file from the VOB and not continue work on the hijacked version. When you check in this file, ClearCase checks in the version from the VOB and creates a copy of the hijacked version with a _keep extension in case you need the changes later.
If you use ClearCase in a multisite situation and if one or more of the files associated with the selected scripts, shared maps, shared datasets, or Java files does not have mastership locally, click Request Mastership to request mastership of the file.
ClearCase MultiSite® uses an exclusive-right-to-modify scheme, called mastership. Mastership is the ability to modify an object or to create instances of a type object.

Results

Related Topics:

About Requesting Mastership

About Software Configuration Management

Using ClearCase with Test Object Maps

What to do next

Feedback