In order to do dependency checkin in ClearCase/ClearQuest, do I depend
upon a 'change set' type query in CQ, or do I look in CC for CrmRequest
hlinks? (This is for base ClearCase with cc/cq integration.)
By dependency checking I mean:
a) looking for dependent records in bad state. We don't want
to pull \main\3 if \main\2 has a defect in reopen/work-in-progess
b) we want to build on just 6 of 10 defects. We need to verify
that when pulling \main\3, that none of the unwanted defects were
included in \main\3, \main\2, and \main\1.
It doesn't look like CQ's Change Set form is very useful since the data
isn't specific enough. "V:\admin\test\[email protected]@\main\4" doesn't tell
me what view V: is associated with (and assumes that the config spec
doesn't change and that no there are changes to the directory
structure.) The CQ dbid field doesn't seem to have a corresponding
mapping in clearcase.
So I'm guessing that if I want to dependency checking with CC/CQ, I have
to use clearcase to:
-walk each version (probably all versions with branch X)
-look for CrmRequest hlinks on each version
-for a given CrmRequest hlink,
-look at the HlinkFromText and HlinkToText attributes to
get the CQ defect number
in order to determine what defects are associated with what code.
Am I missing anything? Is there a better way? Etc.
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. 162
To unsubscribe, send email to
[email protected] and put these words in the
message body: unsubscribe clearquest