OCL/Dev/Releng/Cheatsheet

How to Releng MDT OCL

This is a very brief cheat sheet on how to publish builds for MDT OCL.

First, there are several types of builds:

N-builds: Nightly builds are internal-purpose builds which reflect the current state of the development stream. They do NOT use CVS tags in ocl.map and check out the current HEAD state. These builts are NOT signed and CANNOT be published.

I-builds: Integration builds usually reflect the intermediate state of the product. These are done between the milestones and rely on the CVS tags, i.e. their content may differ from the current CVS HEAD state.

S-builds: Stable (milestone and release) builds are actually I-builds which have a different naming than I-builds.

The releng process consists of two main phases - assembling (running) the build and publishing it on the downloads page and the update site (promotion).

How to Run an N-build

N-builds are run automatically triggered by CVS commits. However, they can be launched manually.

1. Navigate to https://build.eclipse.org/hudson/job/cbi-mdt-ocl-3.0/ 2. Log in using your CVS credentials 3. Click "Build Now". 4. On the next page, do not change the default build parameters and press "Build".

How to Run an I-build

Running an I-build is as simple as running an N-build. However, since I-builds use CVS tags in ocl.map rather than CVS HEAD state there is usually a preparation step. The goal of this step is to tag the new CVS changes which occurred after the last I-build and to update the tags in ocl.map.

Tagging the sources and updating the ocl.map

There are several ways to perform this part, e.g. manually using Eclipse Team integration. However, I prefer the automated approach based on the Releng Tools project. Both approaches are described in this section.

Tagging the sources and updating the ocl.map by hand

1. In the Navigator, select the plugin project(s) which were changed since the last I-build. 2. In the popup menu select Team->Tag as Version 3. In the Tag Resources dialog enter the new tag. Usually, the vYYYYMMDDHHmm form is used, e.g. v201004240200. Use Details->Refresh Tags buttons to explore the tags which have been already used. 4. Click OK

After you tag all the changed plugin projects you need to update your ocl.map file located in org.eclipse.mdt/org.eclipse.ocl/releng/maps/. In the ocl.map file update the lines corresponding to the plugins you have just tagged to the new tag value.

The map file is a Java properties file where the entries have the following format (for CVS): element@element_id=tag,:connection_type:user@host:repository

The SVN entry format is described here http://wiki.eclipse.org/Subversive_PDE_Fetch .

Tagging the sources and updating the ocl.map using Releng Tools

For your convenience you can check out the releng or the parent org.eclipse.ocl project.

You can launch an I build in the same manner as an N-build.

1. Navigate to https://build.eclipse.org/hudson/job/cbi-mdt-ocl-3.0/ 2. Log in using your CVS credentials 3. Click "Build Now". 4. On the next page, do not change the default build parameters and press "Build".