PTP/release engineering

Overview

Note: this is now (October 2008) outdated; builds now run on the eclipse.org build machine; we need to update this page.

Building a PTP release involves a number of steps that must be carried out on both a local machine (generally your workstation) and a remote machine (build.eclipse.org). This document describes these steps.

Preparation

You will require an Eclipse installation on your local machine (architecture is not important). Follow the instructions here for details on how to set up your environment to build the required version of PTP. In addition, you will need to check out the releng/org.eclipse.ptp-update plugin. This plugin contains the PTP update site and other build tools.

Building an update site

Open the org.eclipse.ptp-update plugin and then the site.xml file.

Expand the Parallel Tools Platform category and verify that the version numbers (excluding the qualifiers) are correct for each feature. If the version number of a feature has been incremented, you will need to remove and re-add the feature from the list.

Click on Build All.

Once the build completes you should see the plugins and features folders populated with new files.

Packaging the update site

The remaining actions must be undertake from the command-line. From here on it is assumed that you have a terminal window open.

Change to the update site plugin directory:

cd workspace/org.eclipse.ptp-update

Run the command:

sh update_ptp

This will generate a zip file called ptp-updatesite-version.zip where version is the version of the build.

Signing the plugins

Copy the zip file to build.eclipse.org using the command:

scp ptp-updatesite-version.zip user@build.eclipse.org:/opt/public/download-staging.priv/tools/ptp

where user is your committer user ID.

Next, run the command:

ssh user@build.eclipse.org sign /opt/public/download-staging.priv/tools/ptp/ptp-updatesite-version.zip mail

This will begin the signing process and you will be sent an email when it is completed.

Installing the update site

Move the signed zip file to the release directory with the command:

ssh user@build.eclipse.org mv /opt/public/download-staging.priv/tools/ptp/ptp-updatesite-version.zip downloads/tools/ptp/releases/2.0

Remove the old update site plugins and features:

ssh user@build.eclipse.org "(cd downloads/tools/ptp/releases/2.0; rm plugins/* features/*)"

Unzip the update site using the following command. Answer "A" (All) if you are asked to overwrite any files.

ssh user@build.eclipse.org "(cd downloads/tools/ptp/releases/2.0; unzip ptp-updatesite-version.zip)"

Create individual components

Copy the signed update site back to the org.eclipse.ptp-update directory on your local machine. It should be ok to overwrite the unsigned version.

scp user@build.eclipse.org:downloads/tools/ptp/releases/2.0/ptp-updatesite-version.zip .

Run the make_archives script on the zip file. This will create a number of zip and tar.gz files in the local directory:

sh make_archives ptp-updatesite-version.zip

Remove the old component files from the downloads site:

ssh user@build.eclipse.org "rm -f downloads/tools/ptp/release/2.0/org.eclipse.ptp* downloads/tools/ptp/releases/2.0/ptp_proxy*"

Copy the new zip and tar.gz files up to the download site:

scp org.eclipse.ptp* ptp_proxy* user@build.eclipse.org:downloads/tools/ptp/releases/2.0

Update the downloads page

Update the downloads.php page with the new release information.