Importing Subversion repository contents to EWM

IBM® Engineering Workflow Management (EWM) includes a Subversion importer that simplifies importing files and folders from a Subversion repository and provides a variety of options for mapping Subversion repository contents and user names to Jazz™ components and users.

Subversion repository organization

When you import data from a Subversion repository, you must decide how to express the organization of the Subversion repository as one or more EWM components. An understanding of typical Subversion repository layouts can help you choose the best way to organize your import.

In the most common organization, the Subversion repository is divided into projects, each with its own tags and branches. Such an organization can be represented as a tree structure like this:

Project1
      trunk
         folder/plug-in1
         folder/plug-in2
      tags
      branches
Project2
      trunk
      tags
      branches

where folder/plug-in1 maps to a project in an Eclipse workspace.
It is also possible to have a repository that contains a single project, and has a simpler structure:

   trunk
     folder/plug-in1
      folder/plug-in2

   tags
   branches

EWM baselines and Subversion branch and tag points

Unless you are importing from a very simple Subversion repository, one that contains only a few revisions of one or two small projects, it is impractical to import the entire dump file in a single operation. Importing a single line of development at a time (the trunk, for example, or a branch) generates a set of component baselines that make it easier to use EWM tools on the imported projects.

By default, the importer creates EWM baselines that correspond to Subversion branch and tag points. Because of differences in the data model (EWM uses change sets and Subversion does not), these mappings do not always have a one-to-one correspondence.

Repository database configuration guidelines

A Derby-based Jazz repository might not be suitable for imported Subversion repositories that have large histories (greater than 5000 revisions). Other databases supported by EWM are better for this purpose. For repositories based on Db2®, consider setting the property

com.ibm.team.repository.db.db2.content.tablespace.numpages

to a higher value. As a rule, 250000 Db2 pages will accommodate 10000 Subversion revisions.

Client configuration guidelines

When you are importing from a Subversion repository with a long history, the server connection might time out before the imported stream has been created. To avoid this, right-click the repository connection in the Team Artifacts view and click Properties. In the Jazz Repository Connection properties, set the Connection Timeout to a high value, such as 3600 (which causes the client to wait for one hour before displaying a connection time-out error). Even if the connection does time out, the operation will continue until it completes.


video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki