Skip to main content
Jump to: navigation, search

Eclipse Build Available RSS Feeds

Revision as of 19:32, 12 March 2007 by (Talk | contribs) (Getting Started With RSS Feeds: clarify reference impl vs. live impl)

Eclipse Build Available RSS Feeds

Recent changes to this document

Getting Started With RSS Feeds

To get started using this code, I'd suggest extracting everything from CVS and having a look at the examples provided:

cvs -d -q checkout -r releng_test \
-d org.eclipse.releng.basebuilder/plugins/

For details on extracting the code using Eclipse, see Eclipse Build Available RSS Feeds Getting Started.

Make sure you get the releng_test branch, not HEAD, if you want the latest implementation.

In there, you'll find scripts_rss/ which includes ant script examples for:

  • publishing a feed (feedPublish.xml)
  • manipulating a feed, eg., updating a feed with a new entry, changing attributes on an existing entry, or just querying a feed for some value (feedManipulation.xml)
  • watching a feed and responding to changes (feedWatch.xml)

These all use feedTools.jar, with sources in src_rss/. The properties files used by these scripts are in properties/. You'll see three for feedPublish.*.properties (publishing 3 different feeds) and two for feedWatch.*.properties (two projects watching upstream feeds). You'll also find a README in there which provides more details.

You can also look at the sample data in the data/ folder, which provides three feeds (Eclipse, EMF, UML2).

The feed schema is in the schema/ folder. The Ecore model and genmodel created from the schema and used for the feed validator are in model/, and the feed validator code is best accessed from the feedValidator.xml script in scripts_rss/ and the feedValidator.jar in the root.

Note: The code cited above is the example/reference implementation. For an live working implementation, see the examples below.

Sample Feeds

Support For Jar Signing

So that we can identify which projects' builds are signed, the <build/> node can take an attribute for jars, thus:

<feed xmlns="">

I'm thinking of 5 status codes, assuming the current jar signing process continues as proposed:

  • NONE (or "") - no status available or not participating
  • UNSIGNED - no jar signage available or done yet
  • SIGNREADY - jars promoted to, ready for signing
  • BUILDREADY - signed on, ready to be collected and bundled as zips and copied to UM site
  • SIGNED - signed & bundled on download page and on UM site

Support For Build Type, Branch & ID

So that we can identify what type of build a given entry is, these values can be specified for a type attribute:

  • N : Nightly
  • I : Integration
  • M : Maintenance
  • S : Stable (Milestone or Release Candidate)
  • R : Release

If the property buildType is not specified, the ant task will attempt to guess the build type based on the buildID, by looking for, like this:

this.buildType = buildID.replaceAll("[^NIMSR]", NS); //$NON-NLS-1$
if (this.buildType.length()>1) 
  this.buildType=this.buildType.substring(0, 1);

In addition, there are attributes available for branch, cvsbranch and datetime. Branch is a 3-number branch id, like 3.0.0 or 2.2.1. CVS branch is a string like "HEAD" or "R3_2_maintenance", and is optional. Datetime is a 12-digit number defining YYYYMMDDhhmm, the date and time associated with the build.

Support For Coordinated Releases

So that we can identify which projects' have been posted to Callisto/Europa/Whatnot, there's an element in the <build/> node, thus:

  <coordinated status="COMPLETE">More information here</coordinated>

Status codes are limited to:

Code Purpose/Description
NONE (or "") not part of Callisto or unknown status
BUILDCOMPLETE Have you finished your RC1 bits?
UMSITEREADY Have you placed those bits in your update site?
CALLISTOSITEREADY Have you updated the features.xml file in the Callisto CVS directory?
COMPLETE Are you ready for RC1 to be declared?

Additional information, if applicable, can be placed in the text field of the node, which might include:

Note Purpose/Description
2006-05-02T20:50:00Z When do you expect to finish them?
TPTP If you're waiting for another project, which one(s)?

Where To Publish

