I would recommend this question: Now the problem is to checkin everything that has changed. It is problematic since often not everything has changed, and ClearCase will trigger an error message when trying to check in an identical file. Meaning you will need 2 commands: ct lsco -r -cvi -fmt “ci -nc \”%n\”\n” | ct … Read more
2… 1 cleartool descr -l project:myProject@\myPVob with some grep, you have the list of components (writable or not) and policies. If you want only the Streams: cleartool lsproj -tree myProject@\myPVob You can repeat that for a Stream (to get the sub-streams) cleartool lsstream -tree myStream@\myPVob For the foundation baselines of a Stream: cleartool descr -fmt … Read more
If you don’t want to merge a specific type of file, you can change its type to a “copy merge” policy (ClearCase will copy the source over the destination) cleartool find . -name ‘*.jar’ -exec ‘cleartool chtype “COPY_MERGE” $CLEARCASE_XPN’ This is an improvement from the NEVER_MERGE presented in this IBM article, and is available in … Read more
Do not forget the time directive of selection rule. element /myPath/… /main/{!created_since(16-Sep-2009)} element /myPath/… /main/LATEST Can enable you to see versions from a month ago (see time and query) See also “time-based rule” answer. From there you can branch and update your code from this older stable point.
If you are in a view, you can: get the current stream cleartool lsstream -cview get all baselines for a component in that stream cleartool lsbl -comp myComp@\myPVob -stream myStream@\myPVob get all foundation baselines for that stream cleartool descr -fmt “%[found_bls]CXp” stream:myStream@\myPVob Don’t forget that in a view on a stream with a modifiable component, … Read more
What is described by skwllsp can be be done in a dynamic view through the use of extended pathnames cd m:/myDynamicView/MyVob/path/to/file cleartool lsvtree myFile cleartool checkout -c “cancel co” myFile copy myFile@@/main/xx myFile cleartool checkin -nc myFile with xx being the version number you want to restore. But should you have made multiple checkins, including … Read more
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
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
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