Community
Participate
Working Groups
(After Indigo) move EPP from CVS to git
+1
Created attachment 211746 [details] List of EPP projects and their migration strategy *Now* is the best time for a Git migration - Indigo SR2 is out of the door and we are still in time for Juno. The attached file includes a list of all EPP bundles, features, tests, releng projects, etc. that are available in CVS today, and my proposed strategy (migrated, archive) because IMO many of them should be archived. The rough overview: [1] EPP Release Documentation - MIGRATE TO ITS OWN GIT REPOSITORY [2] EPP Packages - MIGRATE TO ITS OWN GIT REPOSITORY [3] EPP Usage Data Collector - OPEN (PROPOSAL: MIGRATE TO ITS OWN GIT REPOSITORY, then discuss when/if it should be archived) [4] EPP Wizard - TO BE ARCHIVED, NO GIT MIGRATION [5] EPP Installer - TO BE ARCHIVED, NO GIT MIGRATION This means I'd like to clean up and end with only two or three Git repositories.
FWIW, I like the strategy proposed, Markus.
I tagged CVS HEAD a last time with the tag GIT_MIGRATION.
Transformation of CVS authors in commit messages to Git user.name and user.email: I looked into the commit logs of other Git repositories at eclipse.org and used the values that I found there, i.e. if I found the *correct real name* of the person I am using this one, the committer ID otherwise; if I found the *correct email address* I am using this one, the committer ID otherwise. I contacted some committers that had no commits in existing Git repositories by mail and will use what they told me.
Current status: See http://git.eclipse.org/c/epp There are now 4 different Git repositories: [1] /gitroot/epp/org.eclipse.epp.packages.git Contains everything required for building the packages. [2] /gitroot/epp/org.eclipse.epp.usagedata.git The EPP Usage Data Collector - to be archived some time in the future [3] /gitroot/epp/org.eclipse.epp.doc.release.git The release review documentation [4] /gitroot/epp/org.eclipse.epp.old.git 'Everything else', i.e. everything that is not maintained at the moment, e.g. the installer and the wizard. In my attached list I wrote that I am not going to migrate these bits, but yesterday I thought that it might be handy to have everything from the old EPP CVS migrated to Git. Next steps, probably next week: Adjustments to the Juno package build!
Ah, and I updated the source code repository locations in the Eclipse Portal!
Updated the Git repositories in our ohloh listing: https://www.ohloh.net/p/epp
In order to reach the old status quo as soon as possible after the Git migration, I updated the Buckinster-based parts of the build with the new Git repository locations. A pretty easy step I have to say. It's now working locally on my machine, but I am unable to get anything running on Hudson today. > ant -file /PATH/TO/LOCAL/org.eclipse.epp.packages.git/features/org.eclipse.epp.allpackages.juno.feature/build.xml -Dbm.headless.site=http://build.eclipse.org/technology/epp/buckminster/1.2.1.r11564/ -Djuno.site=http://download.eclipse.org/releases/staging -Dbuild.root=/tmp/epp.build -Dplatform.site=http://download.eclipse.org/eclipse/updates/4.2milestones/S-4.2M5-201201271145 -Ddirector.url=http://download.eclipse.org/tools/buckminster/products/org.eclipse.equinox.p2.director.product_1.4.0.v20110313-0656.zip clean.workspace build.site
https://hudson.eclipse.org/hudson/job/juno.epp-repository-build/ and https://hudson.eclipse.org/hudson/job/juno.epp-package-build/ are working again. There are some minor issues left, i.e. * Checking the qualifiers that are generated for the features and plugins based on the repository last-modification date. * Change the way the startEPPJuno.sh file moves the package description files into their final location.
Remaining issues have been solved. Closing bug as FIXED.