In order to ensure that your feed data is as current as your promoted bits, it's recommended that you publish your feed to the same place you publish your zips/jars. For the MDT example, this is*.xml, and the CVS archived versions of the files are in /cvsroot/org.eclipse/www/modeling/mdt/feeds/.

It is recommended that you publish one feed per component that people might want to watch uniquely. For MDT, this means 5 feeds (at time of writing).

Actual Feeds

These are actual feeds, currently being published. If you publish a feed that's not listed here, please add it.

A sample layout for linking to your feed from your downloads page is here: UML2 Downloads.

A sample icon to use is here: Atom 1.0 icon.

Working Examples

These are working examples implemented and in use, based on the samples provided in

In this scenario, EMF publishes a scheduled build every Thursday at 00:00, promotes the build to at 01:00, and then UML2, knowing there's an EMF build every week, starts watching the EMF feed, checking hourly at 02:00, 03:00 and 04:00, in order to pick up the latest driver to do its weekly build. As our build server is at IBM, this delay is necessary to ensure that code committed to has time to propagate across the nodes and to the IBM mirrors. Usually the mirrors replicate between 02:00 and 03:00, causing the UML2 build to start at 03:00.

This is only one use case. For more responsive feed watching, cron-based checks could be done 24h a day, multiple times an hour, and more than once a week.

The most recent version of the scripts documented here is in /cvsroot/modeling/releng-common/tools/scripts/.

MDT & EMFT Components

Currently, MDT & EMFT components only publish RSS, they do not listen to upstream RSS feed(s). Setup is fairly straightforward.

1. (see line 349), is passed the property RSS=1 (or executed using the -rssonly flag).

2. The promote script calls out to feedPublish.xml using


Publishing an EMF build automatically is done in two steps, both fired by crontab:

# M build every Thu (4); runs as web user, www-data
0 0 * * 4 sudo -u www-data /home/www-data/emf-build/scripts/ -proj emf -buildType M \
 -tagBuild true -branchCVS HEAD -noperf -runJDK14Tests -runJDK50Tests -runOldTests > \
 $HOME/cron_logs/ 2>&1
# promote M build + update feed (among other things)
0 1 * * 4 /home/www-data/emf-build/scripts/ -proj emf -branch 2.2.1 -type M \
  -user nickb -userIES nboldt -announce > $HOME/cron_logs/ 2>&1

One of the steps in promoting a build is to check out the latest copy of the feed from CVS, update it, commit it back to CVS, and scp it to This is done by having fire feedPublish.xml:


In this scenario, UML2 listens from 02:00 to 04:00 by running, but has chosen to manually verify and promote builds (also using

# respond to emf feed change; runs as web user, www-data
0 2,3,4 * * 4   cd /home/www-data/emf-build/scripts/ && sudo -u www-data \
 /home/www-data/emf-build/scripts/ -proj uml2 -branchCVS R2_0_maintenance > \
 $HOME/cron_logs/ 2>&1

If a change is seen in the feed, run the respondToFeedChanged target in feedWatch.xml, which has been customized to update dependencies then run a build:

<target name="spawnBuild">
  <echo message="Spawn new build:"/>
  <echo message="/home/www-data/emf-build/scripts/ -proj uml2 ${buildType} ${buildAlias} -branchCVS ${branchCVS} ${runOptions} -URL '${feedWatchAction.TheValue.2}/${feedWatchAction.TheValue.1}' -URL '${feedWatchAction.TheValue.3}'"/>
  <exec spawn="true" executable="bash" resolveexecutable="true">
    <arg line="/home/www-data/emf-build/scripts/ -proj uml2 ${buildType} ${buildAlias} -branchCVS ${branchCVS} ${runOptions} -URL '${feedWatchAction.TheValue.2}/${feedWatchAction.TheValue.1}' -URL '${feedWatchAction.TheValue.3}'"/>

Latest Code

The latest code - shell and ant scripts, ant task code, XML Schema for the feed, and sample data - can be found in CVS, currently in the releng_test branch. This includes:

Discussion / Bugzilla

Additional Information

Back to the top