CC Synchronization Dyn View Config Spec for Base ClearCase
We understand why /main/0 is the final rule in the DO_NOT_USE dynamic view for a ClearCase Synchronization stream with UCM ClearCase, but why base ClearCase? We don't use /main/0 in our base ClearCase dyn views. The result is the sync process cannot 'see' anything in the base ClearCase VOB unless we merge everything from the dev branch to the sync branch, but even then, not everything is on the dev branch as the dev config spec is also based on /main/LATEST. Will it cause harm if we update the DO_NOT_USE dyn view config spec to replace /main/0 with /main/LATEST? We tried but it complained about /main/LATEST not matching /main/0 and we are unsure of exactly what it is comparing to. Has anyone run into this?
Thanks,
Tim
Thanks,
Tim
3 answers
No, you can't play games with that config spec (:-).
In particular, in order to do a fast "diff" to see what files have
changed since the last sync, the sync algorithm needs to have a very
specific kind of config spec in that view.
But if you just want to sync with /main/LATEST, that's easy to do ...
just select "main" as the ClearCase branch you want to sync with.
BUT ... remember that the sync branch is locked during the duration of
the sync, so that means nobody will be able to checkin to /main while
the sync is running.
Cheers,
Geoff
On 5/12/2010 8:23 AM, timothy.mulligan wrote:
In particular, in order to do a fast "diff" to see what files have
changed since the last sync, the sync algorithm needs to have a very
specific kind of config spec in that view.
But if you just want to sync with /main/LATEST, that's easy to do ...
just select "main" as the ClearCase branch you want to sync with.
BUT ... remember that the sync branch is locked during the duration of
the sync, so that means nobody will be able to checkin to /main while
the sync is running.
Cheers,
Geoff
On 5/12/2010 8:23 AM, timothy.mulligan wrote:
We understand why /main/0 is the final rule in the DO_NOT_USE dynamic
view for a ClearCase Synchronization stream with UCM ClearCase, but
why base ClearCase? We don't use /main/0 in our base ClearCase dyn
views. The result is the sync process cannot 'see' anything in the
base ClearCase VOB unless we merge everything from the dev branch to
the sync branch, but even then, not everything is on the dev branch
as the dev config spec is also based on /main/LATEST. Will it cause
harm if we update the DO_NOT_USE dyn view config spec to replace
/main/0 with /main/LATEST? We tried but it complained about
/main/LATEST not matching /main/0 and we are unsure of exactly what
it is comparing to. Has anyone run into this?
Thanks,
Tim
In the "create synchronized stream" wizard, on the "ClearCase Stream
Information" page, in the "ClearCase branch type selector" field, type
in "main@\YOUR_VOB_NAME".
Cheers,
Geoff
On 5/13/2010 1:53 PM, mark.gentile wrote:
Information" page, in the "ClearCase branch type selector" field, type
in "main@\YOUR_VOB_NAME".
Cheers,
Geoff
On 5/13/2010 1:53 PM, mark.gentile wrote:
Geoff, I'm not sure what you mean by select the "main"
branch. Where do you select the "main" branch? Can you
please provide more detailed information?
--Mark