Topic
  • 3 replies
  • Latest Post - ‏2013-02-05T09:53:30Z by GKellner
michelei
michelei
22 Posts

Pinned topic Best way to isolate ClearCase source code

‏2013-02-01T10:50:15Z |
Hi all,

we need to share part o four source code to an external sw house.
We use CCase 2003.06.10 and we want to give them remote access to our pc in order to checkout and checkin files.

Which is the best solution to make them working only on their VOB? we don't want they can see the other VOBs.

CLearCase 8 (we ahve planned the migration) can help us more?

Thanks!
michele
Updated on 2013-02-05T09:53:30Z at 2013-02-05T09:53:30Z by GKellner
  • jeff98air
    jeff98air
    817 Posts

    Re: Best way to isolate ClearCase source code

    ‏2013-02-01T18:09:06Z  
    If you have a separate PC that will be dedicated as their remote server, then I would create a new ClearCase region (cleartool mkregion) just for their use and set that remote server to the new region. Then, only tag the VOBs you wish to give them access to in that region (cleartool mktag). Only VOBs and views tagged to the new region will be visible from that remote server.

    -Jeff Ng
  • michelei
    michelei
    22 Posts

    Re: Best way to isolate ClearCase source code

    ‏2013-02-05T08:03:42Z  
    • jeff98air
    • ‏2013-02-01T18:09:06Z
    If you have a separate PC that will be dedicated as their remote server, then I would create a new ClearCase region (cleartool mkregion) just for their use and set that remote server to the new region. Then, only tag the VOBs you wish to give them access to in that region (cleartool mktag). Only VOBs and views tagged to the new region will be visible from that remote server.

    -Jeff Ng
    thanks!
    I will try soon
    have a nice day

    michele
  • GKellner
    GKellner
    259 Posts

    Re: Best way to isolate ClearCase source code

    ‏2013-02-05T09:53:30Z  
    • michelei
    • ‏2013-02-05T08:03:42Z
    thanks!
    I will try soon
    have a nice day

    michele
    But be careful with the security rights for the users on those clients.
    If they can switch the region, they can see/access the other VOBs.

    So you would need an extra access group for those users at the VOB share or below, depending on your file system structure.

    greetings georg.