Book a Demo

Author Topic: Version Control on Terminal Server  (Read 2131 times)

michael.harding

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
  • EA User
    • View Profile
Version Control on Terminal Server
« on: August 07, 2006, 02:17:08 am »
I'm deploying a terminal server to support multiple users concurrently working on a single EA model.

My problem arises when configuring the Version Control Options for each user.

For example, assume the Unique ID for the repository is "model_repo".

If I setup the Version Control Configuration for user "John", the paths.txt file in the EA directory contains this:

Quote
%PATH%;type=Version Control;id=model_repo;path=C:\Profiles\John\svn\model_repo;


When configuring a subsequent user "Alice", the above entry in the paths.txt file is replaced by this:

Quote
%PATH%;type=Version Control;id=model_repo;path=C:\Profiles\Alice\svn\model_repo;


So it appears that EA only supports one configuration of a repository per machine - which creates problems when trying to give multiple users their own working copies on the terminal server.

The planned workaround is to share the profile directory and map it to a drive (on the same machine):

i.e. Share C:\Profiles

then

User John maps C:\Profiles\John to H:\
User Alice maps C:\Profiles\Alice to H:\

Then setup the local working copy for the "model_repo" repository to H:\svn\model_repo\

Therefore giving each user an effective path of:

C:\Profiles\User\svn\model_repo\

Anyone have a more elegant solution to this problem?

Cheers,
Mike


michael.harding

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
  • EA User
    • View Profile
Re: Version Control on Terminal Server
« Reply #1 on: August 10, 2006, 01:06:15 am »
Just to follow up, this setup appears to work correctly.
Still, would be nice to have the version control entries in paths.txt being owned by particular users.

Cheers,
Mike