Reputation: 67
In my continued quest to learn and tame our use of ClearCase [UCM], I have realized that every label, activity, baseline, stream and almost every view from the beginning of time is open and visible within our ClearCase setup.
In a similar vein to this answer, I am under the belief that it could be beneficial to lock obsolete our old baselines at least.
Is there an easy way to find baselines older than a certain date (from Windows in my case)?
I've been struggling with the cleartool find
, lsbl
and desc
commands and feel I am missing something simple.
As a second part to this, if I did find a command - should it be used? Is there a danger in almost blindly selecting all [old] baselines and locking them obsolete in this manner [other than those reasons already stated in the answer above]?
Is there another recommended method for this, or should I be looking at housekeeping at a different level? Different object? Or not at all?
Upvotes: 1
Views: 91
Reputation: 1073
Given the irremovable nature of a lot of UCM metadata, you may also want to consider migrating the components and projects to new VOBs. Locking a baseline/stream obsolete only makes it not display, it will still be looked up when a tool gets the baselines in the stream. Depending on your project architecture and baselining process, this could be anywhere from somewhat to extremely painful...
There isn't anything wrong with a project/component structure that has been around for over a decade. I work every day on one. If you're only worried about stuff being visible, the lock obsolete process is fine. if you're having other issues as well, then a "clean slate" PVOB/CVOB may resolve them.
Upvotes: 1
Reputation: 1324347
One possibility, that I describe in "How to get the recent baselines of a project in clearcase" is to use the fmt_ccase
option combined with cleartool lsbl
:
cleartool lsbl -fmt "%d %n\" -stream...
You still need to parse and sort the output, but that is a start.
should it be used? Is there a danger in almost blindly selecting all [old] baselines and locking them obsolete in this manner?
Not really (beside the bug I mentioned about foundation baselines): it is a purge policy, and it will need to be adjusted project by project.
Upvotes: 1