Multiple Version Control Id's

[JeffM]

Does anyone know if there is a way to avoid having to log onto every different version control "ID"  when opening an EA Project?

I.e., I have multiple unique ID's/ Projects [paths] set up to allow individual groups to manage their own files within their Groups project folders located in different file path locations and this works great but when opening the EA project it prompts for a sign-in to every unique assignment [without even indicating which one you're logging onto].  So is there a way to supress this, or automate the process?  I know there is an option to "Use current project for all files under source control" but these are different projects in the same version control system and therefore need different assignments in EA.

FYI - These are all connected to the same server/version control system so I am really being asked to sign into all the different "projects" within the version control system.  Also, we're using a central Oracle repository.

Thanks.
Jeff M.

[JeffM]

Just moving this up... didn't want it to get completely lost as I'm at a loss on this.  It doesn't appear that EA works with Version Control very well... I'd think it'd be able to save each version control connection and log on automatically, or at least in a more streamlined way.  

If I were to add 20 projects in different locations on the same server I'd have to sign on 20 times each time I opened the file/repository.  That's nuts man.  I know the solution is to just create one Project and break it into subfolders and then select "Use current project for all files under source control" but that isn't what has been requested, so again if anyone has any insight I'll take it.

Thanks.
Jeff M.

[HowardB]

Hello Jeff,

I am assuming that you are using an SCC version control product, as the description of the problem you are having does not fit either CVS or Subversion.

EA supports SCC products through the MS SCC API specification.  This specification does NOT include any way to "log in" to a project (at least, not in the version that I have).  However, neither does it preclude an SCC provider from displaying a dialog prompting users to log in, when connecting to a project.  

If your version control product requires that you "log in" each time you connect to a project, this is something that is outside of the SCC specification.  Maybe that product itself has some option or registry setting that allows for automatic logins.  I am afraid you will need to seek support through your VC product's vendor.

I know we had a similar issue in the past with a user trying to write EA automation scripts to connect to SourceGear Vault.  The response from SourceGear at that time was that we cannot automate the login through the SCC interface.

I hope this sheds some light on the problem.

Regards,
Howard.

[JeffM]

Thank you for the info... and yes I'm a moron I never even indicated that we are using Starteam SCC integration.  I've been looking at that since I now believe the requirement comes from outside of EA - i.e., the StarTeam SCC login is required in the starteam component.

I think my easy solution will be to suggest one starteam project for EA and place group subfolders there.  That way I can just use that "Use current project for all files under source control" checkbox and be done with it.

BUT, if I get the time and/or find a solution I'll post it so that someone else may be able to benefit.

Jeff M.