Configuration

All configuration happens on command line or in a property file. Command line has precedence over the property file, which has precedence over the build in defaults.

Git and Clearcase

There are four fundamental configuration items you must set:

• cleartool command line executable installed elsewhere
• You need two more pieces of information:
• path of your git repository
• path of the source code directory within a ClearCase UCM view.

Plear note that it strongly recommended if both repository and view were dedicated exclusively to git-to-clearcase.

1) Cleartool command line executable

Absolute, full path to cleartool.exe.

Use --ct path on command line or cleartool.exec=path in the configuration file.

2) Git command line executable

Absolute, full path to git.exe.

Use --git path on command line or git.exec=path in the configuration file.

3) Cleartool vob view directory

Absolute, full path to the source code directory within the Clearcase view of the VOB.

Use --view path on command line or vobview.dir=path in the configuration file.

4) Git repository

Absolute, full path to the git repository root.

Use --repo path on command line or repository.dir=path in the configuration file.

Configuration: Git before synchronization

Before synchronizing, git-to-clearcase may run some additional Git repository maintenance. If you run git-to-clearcase on a exclusively dedicated repository, then you may safely leave out options 3 to 5.

1) Fetch commits from remote repository.

Ensures the the local repository contains the latests commits from every developer. Automatic fetch requires a specific public/private key setup, thus this operation is turned off by default.

Useful for automation of the synchronization process. Add --fetch to command line or fetchRemoteGitRepository=true to the configuration file.

2) Forward local git repository.

Ensures that the repository points to the latest commit of the branch. By default, git-to-clearcase synchronizes the Clearcase view to the current Git commit. This operation is turned off by default as it is left up to you to navigate the git history before synchronizing.

Useful for automation of the synchronization process. Add --forward to command line or fastForwardLocalGitRepository=true to the configuration file.

3) Reset local git repository.

Ensures that there are no uncommitted changes that might be synchronized by accident. Turned off by default as git-to-clearcase expects a dedicated repository that should not get dirty local edits.

Add --reset to command line or resetLocalGitRepository=true to the configuration file.

4) Clear local git repository.

Ensures that there are no unversioned files that my interfere the synchronization. Turned off by default as git-to-clearcase expects a dedicated repository that should not get dirty local edits.

Add --clean to command line or cleanLocalGitRepository=true to the configuration file.

5) Configure the local git repository.

Ensures that the repository contains properties that instruct git command line to behave as expected by git-to-clearcase. It frees your from the burden of configuring the repository properties by hand.

Useful only on the fist run. Add --configure to command line or applyDefaultGitConfig=true to the configuration file.