The reference on “composite Baselines” is: “Best practices for using composite baselines in UCM”. Introduced in ClearCase v2002, composite baselines are a mechanism for grouping baselines into a collection. One baseline is designated as the composite, and other baselines become members of the composite You do not necessarily have to use composite baselines when you … Read more
No, there is no ClearCase to Git bridge, convertor or adaptor that I know of (retaining the full history, with all its events). It is best to: restrict a git repo to an UCM component (while a Vob can contain multiple component and be way too big for a Git repo to handle) add in … Read more
I confirm that you cannot find the root directory of a snapshot view only knowing its view tag: a snapshot view can be loaded in several separate directories if you want. The only link between your snapshot view and its root directory is the .view.dat hidden file which contains the uid of the view. Plus, … Read more
Single most dangerous pitfall: Once a component is defined, you cannot move an element outside of this component (you can copy it and re-create it elsewhere, but you will loose its history) Single most useful best-practice: Understand well the nature of an UCM component: it is about coherency. A component is a set of file … Read more
Integration is a term used by convention to designate the first root stream of an UCM project. Each UCM project has one root stream (and potentially many sub-streams). The idea is that you will use your integration view as the destination view for deliver coming from sub-streams, effectively “integrated” the work done on said sub-streams … Read more
The usual commands are based on cleartool ls: ct lsprivate: but it is only for dynamic views, not snapshot views ct ls -rec -view_only: at least, it works in both snapshot and dynamic views However both list also your checked-out files. If you want only the private files, ie skipping the hijacked/eclipsed/checked-out and symlinks, you … Read more
To understand why Git does not offer some kind of what you are referring to as an “inheritance mechanism” (not involving a commit), you must first understand one of the core concepts of those SCMs (Git vs. ClearCase for instance) ClearCase uses a linear version storage: each version of an element (file or directory) is … Read more
individual stream for each developer under DV stream Whoât???? This is SPARTA! (err… no: madness: this is madness) A stream represents a development effort, not a sandbox for a “resource” (i.e. “a developer”). Resources come and go, development tasks stay. You should have a stream per development line, upon which many developers create their own … Read more
As explained in How can I use ClearCase to “add to source control …” recursively?, you have to use clearfsimport which does what you are saying (checkout the parent directories, mkelem for the elements) clearfsimport -preview -rec -nset c:\sourceDir\ChildDirectory5 m:\MyView\MyVob\ParentDirectory Note the : -preview option: it will allow to check what would happen without actually … Read more
A first possibility would be to try and select the correct version of the sub-directory to revert, like: element /path/to/directory /main/[branch]/[version] But that would be plain wrong, because: extended path names is not supported in snapshot view, as explained in this SO question. to select the directory alone is not enough (the files would still … Read more