Revision as of 16:19, 31 May 2006

Eclipse Build Available RSS Feeds

Recent changes to this document

Sample Feeds

• Samples feed files can be seen in CVS here: /cvsroot/eclipse/org.eclipse.releng.basebuilder/plugins/org.eclipse.build.tools/data/
• Most of the contents of the <build/> node are optional. The schema for these examples is located here. For tasks used to create/modify/view or respond to feeds, see #Latest_Code.

Support For Eclipse.org Jar Signing

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

<feed xmlns="http://www.w3.org/2005/Atom">
  ...
  <summary>
    <build 
      xmlns="http://www.eclipse.org/2006/BuildFeed" 
      callisto="COMPLETE" 
      href="http://download.eclipse.org/downloads/drops/S-3.2RC5-200605191206" 
      jars="UNSIGNED" 
      type="S">
    ...
  </summary>
</feed>

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 eclipse.org, ready for signing
• BUILDREADY - signed on eclipse.org, 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

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

<build 
  xmlns="http://www.eclipse.org/2006/BuildFeed" 
  callisto="COMPLETE" 
  href="http://download.eclipse.org/downloads/drops/S-3.2RC5-200605191206" 
  jars="UNSIGNED"
  type="S">

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

• MC : Maintenance-Callisto
• SC : Stable-Callisto
• RC : Release-Callisto

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

 public void setBuildType(String buildType) 
 {
   if (!isNullString(buildType)) 
   {
     this.buildType = buildType;
   }
   else
   {
     this.buildType = buildID.replaceAll("[^NIMSR]", NS); //$NON-NLS-1$
     if (this.buildType.length()>1) 
     {
       this.buildType=this.buildType.substring(0, 1);
     }
   }
 }

Support For Callisto Status

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

<build 
  xmlns="http://www.eclipse.org/2006/BuildFeed" 
  callisto="COMPLETE" 
  href="http://download.eclipse.org/downloads/drops/S-3.2RC5-200605191206" 
  jars="UNSIGNED"
  type="S">

Status codes here could be:

Latest Code

The latest code can be found in CVS, currently in the releng_test branch:

• /cvsroot/eclipse/org.eclipse.releng.basebuilder/plugins/org.eclipse.build.tools

The latest XML Schema is here:

• Eclipse_Build_Available_RSS_Schema

Additionally, zips are available here (but are NOT as recent as what's in CVS):

• Shell & Ant tasks to create, update, query & publish feeds (CVS, SCP)
• Shell & Ant tasks to respond to feed changes (eg., sending an email, firing another ant task, launching a shell process with <exec>)

• https://bugs.eclipse.org/bugs/show_bug.cgi?id=116912#c35

• Ant task (and shell wrapper) to validate a feed against the latest schema

• https://bugs.eclipse.org/bugs/show_bug.cgi?id=116912#c36

Additional Information

• For more on the Atom 1.0 spec, see http://www.ietf.org/rfc/rfc4287.txt.