Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search


This page is related to the Ganymede Simultaneous Release.


The Ganymatic is live and running every day. The status & logs are here:

In addition to sending emails to project release engineers who are responsible for broken builds, there are three 'Eclipse Build' format RSS feeds available for project teams to monitor. More info on feeds: Getting Started Guide, Feed Schema.

Of course, there really is no "build" of Ganymede, but only a copying of what is already available on each project's update site, to a central site.

This central update site, naturally, is To get a sneak peek, point your Update Manager at

Running a Build

The Ganymatic runs automatically when it detects changes in CVS that warrant a new build. However, if you're impatient or want to test your latest contribution, you can kick a build yourself using the Cruise Control interface:

  • Next, click the icon that looks like an arrow biting its tail. Onmouseover it says "Force build". Cruise-Control-force-build-icon.gif
  • Wait a minute or two, then go back to the main Ganymede dashboard, and wait for your build to complete.

The Projects' Roles

Pre-Project Configuration Files

The pre-project configuration files are stored in the Callisto CVS:


Or, general "read" access via

There is one project:


Syntax and Semantics

<?xml version='1.0'?>
    <sc:member name="Bjorn Freeman-Benson" email="" />
    <sc:member name="Karl Matthias" email="" />
    <sc:cspec name="org.eclipse.wtp-sc">
        <dependency name="org.eclipse.jpt.feature" 
                    versionDesignator="[1.0.0.v200706250000-77--CYQCCz-CoRPCCCH]" />
        <dependency name="org.eclipse.jst" 
                    versionDesignator="[2.0.0.v200706110805-7B-18dDQISlz0z0cc-oasolrW8jP]" />
        <dependency name="org.eclipse.wst.common_ui.feature" 
                    versionDesignator="[2.0.0.v200706041905-7C5EGzE9RvTVniSrwnf4TgOPe3e9]" />
        <public name="Web and JEE Development">
          <attribute component="org.eclipse.jst" />
          <attribute component="org.eclipse.wst.common_ui.feature" />
        <public name="Other Development">
          <attribute component="org.eclipse.jpt.feature" />
  1. ${downloads}/webtools/milestones/site.xml: The location of the project's update site. It's more efficient to access the site via a file path than a url, but a url will work. ${downloads} refers to the root of the server.
  2. Bjorn Freeman-Benson and person to notify if this project is responsible for breaking the build. Feel free to have multiple people listed.
  3. org.eclipse.wtp-sc: the unique identifier for this site contribution
  4. org.eclipse.jpt.feature: The feature identifier. One per feature (of course). Features are listed one per <dependency .../> node.
  5. 2.0.0.v200706041905-7C5EGzE9RvTVniSrwnf4TgOPe3e9: The feature version. One per feature (of course). Buckminster (the technology Ganymatic is built on) has a number of ways to specify the version. Most projects will use a single fixed version here, although you can also have an empty string to mean "the latest version found on my update site".
  6. Web and JEE Development: Categories for the Ganymede site.xml file; used to group the features.

Schemas for these files are available at: , , ,

A note on <sc:member semantics: please don't use an eclipse -dev mailing list, or any other email address that requires a subscription ... the builder will seldom be subscribed.

Project Responsibilities

Each Ganymede project's PMC and/or Project Leader is responsible to keep its own *.sc (site contribution) file up to date as the project generates 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 file location or url specified in the site contribution file.

Typically, as projects move from milestone to milestone (or release candidate to release candidate) only the version identifiers (e.g. 1.0.0.v200706250000-77--CYQCCz-CoRPCCCH]) in the site contribution file will need to be changed. At other times, features might be added, removed, or renamed:

  • Adding a feature: add new <dependency> and <attribute> nodes
  • Removing a feature: remove the corresponding <dependency> and <attribute> nodes
  • Renaming a feature: change the feature identifier (in two places) (e.g., org.eclipse.jpt.feature).

Each project should post updates on the Ganymede/Signoffs page after each of their Milestone and Release Candidates is released.

TBD: how to trigger a new build and how to sign off that the project M-bits are ready to use.

The Production Ganymatic

The Ganymede builds are triggered automatically when ever someone commits their site contributions to head. In some few cases, for example, if someone subsequently updates or fixes their own update site, but the sc files don't change, then you may have to "touch" your sc file and commit it, just to trigger a build, or, you can "manually" force a new build from the Orbit Cruise Control page.

Digests, P2 Metadata, Pack200 and Promotion

The digest and P2 meta data are created every "build", so they should always be accurate. But, the site is "packed" (with pack200) only once per day, overnight, since it takes about 2 hours.

The implication of this, is that before "promoting" a build, you need to make sure that the packing step has taken place on the latest files in staging. (There will be no pack200.gz files, if it has not ran, yet).

If it has not ran yet, and you want to promote, you can "manually" start the pack build from Cruisecontrol, and enjoy your favorite beverage while it cranks away.

Promoting a build from Staging area to Releases Area

There is a script, in, called '' which performs the usual steps of copying 'staging' bits to 'releases' area. It should be executed from the directory.

It removes all the previous 'releases' files (which is appropriate for milestones, and the final release, but will have to be improved for the maintenance releases). After removal, it copies all the files from /releases/ganymede/staging "up to" /releases/ganymede. It also uses a sed script to modify URLs in the site.xml file that contain /releases/ganymede/staging to be shortened to /releases/ganymede. Then, it recreates the the file, and the P2 metadata files. These partially have to be re-created because they contain some URLs inside (for the mirror script) which has to be modified from 'staging' to 'releases', but also since as a general principle, they should be recreated, so they are sure to reflect the contents of the 'new' site (even though, most of the time, the contents are identical to the 'old' site).

