Messages

1

General Board / Re: EA Corporate Deployment question

« on: April 22, 2009, 11:28:42 pm »

Thanks for the help everyone.

There will be three developers using the same model, but I am the only one using EA right now. I'm trying to determine what our configuration should be to allow sharing between developers, have the model under version control, and also be able to share some packages between projects. My evaluation "testing" was with me as a user on two different machines. That may have affected the outcome.

For my setup I had a shared EAP file and the packages within the model were under version control. We are using the SCC interface with IBM/Rational ClearCase. What I saw was that when I checked out a package on one computer, the package also showed as checked out from the other computer, making it modifiable for both "users".

What I overlooked was that I am the same user on both machines with the same working directory in the version control system. I will have to try a more realistic test one of our other developers.

2

General Board / Re: EA Corporate Deployment question

« on: April 21, 2009, 07:52:37 am »

I have a related question:

After some preliminary testing it seems that if you are using shared storage (I'm using a shared .EAP file) and have packages in your model under version control, whenever any user checks out a package from version control the package is checked out (and modifiable) for anyone else using the shared model.

I was hoping for a deployment where the package would only be changing for the user that had it checked out until it was checked back in.

I would like to avoid putting the .EAP file itself under version control, but I'm not sure what the other options would be. We want to have some of the individual packages under separate version control so that they can be shared across projects. Putting the EAP file under version control as well seems redundant, locks everyone out of the entire project while someone is making changes, and uses more storage space.

I also thought about having each user have their own local/private project file and just import the root of the model, which could be under version control. Seems like it would work. The only thing I didn't like about that option is that there isn't a centrally located EAP file that a non-developer could view (e.g. using EA Lite). We would have to manually save one somewhere periodically.

Any other thoughts? How do people deal with this?

Thanks,

Darin

3

Bugs and Issues / Re: Importing Source Controlled Package

« on: April 23, 2009, 04:33:30 am »

I don't know what version of EA you have, but there is a section 9.6.6 in the EA User Guide for 7.5 (you can download if you don't already have it) that describes how to do it.

It says to right click on the package you want to be the parent package, select Package Control..., then Get Package...

You'll be prompted to select a version control configuration, and then it will show a list of packages (xml files) already under source control. Select one and it will import it into the parent you selected.

I have tried this on 7.5 (and I believe I have done it on 7.1) and it worked for me. The "parent" package I selected was not at the top.

I've only been using EA for about a month, and haven't started a real project yet, so I'm definitely not an expert.