Europa/Build

From Eclipsepedia

< Europa
Revision as of 22:59, 4 February 2007 by Bjorn.freeman-benson.eclipse.org (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This page is related to the Europa Simultaneous Release.

These are some brief notes to document how the callisto projects "contribute" to the "Europa Build".

Of course, there really is no "build" of Europa, but only a copying of what is already available on each project's update site, to a central site. Plus, there is a "site.xml" file, and index.html, etc., that are authored, and Europa projects are (relatively) free to make updates to them.

The purpose of the build is simply to document the steps in the process, require as little manual intervention as necessary, and have the build be reproducible, version controlled, etc.

Contributors to the Europa Discovery site need to be aware the CVS Callisto projects.

:extssh:<your-committer-id-goes-here>@dev.eclipse.org:/cvsroot/callisto

Or, general "read" access via

:pserver:anonymous@dev.eclipse.org:/cvsroot/callisto

There are two projects there:

org.eclipse.europa.tools
org.eclipse.europa.updatesite

The org.eclipse.europa.tools project has a build-home sub-directory, with several ant files, of the form features-{project}.xml, where {project} is ep, wtp, birt, emf, cdt, dtp, gef, gmf, tptp, ve, etc.

Each Europa project's PMC and/or Project Leader is responsible to keep those feature-{project}.xml files up to date as the project releases new milestones and release candidates. The project's project leader will probably delegate to the project's release engineer(s).

Obviously, each project's own update site must already exist (and be working) at the URL that is specified in the feature-{project}.xml.

Typically, as projects move from milestone to milestone (or release candidate to release candidate) only the version identifiers in their feature-{project}.xml file have to be changed. There might, for some projects, be times when the feature ids themselves have to change or perhaps the URL will change as to where to find the project's update site.

On a regular schedule, or on request by a project that has just updated their feature-{project}.xml file, Bjorn does the following:

  1. an ant task will be ran to use update manager's "mirror" function to "pull" features from a project's site, and copy them to the callisto/staging site.
  2. The callisto site.xml file will be updated with the new feature versions, and copied to /callisto/staging site.
  3. Once the staging site has been tested by the projects, to indeed discover and install the right versions, on the right platforms, etc., there will be a "mass delete and mass copy" of the /callisto/staging site to the /callisto/release site.
  4. This "release" will be coordinated with the webmaster, so that the mirrors have time to replicate /callisto/relases (note: /callisto/staging is not mirrored, since it is for testing only, and may be created and re-created frequently, which would cause unnecessary noise on the mirror network).