Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "DTPReleaseContributionInstructions"
(Created page with "==Preparing DTP Milestone Update Site== The uploading of nightly builds is automatically done by the DTP build scripts, including files upload and downloads page updates. To ...") |
m (→Contributing DTP Milestone to Eclipse Simultaneous Release) |
||
Line 48: | Line 48: | ||
==Contributing DTP Milestone to Eclipse Simultaneous Release== | ==Contributing DTP Milestone to Eclipse Simultaneous Release== | ||
+ | |||
+ | ==Updating the downloadable zip file links in the DTP downloads page== |
Revision as of 20:35, 10 February 2014
Preparing DTP Milestone Update Site
The uploading of nightly builds is automatically done by the DTP build scripts, including files upload and downloads page updates.
To promote a nightly/integration build as Milestone build, login to “build.eclipse.org” with shell access.
A build administrator user account has a $HOME/downloads link, which should already be setup as a symbolic link to the downloads site.
1. Copy the update site contents from the appropriate Nightly build directory to the Milestone build directory on "build.eclipse.org". For example,
- DTP 1.11.2 Milestone update site directory: ~/downloads/datatools/downloads/drops/M_updates_1.11.2
- DTP 1.11.2 Nightly update site directory: ~/downloads/datatools/downloads/drops/N_updates_1.11.2/v<buildTimestamp>
1.1 Create a new directory for staging milestone update site, e.g.
- ~/downloads/datatools/downloads/drops/M_updates_1.11.2_rc2
1.2 Copy the features and plugins folders from a Nightly build directory to the staging milestone directory
1.3 Copy the file “site.xml” from the last milestone directory to the staging directory, e.g.
cd ~/downloads/datatools/downloads/drops cp M_updates_1.11.2/site.xml M_updates_1.11.2_rc2
1.4 Edit the site.xml file in the staging milestone directory
- Update the value of the feature url and version attributes to the version of the 2 top-level feature jars found in the features directory (that were copied in a previous step). For example,
<feature url="features/org.eclipse.datatools.sdk.feature_1.11.2.v201309171554-7PAi7gFEpPZGKx8iIz--V5Urairv.jar" id="org.eclipse.datatools.sdk.feature" version="1.11.2.v201309171554-7PAi7gFEpPZGKx8iIz--V5Urairv">
<feature url="features/org.eclipse.datatools.enablement.sdk.feature_1.11.2.v201309171554-7I9v7XFE9JgQO0wJBYD1THz0pOhh.jar" id="org.eclipse.datatools.enablement.sdk.feature" version="1.11.2.v201309171554-7I9v7XFE9JgQO0wJBYD1THz0pOhh">
1.5 Generate the P2 metadata files (artifacts.jar and content.jar) in the staging milestone directory
- (See the script and related directories packaged in ~/downloads/datatools/tools/dtp-tools.tar.
- Extract from dtp-tools.tar to your own account working area, as needed. Then “unzip jdk15.zip” for the JVM to use in below command.)
- Run below command, having substituted the appropriate target update site directory name, e.g. substitute "M_updates_<version>_<staging>" with “M_updates_1.11.2_rc2”.
- The generated artifacts.jar and content.jar files will be written to the directory specified by the –targetDir argument.
./buildUpdateSiteMetadata.sh -p DTP -basebuilderDir ${HOME}/dtp-tools/org.eclipse.releng.basebuilder -targetDir ${HOME}/downloads/datatools/downloads/drops/M_updates_<version>_<staging> -vm ${HOME}/dtp-tools/jdk1.5.0_09/bin/java &
When ready to promote the milestone build,
1.6 Rename the last milestone directory for backup, e.g.
mv M_updates_1.11.2 M_updates_1.11.2_rc1
1.7 Rename the staging milestone directory to the milestone directory, as specified in site.xml; e.g.
mv M_updates_1.11.2_rc2 M_updates_1.11.2