Difference between revisions of "OCL/Dev/Releng/Tycho"

Revision as of 13:24, 21 February 2024

MDT OCL Releng Introduction

This is a very brief cheat sheet on how to make and publish builds for Eclipse OCL project.

First, there are several types of builds:

N-builds: Nightly builds are internal-purpose builds which reflect the current state of the development stream, that is, using the current GIT master HEAD.

I/M-builds: Integration/Interim builds.

S-builds: Stable/Milstone/Release-Candidate builds.

R-builds: Release builds.

The regular releng process consists of two cascaded builds.

https://ci.eclipse.org/ocl/job/ocl-master assembles and tests the build and if successful

https://ci.eclipse.org/ocl/job/promoter publishing it on the downloads page and the P2 repository (promotion).

How to Run a Build

N-builds are run automatically when a CVS change is detected (CVS is monitored every 6 hours). I, S, R, and M-builds must be manually launched.

1. Navigate to https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-core-3.1-nightly/
2. Log in using your CVS credentials
3. Click "Build Now".
4. On the next page, select the correspondent build type. In case you need to publish a milestone/release/maintenance build, you may want to use a proper build alias for the build. For instance, to create an M2 milestone for MDT/OCL Indigo, you have to select the S-build type and establish "3.1.0M2" as the build alias.
5. Finally, you must press "Build" to start the build.

How to Publish a Build

N-builds are usuallaly published in an automated way. A cron entry defined by the release engineer is responsible to execute the publishing script every night:

30 3 * * * ant -f /shared/jobs/buckminster-mdt-ocl-core-3.1-nightly/lastSuccessful/archive/publishroot/publisher.ant 
-Dbuild.root=/opt/public/jobs/buckminster-mdt-ocl-core-3.1-nightly/lastSuccessful/ 
&> logs/mdt-ocl-publishing.log

Specifically, this ant task publishes the last successful build so that if you wanted to publish a manually executed (and succesfully completed) build you would only require to execute that command in a shell on build.eclipse.org server. To access this server, you have to use a ssh client tool (i.e PUTTY) and do the following:

1. Ssh to build.eclipse.org at port 22.
2. Log in using your CVS credentials.
3. Execute the ant task above.

NB: If it's the first time you access Eclipse's servers, you need to be granted with shell access to log in.
In order to obtain said shell access, tell your project leader to do the request.
Example: https://bugs.eclipse.org/bugs/show_bug.cgi?id=310790.

NB: Mirror servers are synchronized automatically with build.eclipse.org. No manual action is required.

Updating Eclipse OCL in the Eclipse SimRel Release Train

After the publishing process is successfully finished the S/R/M-build has to be included into the Eclipse release train.

To do so, one needs to update the Eclipse OCL contribution to the SimRel project.

In a web browser, if not already set up and assuming xyzzy is your Eclipse committer id

1. create the https://github.com/xyzzy/simrel.build fork of eclipse-simrel/simrel.build:main.

In Eclipse, if not already set up:

1. Clone https://github.com/eclipse-simrel/simrel.build.git

In Eclipse:

1. Check out the main branch
2. Pull from origin
3. Create and checkout a Pull Request branch such as pr-ocl
4. Edit the /org.eclipse.simrel.build/ocl.aggrcon file (GIT history has numerous examples)
5. Commit the edit
6. Push the PR branch to xyzzy specifying pr-ocl

(NB OCL and QVTd are tightly coupled so often committed together).

Back in a web browser and provided you have simrel committer rights

1. Navigate to https://github.com/xyzzy/simrel.build
2. Accept the offered pr-ocl PR (Compare PR)
3. (Pull request)
4. wait while auto-build proceeds
5. (Squash and merge)
6. (Confirm)