Fail on views that have hardcoded vobs in config spec

Bug #592228 reported by Jens Brejner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Accelerated ClearCase
New
Undecided
Unassigned

Bug Description

View time stamper encounters a problem in the following scenario.
Multiple ClearCase regions, and vobs are tagged with different names in each vob.
Example
Region A
vobtag \avob points to \\server\share\anyvob.vbs
Region B
vobtag \bvob points to \\server\share\anyvob.vbs

Now if the default region is A, then the view-server runs in region A, so view_timestamper will be executed there.
And if there in region B is a view that has a config spec which names the vob \bvob, the call to cleartool setcs -current fails, because ClearCase tries to validate the config spec while setting it.

This can not be fixed in the script, but can be avoided by using the same vobtag in all regions, or by using the vobuuid syntax in the config spec - but that is really ugly.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.