Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PTP/release engineering"
(→Building An Update Site) |
|||
| Line 25: | Line 25: | ||
== Signing the plugins == | == Signing the plugins == | ||
| − | # Copy the zip file to build.eclipse.org:/opt/public/download-staging.priv/tools/ptp | + | # Copy the zip file to build.eclipse.org using the command <code>scp ptp-updatesite-''version''.zip ''user''@build.eclipse.org:/opt/public/download-staging.priv/tools/ptp</code> where <code>''user''</code> is your committer user ID. |
# Run the command <code>ssh user@build.eclipse.org sign /opt/public/download-staging.priv/tools/ptp/ptp-updatesite-''version''.zip mail</code>. This will begin the signing process and you will be sent an email when it is completed. | # Run the command <code>ssh user@build.eclipse.org sign /opt/public/download-staging.priv/tools/ptp/ptp-updatesite-''version''.zip mail</code>. 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 <code>ssh ''user''@build.eclipse.org mv /opt/public/download-staging.priv/tools/ptp/ptp-updatesite-''version''.zip downloads/tools/ptp/releases/2.0</code> | ||
| + | # Unzip the update site using the command <code>ssh ''user''@build.eclipse.org "(cd downloads/tools/ptp/releases/2.0; unzip ptp-updatesite-''version'')"</code>. ''NOTE THAT THIS WILL OVERWRITE THE EXISTING UPDATE SITE.'' | ||
Revision as of 11:31, 6 June 2008
Contents
Overview
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.xmlfile. - Expand theParallel 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
workspace/org.eclipse.ptp-updatedirectory. - Run the command
./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/ptpwhereuseris your committer user ID. - 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 - Unzip the update site using the command
ssh user@build.eclipse.org "(cd downloads/tools/ptp/releases/2.0; unzip ptp-updatesite-version)". NOTE THAT THIS WILL OVERWRITE THE EXISTING UPDATE SITE.