Question

I have been optimizing our continuous integration builds, and the remaining bottleneck seems to be the following ClearCase commands:

cleartool.exe mklbtype -nc -ordinary BUILD_ApplicationWorkspace_1.0.0.0@vob_example

For a view with 1800 files, this is taking over 6 minutes to complete. Our MSBuild task takes half that. I am guessing the bulk of the bottleneck is network bandwidth but also how we are labeling the files used in this build.

Baed on this, I have questions:

1. Are we efficiently labeling the source code files, or is there a more efficient command we can run?
2. How can I get better metrics to understand where this ClearCase command is spending the bulk of its time?
3. Do prior labels slow ClearCase labeling down?
4. Related, does ClearCase have anything similar to Git Sub-modules or svn:externals? Currently we are creating a view of everything, including dependencies, before we do the build.

Thanks for your help.

Answer 1

cleartool mklbtype shouldn’t take that long: it is about creating the type of the label, not about applying it on each and every of your file.
If anything, mklabel should takes time.

Applying the UCM methodology (as opposed to your current “Base ClearCase” usage) might help in that:

• it forces you to define “components” (coherent groups of files, ie not “1800 files”, which is quite large)
• it proposes “incremental baseline“, which only labels what has changed.
• the UCM components are a bit akin to git Submodules (you can group them in a composite baseline), but that is not the same than svn:external, as mentioned here and in “Why are git submodules incompatible with svn externals?“.

But if you are stuck with Base ClearCase, you are stuck with labelling everything, and one venue for optimization would be to label only a subset of those files.