How can I use ClearCase to “add to source control

Question

I unpacked a zip-file delivery into a clearcase view. Now I want to add the complete file tree to the repository. The GUI only provides an "Add to source control ..." for individual files/directories. Do you know how to recursively add the whole tree?

(I'm on a Windows system, but have Cygwin installed.)

Answer 1

ClearTeam Explorer, version 8 (maybe earlier as well), has recursive add of subdirectories/files when you select "Add to Source Control". When the "Add to Source Control" dialog box appears, check the "Include descendant artifacts of the selected directories" checkbox and uncheck the "Checkout descendant files only, do not checkout descendant directories" checkbox.

Answer 2

Here is one other way I found by using the Windows Explorer:

1. Select Search... from the context menu on the target directory.
2. Search for *.
3. Select all (Ctrl-A) files/directories in the result list.
4. Select ClearCase > Add to source control... from the context menu on an item in the result list.

There you go ...

Answer 3

You have to use the commandline. The Context menu in Explorer doesnt do this recursively!

clearfsimport –recurse /usr/src/projectx /vobs/projectx/src

Answer 4

Heres a script to do it And tips to integrate the script from Explorer

http://www.ibm.com/developerworks/rational/library/4687.html

Answer 5

I would rather go with the clearfsimport script, better equipped to import multiple times the same set of files, and automatically:

• add new files,
• make new version of existing files previously imported (but modified in the source set of files re-imported)
• remove files already imported but no longer present in the source set of files.
• make a clear log of all operations made during the import process.

So if your 'zip-file delivery needs to be updated on a regularly basis, clearfsimport is the way to go, but with the following options:

clearfsimport -preview -rec -nset c:\sourceDir\* m:\MyView\MyVob\MyDestinationDirectory

Note the :

• -preview option: it will allow to check what would happen without actually doing anything.
• '*' used only in Windows environment, in order to import the content of a directory
• -nset option.

From CMWiki, about that 'nset' option:

By default, clearfsimport is meant to be used by the vob owner or a privileged user, but users often overlook the -nsetevent option, with which it may be used by any user.
This option drives clearfsimport not to set the time stamps of elements to this of the source file object outside the vob (which requires privileged access).
There is a minor non-obvious side-effect with this: once a version will have been created with a current time stamp, even the vob owner will not be able to import on top of it a version with an older (as it would be) time stamp, without this -nsetevent option. I.e. once you use this option, normal or privileged user, you are more or less bound to use it in the continuation.

Answer 6

Since I did not have access to clearfsimport , I added the files/directories in a two step process:

1.) find . ! -path . -type d | xargs cleartool mkelem -mkpath -nc

This will create nodes for all new directories recursively

2.) find ./ -type f | xargs cleartool mkelem -nc

This will create nodes for all new files recursively