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
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
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
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
As explained in “Before adding files and directories to source control”, the version 0 is a placeholder marking the start for all versions in a given branch: You can end up with only the version 0 when you undo-checkout a file you just checked out in a new branch (in that case, only a version … Read more
Evil Twin An Evil Twin is an element that you have removed (using rmname) and want to re-add, but it’s ‘evil twin’ exists in previous versions of the directory. You have to remember that each element had a unique ID, so you are attempting to add an element with the same name – but with … Read more
Here’s a method that avoids hijacks, which our team used this method quite successfully for over a year, until we retired ClearCase for Subversion (per company policy, although it is a backwards step for our team – we were basically just using ClearCase as a dumb file system, and virtually working natively in git, but … Read more
I’m trying to look at a bunch of old versions I am not sure if you are speaking about “a bunch of old versions” of one file, “a bunch of old versions” from several files. To visualize several old versions of one file, the simplest mean is to display its version tree (ct lsvtree -graph … Read more
You can find a good comparison between ClearCase and Git in my SO answer: “What are the basic ClearCase concepts every developer should know?“, illustrating some major differences (and some shortcomings of ClearCase) File-centric operations The most single important shortcoming of ClearCase is its old “file-centric” approach (as opposed to “repository-centric” like in SVN or … Read more