Cloud Tools for Eclipse Release Instructions

Preparation

1. Update the version number in these three files. Commit/push/review/merge.

   features/com.google.cloud.tools.eclipse.suite.feature/pom.xml
   features/com.google.cloud.tools.eclipse.suite.feature/feature.xml
   gcp-repo/metadata.product
   

   • See #3003 for an example of the necessary changes.
   • Make sure to delete the branch after merging, both locally and remotely, to avoid potential branch/tag naming conflicts.
2. Tag the repo in GitHub. The tag name should be something like "v1.6.1A".
   • A tag in Git is basically a name to a particular commit. We will build a release against the code pointed to by this tag.
   • When needed to rebuild with new new fixes, go "v1.6.1B", "v1.6.1C", and forth.

Build

1. Trigger a release build on the command-line internally. Use the tag for which you want to build.
   • For the exact command, see the comment of the Kokoro job config: devtools/kokoro/config/prod/google-cloud-eclipse/ubuntu/new_release.cfg
   • This launches two Kokoro builds in sequence. If everything goes OK, you will get two success email notifications. (It will take at least 30 minutes.)
   • If builds fail, check logs, fix problems, re-tag the repo if necessary, and build again.
   • It is OK to trigger multiple builds concurrently (usually unnecessary).

Post-Build

1. Once you receive the second success email notification, copy the Kokoro-built repo into a permanent location.
   1. Email title: "[Kokoro] SUCCESS: google-cloud-eclipse/ubuntu/jar_signing"
   2. Take note of the "Artifact location" URL in the email. (You can also get the link through the Kokoro UI.)
   3. Run release/copy_repo_to_final_location.py.
      • This copies the repo to a permanent GCS location, which our official CT4E install URL will eventually point to: gs://cloud-tools-for-eclipse/<version>
2. Verify that you can install the plugin into Eclipse. Install URL: https://storage.googleapis.com/cloud-tools-for-eclipse/<version, e.g., 9.9.9>/.
   • Links that begin with https://storage.cloud.google.com/ do not work.
3. Create a Lorry entry.
   1. Search for "google-cloud-eclipse".
   2. Clone the approved version of the most recent stable link.
   3. Update the target in the cloned entry.
   4. Update the embargo date too. Generally, Mon-Thu between 10AM and 3PM.
4. Send 1) the direct URL of the update site; and 2) the URL of the newly created Lorry entry to the teammate who will follow the qualification process.
   • Assuming no serious bugs are uncovered during testing, this teammate should approve the Lorry entry.
5. Verify you can install the new release:
   • On Eclipse with the old version installed, do Help > Check for Updates.
   • On a clean instance of Eclipse, install from the official stable URL: https://dl.google.com/dl/eclipse/google-cloud-eclipse/stable/