How to manage xCP 2 Application using Source Control System?

Hi,

xCP Designer is not internally integrated with SVN or any other source code plugin, but still probably we can map Application folder to SVN so that multple developers can work I think.

Has anyone made a setup and what are the challenges? So eqch developer shares the same code but different deployment environment?

Does it mean same code base but different application name for each developer on the same xMS Server Or the entire codebase and application name but different xMS server instances 5if possible)?

Can someone guide on the steps they followed to create the setup

-- Anurag

Find more posts tagged with

Comments

AlanZ

Your question has been moved to the Documentum developer community where it has a better chance of being seen and answered

pettitk

the help file says:

EMC Documentum xCP Designer Help > Creating Applications and Projects > Tasks

--------------------------------------------------------------------------------

Working with a source control system

You can use a third-party source control system to manage application resources. All source control actions are initiated through the third-party source control client. The following high-level steps summarize how to use a third-party source control system to manage resources:

1.Install the source control repository and client.

2.Create an xCP Designer application on your file system.

3.Add the application root folder to the source control repository.

Exclude the following folders (indicated with a forward slash) and files when adding the application root folder and its contents to the repository:

•configuration/

•gen/

•META-INF/

•target/

•.index

•.generatedresources

•runapp.log

4.Verify that the application is under source control by confirming the following folders (indicated with a forward slash) and files are in the repository:

•.settings/

•Artifacts/

•content/

•lib/

•src/

•.classpath

•.project

•build.properties

•pom.xml

5.To work with an application that another developer has added to the source control repository:

a.Check out the application from the source control repository to the checkout directory on your file system.

b.Import the application into your xCP Designer environment.

Do not select the option to import a copy of the application.

c.After you update shared resources, check them into the source control repository.

d.To get changes that were checked in by other developers, use your source control client to synchronize your local file system with the changes from the source control repository and then click Refresh on the xCP Designer toolbar to pick up the latest changes.

Refer to the documentation for your source control system for more information on setting up a source control system and using the source control client to complete source control actions.

Related tasks

Adding a library

Importing a project

Importing an application

carlosanchez-g2dHi

Hello,

I'm currently trying to set up the svn following your recommendations. When we import the project (not performing the copy files) the new project is not available to open.

I've noticed that not all of the files listed exist on the folder (i.e. build.properties) Is the same process followed to achieve this in xCP 2.1?

Regards

a.ardashov

Hello, Carlos,

Try to revise next topic.

carlosanchez-g2dHi

Yes, thank you.

I ended up doing Option A. (Creating the blank application and then sync with the SVN repository) the other one wouldn't work (tired it several times deleting cache, maven repository,....).

There guide is quite accurate but there are still some files like runtimeappconfig.rtappconfig that should be kept local in the Artifacts project.