Jump to: navigation, search

Difference between revisions of "DTP Source Code Repository"

m (Migration from CVS to Git)
(Migration from CVS to Git)
Line 1: Line 1:
 
{{Back To|name=DTP Main Page|href=Data Tools Platform Project}}  
 
{{Back To|name=DTP Main Page|href=Data Tools Platform Project}}  
  
== Migration from CVS to Git ==
+
== Migration from CVS to Git ==
  
DTP source code repository has been maintained on CVS since the beginning of the project. After the Indigo release (DTP 1.9), the DTP project is planning to migrate our source code repository from Eclipse CVS to Git. This is in line with the overall direction of Eclipse projects. We also want to take the opportunity to refine the source code organization and clean up obsolete plug-ins, as part of the migration.  
+
DTP source code repository has been maintained on CVS since the beginning of the DTP project. After the Indigo release (DTP 1.9), the DTP project migrated our source code repository from Eclipse CVS to Git. This is in line with the overall direction of Eclipse projects. We also took the opportunity to refine the source code organization and cleaned up obsolete plug-ins, as part of the migration.  
  
We are essentially migrating the DTP CVS Head branch to Git, and it will include the history in CVS.
+
We have essentially migrated the DTP CVS Head branch to Git, which includes the history in CVS at the time of migration. Starting from [http://wiki.eclipse.org/DTP_1.9.1_Schedule_and_Rampdown_Policy DTP 1.9.1] (Indigo SR1 release) and on, builds are made from the '''master''' branch in the Eclipse DTP Git source code repositories.  
Starting from [http://wiki.eclipse.org/DTP_1.9.1_Schedule_and_Rampdown_Policy DTP 1.9.1] (Indigo SR1 release) and on, builds are made from the '''master''' branch in the Eclipse DTP Git source code repositories.
+
If there is ever a need to build DTP 1.9 or older version, it should still grab the source from corresponding CVS branches.  
+
  
=== Migration Schedule ===
+
The source repository for DTP 1.9.0 and earlier versions are maintained in CVS only.
The migration process has completed. It occurred between 7/18/2011 and 7/25/2011.
+
Continued use of DTP CVS for the earlier versions would accommodate:
 +
*Adopters using products or applications based on DTP 1.9.0 or earlier, and which does not have a Git client<br>
 +
*Any tools, build scripts and web sites with existing pointers into the DTP CVS repository
 +
 
 +
If there is a need to build DTP 1.9.0 or earlier version, it should still pull the source from corresponding CVS branches. Any back-port to these branches, if needed, must be done in DTP CVS as well.
 +
 
 +
We are thus keeping the DTP CVS repository writable after the Git migration (for the time being), to allow commits to the earlier branches.  Note that CVS Head will not be used by the DTP builds. We plan to delete all content from HEAD in CVS to avoid confusion.
 +
 +
=== Migration Schedule ===
 +
 
 +
The migration process has completed. It occurred between 7/18/2011 and 7/25/2011.  
  
 
The migration tasks mainly involved importing related files and CVS history over to the new Git repositories (1 day), running tools to verify the repos (2-3 days), and running test builds from the Git repos (1 day).
 
The migration tasks mainly involved importing related files and CVS history over to the new Git repositories (1 day), running tools to verify the repos (2-3 days), and running test builds from the Git repos (1 day).

Revision as of 19:54, 29 July 2011

Back to DTP Main Page


Migration from CVS to Git

DTP source code repository has been maintained on CVS since the beginning of the DTP project. After the Indigo release (DTP 1.9), the DTP project migrated our source code repository from Eclipse CVS to Git. This is in line with the overall direction of Eclipse projects. We also took the opportunity to refine the source code organization and cleaned up obsolete plug-ins, as part of the migration.

We have essentially migrated the DTP CVS Head branch to Git, which includes the history in CVS at the time of migration. Starting from DTP 1.9.1 (Indigo SR1 release) and on, builds are made from the master branch in the Eclipse DTP Git source code repositories.

The source repository for DTP 1.9.0 and earlier versions are maintained in CVS only. Continued use of DTP CVS for the earlier versions would accommodate:

  • Adopters using products or applications based on DTP 1.9.0 or earlier, and which does not have a Git client
  • Any tools, build scripts and web sites with existing pointers into the DTP CVS repository

If there is a need to build DTP 1.9.0 or earlier version, it should still pull the source from corresponding CVS branches. Any back-port to these branches, if needed, must be done in DTP CVS as well.

We are thus keeping the DTP CVS repository writable after the Git migration (for the time being), to allow commits to the earlier branches. Note that CVS Head will not be used by the DTP builds. We plan to delete all content from HEAD in CVS to avoid confusion.

Migration Schedule

The migration process has completed. It occurred between 7/18/2011 and 7/25/2011.

The migration tasks mainly involved importing related files and CVS history over to the new Git repositories (1 day), running tools to verify the repos (2-3 days), and running test builds from the Git repos (1 day).

DTP Git Repository Organization

Separate Git repository will be created for each DTP sub-project. The main guideline used for the repository split is to group those highly-related projects that are likely maintained by the same set of committers.

Below are the list of separate DTP Git repositories. See the spreadsheet for the proposed directory structure and content in each Git repository. Note that obsolete or archived plug-in projects will not be migrated, and are thus not included in the Git repositories.

Separate Git source repositories for each sub-project and enablement groupings

  • org.eclipse.datatools.connectivity.git
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.connectivity.git
  • org.eclipse.datatools.modelbase.git
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.modelbase.git
  • org.eclipse.datatools.sqltools.git
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.sqltools.git 
  • org.eclipse.datatools.enablement.<vendor>.git

            where <vendor> are: hsqldb, ibm, ingres, msft, mysql, oda, oracle, postgresql, sap, sqlite, sybase

ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.enablement.hsqldb.git 
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.enablement.ibm.git 
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.enablement.ingres.git 
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.enablement.msft.git 
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.enablement.mysql.git 
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.enablement.oda.git 
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.enablement.oracle.git 
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.enablement.postgresql.git
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.enablement.sap.git 
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.enablement.sqlite.git 
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.enablement.sybase.git 
  • org.eclipse.datatools.enablement.general.git -- contains non-vendor specific enablement plugin projects
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.enablement.general.git 
  • org.eclipse.datatools.incubator.git
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.incubator.git

Each of the above source repositories contains the following sub-folders, if content exists:

  • plugins/  : contains source plug-in projects
  • releng/  : contains map file of the source plug-in projects
  • tests/  : contains unit test plug-ins
  • examples/ : exemplary implementation projects


Additional separate Git repositories for non-source projects

  • org.eclipse.datatools.build.git
  • org.eclipse.datatools.doc.git
  • org.eclipse.datatools.nl.git
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.build.git 
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.doc.git 
ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.nl.git

Browsing Remote Git Repositories

Use a web browser to browse the content of the Eclipse DTP Git repositories.

Resources for getting familiarized with Git

Some Useful EGit/Git Documentation

Temporary Test Git Repositories

We have created a few temporary test Git repositories on github.com. Note that the directory structures found in these test repos are not the proposed ones. (See the spreadsheet referenced above for the proposed directory structures.)

To write (e.g. push) to the DTP test remote repos on github, it will need a password: Actuate2011


Browsing Remote Test Git Repositories

To browse the content of a remote Git repo, use a web browser with the remote repo URL, e.g.