So, to summarize, the actual mechanics are pretty simple: on, perform something like the following, saving the output in case you need to inspect it for errors, etc.

 cd /shared/ganymede/workingdir/
 ./ | tee ~/recordOut.txt 

Note, it's not a bad idea to sanity check the files, dates, sizes, etc., in ~/downloads/releases/ganymede. They should be similar to the following:

-rw-rw-r-- 1 david_williams   98K 2008-06-02 13:21 artifacts.jar
-rw-rw-r-- 1 david_williams 1118K 2008-06-02 13:21 content.jar
-rw-rw-r-- 1 david_williams  129K 2008-06-02 13:08
-rw-rw-r-- 1 david_williams   40K 2008-06-02 13:21 site.xml

Plus, it's usually good to read the first of the site.xml file, and make sure the URLs there got changed correctly so they no longer contain 'staging'.

Also, if you're curious, there's a utility script, that will list some summary data, ... to double check things look relatively normal:

david_williams@build:~/downloads/releases/ganymede> ./

 number of features: 433 (11 are not packed)
 number of plugins: 1575 (63 are not packed)

Creating Ganymatic

For Your Own Local Build Machine

1. Build a copy of Ganymatic and transfer it to your build server (if not building locally).
2. Check out the org.eclipse.ganymede.sitecontributions and projects.
cvs -d -q co org.eclipse.ganymede.sitecontributions; \
cvs -d -q co
3. There are two files of variables and properties you need to customize for your machine, with these names:
It is recommended you create a directory called ganymedeConfig in your $HOME directory, and put your two customized files there, since several of the script files will look there automatically and use those files, if they exist.
See other examples in
Note, the reason for having your own customizations in a separate location (~/ganymedeConfig) is so that you can easily get a fresh copy of without "stepping on" your own customizations. Only the production build machine should depend on the property files located in the project.
4. Use ant to run the build.xml from Or, use this script:
cd; \
/shared/ganymede/apps/apache-ant-1.7.0/bin/ant \
5. The results (update site and website) are placed in the directories you specified in the file. Email notification (if any) is also configured in the properties file.

For Build.Eclipse.Org

To create the binaries (headless assembly scripts and runtime) for Ganymatic:

1. Start with an Eclipse 3.3 or 3.4 SDK with the latest version of Buckminster 1.0 installed. You need the two features org.eclipse.buckminster.core and org.eclipse.buckminster.pde. Please note that Buckminster has a lot of optional features. Don't install all of them (some are even mutually exclusive).
2. Check out the org.eclipse.dash.siteassembler project.
cvs -d -q co \
  -d org.eclipse.dash.siteassembler org.eclipse.dash/org.eclipse.dash.siteassembler
3. [This should already be the case, but just in case ... ] Make sure the siteassember project targets a 5.0 JVM. Right-click the checked-out project and select
Properties > Java Compiler > Compiler compliance level: 1.5
4. Right click on the org.eclipse.dash.siteassembler project and choose
Buckminster > Invoke Action... > buckminster.clean
5. Right click on the org.eclipse.dash.siteassembler project and choose
Buckminster > Invoke Action... > headless.assembler
  • This generates the org.eclipse.dash.siteassembler/bin/buckminster directory
  • If there are strange errors, delete the org.eclipse.dash.siteassembler/bin/ and try again from the buckminster.clean
6. Zip & transfer the bin/buckminster directory to Unpack it as
export you=yourUserName; \
cd /path/to/workspace/org.eclipse.dash.siteassembler/bin; \
zip -r /tmp/ buckminster; \
ssh $ "mkdir -p ~/ganymede/buckminster/bin/"; \
scp /tmp/ $; \
ssh $ "cd ~/ganymede/buckminster/bin/; unzip"; \
rm -f /tmp/
7 Unlike the process for your own local build machine, there should not be any user-defined customization used or required for running Ganymatic on This is by design, so that anyone can take over running the builds on and get the same, repeatable result by simply checking out the project and running it (that is, it should not depend on what user id is running the process, for production builds).
Additional tidbits
If interested in how it works, the '' is the main part of the buckminster code that does headless builds (composition) but it lacks the project specific information that is compiled into org.eclipse.dash.siteassembler jar, which is in the bin/buckminster directory, along with the rest of
Ever wonder why or when the bin/buckminster code should be regenerated? See Bug 227693 but the short answer is whenever there are bug fixes to Buckminster, or the org.eclipse.dash.siteassembler changes.

Additional Requirements and Information

See Europa Build for how last year's build worked.

Bugs & Feature Requests

See Also

Required Patches

Some of these patches may be required, depending on which versions of the Platform are being used, to have a perfectly reproducible build as the eclipse production machine. I just wanted a central place to document them, so I wouldn't lose the information.

  • bug 229019 contains a patch that allows jars with security exceptions to be identified. This patch was applied to the 3.3.2 version of update.core, exported from developer workspace (not built, per se) and used in place of the one that is used by default in the current Buckminster headless assembly application. The patch simply allows the jar with the error to be listed so it can be tracked down and fixed.
  • bug 226850 contains a patch that is required to get site optimizer to pack directories. Hopefully this will be in the final 3.4 platform, but if anyone is using a build prior to that, they would have to have this patch applied to get the jars packed.

Back to the top