I am using Sparx Enterprise Architect with a SQL Server Repository. We wish to take baselines in order to manage change and be able to compare packages and be able to revert to a previous baseline. When using the baseline facility the baseline is saved to a local temporary folder, this means that other users of the repository cannot see or access these local baselines. We have user authentication turned on.
How can I change the default directory the baseline is being saved to? I have searched the EA menus, Sparx documentation and the internet for a way of doing this and come up with nothing. Or alternatively, is there a way for the baselines to be saved in the repository itself so all can access them?
We could use the export to XMI function but it seems to me the baseline was created to be able to do what we want without this.
Location baseline saved to by default:
Related
In eclipse we have possibility to create psf file using Export --> Team Project set and use that psf to create new workspace code.
Is there a similar possbility in ALM to get the information out of snapshot and use it as psf?
This is not exactly like a project set file (psf), but in RTC, you can memorize the exact state of multiple repos (here in RTC "components") with a stream.
By communicating the stream name, any collaborator can create a repo workspace on that stream and checkout (in his/her own sandbox) the components.
That is what you find in this thread for instance::
Instead of a .psf file, you would use an RTC stream.
When someone has changes that they want to make visible to the rest of
the team, instead of updating the .psf file, they would deliver their
changes to the RTC stream.
Conversely, when you want to catch up to
the changes being made by other team members, you would accept changes
from stream (rather than pulling a set of tags).
See also this thread:
A team project-set (Eclipse) can be exported to a .psf file while working-sets are part of your preferences.
The team project-set was added to eclipse to augment SCM systems which didn't make it easy to bootstrap and get the right line-up of projects.
In Jazz we recommend you setup a stream with the component/projects your team members need to work on and they can simply create their own repo workspace and load it.
When a repo workspace is loaded, we automatically create a working-set for each component that is loaded, as the documentation quote above mentions.
I have been reading about version control in enterprise architect. Here is a small scenario that I have. Can anyone please tell me how enterprise architect behaves in such a situation.
Suppose the package is being shared by 3 users and the package has a number of classes each having some activity diagrams and state machines.
Incase a user A makes any changes to one of the state machines and commits his changes.
Will these changes be reflected in the diagrams of the other users as well if the user updates his copy.
Thank you guys
Of course, it supposed to behave like this.
Why don't you try it?
Create a repository and local copy of version control.
Then from EA add packages to the version control and start testing.
Wonderfull material about EA with version control can be found here :
Best Practices
Implementation in EA is described clearly here
Creating SVN repository can be done easily with visual svn
Creating local copies of svn can be done with Tortoise svn
Good luck!
I am working on a ModX website (mainly templates but also system settings, user management, etc) while a development website is already online with the customer starting to input the content.
I haven't found a practical solution to push my work online (layouts are stored in the database) without overriding the content input by the customer (in the database as well).
My present workflow consists of first replacing my local modx_site_content table with the one extracted from the online database, then push this hybrid database online. Not practicle, plus I am not sure user changes are confined to modx_site_content only.
There must be a better workflow though! How do you handle this?
I don't think it gets any easier than selecting the tables you need and exporting only those into the live environment. Assuming you only work on templating, the template, snippet & chunk tables are all you need to export.
We usually take a copy, develop, and merge only once when the new features are supposed to go live this minimizes this trouble. Also the client can continue normally until d-day.
If youre doing a lot of snippet work you could always just include an actual php file instead and work with your editor directly towards those files, connect them to git and what not.
If you project is not really big, you can store your chunks/resources, etc. in a separate files (there is and option called "Static Resource"), and then, manage your changes with git. Otherwise, you need to store user data in a separate table and deploy the whole database with Fabric, for example.
If two people are working on the same EAP file and later want to merge it. Can they do it?
Is it possible to merge two EAP files?
My original, accepted answer: (also note the 2018 update below)
Have a look at this manual section:
http://www.sparxsystems.com/enterprise_architect_user_guide/projects_and_teams/teamdevelopment.html
As with all collaboration, there is a chance for raising conflicts when more that one person works on the same data.
From EA's side the most straightforward approach is the XMI transfer (import/export).
If you collaborate on a regular basis you might want to setup more advanced version control. (see above weblink) Careful, the feature availability depends on the EA version that you use.
As pointed out here it is possible for small teams to access and work on the exact same file on the FS.
Update from 2018:
The user guide has been updated and is available through new URLs. The current user guide page now differentiates methods for
network deployment of EA files
Replication (including a sub-page that also deals with resolving merge conflicts)
XMI Export / Import
In the meanwhile there is a 3rd party solution of LieberLieber avbailable, the Model Versioner, with which you can diff and merge EAP files on the model level:
https://lemontree.lieberlieber.com
Going forward, our group will be developing .NET apps using TFS, and the application lifecycle management will be great.
We also have a lot of legacy java apps that we currently version by zipping them up and throwing them in source safe. Or an other example would be a couple of stored procedures used for a report or scheduled job, we want them versioned and backed up with the rest of our source.
Can we achieve that same sort of one off functionality using TFS? We'd like all of our source in one place, but some of it just needs to be very simple. Thanks for your help.
Yes.
TFS is made to handle your scenario- not just to manage your SDLC and .NET applications.
For example, we store our legacy SPs and documentation in TFS. You can have those files versioned with your development branch too if you so desire. Essentially anything you can do with the code for your .NET application in terms of versioning you can achieve with all of your legacy files as well.
So you can feel confident, moving forward, that your choice to move to TFS is the right one if that is your only outstanding concern.
How to Add Files
Go to Source Control Explorer (View -> Other Windows -> Source Control Explorer or Double Click in Team Explorer View).
Navigate to where you want to store your legacy files in the structure or if you need to create a new folder to store the files (Icon is on the left of the toolbar).
Once the folder is created, click the icon with a little plus beside it to the right of the new folder icon to "Add Items to Folders." You can also right-click in the window to the right-hand side that shows you the files in the folder and both create new folders and add files to the folder.
Inside of this dialogue you can select your legacy files and add them to TFS.