Jump to: navigation, search

Difference between revisions of "Eclipse Build Available RSS Feeds"

(Add section on Callisto status; update Jar signing status)
(Additional Information)
Line 212: Line 212:
 
* For more on the Atom 1.0 spec, see [http://www.ietf.org/rfc/rfc4287.txt http://www.ietf.org/rfc/rfc4287.txt].
 
* For more on the Atom 1.0 spec, see [http://www.ietf.org/rfc/rfc4287.txt http://www.ietf.org/rfc/rfc4287.txt].
  
* For sample code (which will be revised shortly to implement this revised schema), see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116912#c21 https://bugs.eclipse.org/bugs/show_bug.cgi?id=116912#c21].
+
* For the latest code, see:
 +
 
 +
:* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116912#c21 https://bugs.eclipse.org/bugs/show_bug.cgi?id=116912#c21] (shell scripts to create/update feeds, watch for feed changes, and respond by launching a build).
 +
:* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116912#c21 https://bugs.eclipse.org/bugs/show_bug.cgi?id=116912#c24] (Ant tasks to create, update, query feed).

Revision as of 14:03, 27 April 2006

Eclipse Build Available RSS Feeds

Sample Hypothetical Feeds

  • Below are a few sample feeds which will hopefully be implemented within the Eclipse 3.2M6 timeframe. As this spec evolves this document will too, including revised URLs where applicable.
  • Everything in the <summary/> field is optional. A schema that backs these examples will be available soon, along with an Ant task to generate these during a build (after tests have run).
  • The ant task (for the moment, until I think of something else) will take the following parameters:
    • feed URL to publish
    • user@dev.eclipse.org to use for scp'ing the file
    • overwrite existing feed (one build per feed) or insert new content (many builds per feed)

Sample Eclipse Platform Feed

<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Eclipse Builds</title>
  <link rel="self" type="application/atom+xml" href="http://www.eclipse.org/news/builds.xml"/>
  <updated>2005-10-27T21:49:50Z</updated>
  <author>
    <name>Eclipse Build Team</name>
  </author>
  <id>http://www.eclipse.org/news/builds.xml</id>
  <entry>
    <title>[announce] Eclipse 3.2.0 M6 is available</title>
    <link href="http://download.eclipse.org/eclipse/downloads/drops/S-3.2M5a-200602231656/"/>
    <id>http://download.eclipse.org/eclipse/downloads/drops/S-3.2M5a-200602231656/</id>
    <updated>2006-05-28T20:50:00Z</updated>
    <summary>
      <tests type="junit" href="http://download.eclipse.org/eclipse/downloads/drops/S-3.2M5a-200602231656/testResults.php"/>
      <tests type="performance" href="http://download.eclipse.org/eclipse/downloads/drops/S-3.2M5a-200602231656/performance/performance.php"/>
      <downloads>http://download.eclipse.org/eclipse/downloads/drops/S-3.2M5a-200602231656/</downloads>
      <update>http://download.eclipse.org/callisto/releases/</update>
    </summary>
  </entry>
</feed>

Sample EMF Feed

<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>EMF Builds</title>
  <link rel="self" type="application/atom+xml" href="http://www.eclipse.org/emf/news/builds.xml"/>
  <updated>2005-10-27T21:49:50Z</updated>
  <author>
    <name>EMF Build Team</name>
  </author>
  <id>http://www.eclipse.org/emf/news/builds.xml</id>
  <entry>
    <title>[announce] EMF 2.2.0 M6 is available</title>
    <link href="http://download.eclipse.org/tools/uml2/scripts/downloads-viewer.php?s=2.0.0/R200509282050"/>
    <id>2.0.0/R200509282050</id>
    <updated>2005-09-28T20:50:00Z</updated>
    <summary>
      <tests type="junit">
        <results os="ALL" ws="ALL">PASS</testresults>
      </tests>
      <releasenotes>http://www.eclipse.org/uml2/news/release-notes.php?version=2.0.0</releasenotes>
      <downloads>http://download.eclipse.org/tools/uml2/scripts/downloads.php</downloads>
      <update>http://download.eclipse.org/tools/uml2/updates/</update>
      <depends>http://download.eclipse.org/downloads/drops/S-3.2M2-200509231000/eclipse-SDK-3.2M2-linux-gtk.tar.gz</depends>
    </summary>
  </entry>
</feed>

Sample UML2 Feed

<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>UML2 Builds</title>
  <link rel="self" type="application/atom+xml" href="http://www.eclipse.org/uml2/"/>
  <updated>2005-10-27T21:49:50Z</updated>
  <author>
    <name>UML2 Build Team</name>
  </author>
  <id>http://www.eclipse.org/uml2/news/builds.xml</id>
  <entry>
    <title>[announce] UML2 2.0.0 is available</title>
    <link href="http://download.eclipse.org/tools/uml2/scripts/downloads-viewer.php?s=2.0.0/R200509282050"/>
    <id>http://download.eclipse.org/tools/uml2/scripts/downloads-viewer.php?s=2.0.0/R200509282050</id>
    <updated>2005-09-28T20:50:00Z</updated>
    <summary>
      <tests type="junit">
        <results os="ALL" ws="ALL">PASS</testresults>
      </tests>
      <releasenotes>http://www.eclipse.org/uml2/news/release-notes.php?version=2.0.0</releasenotes>
      <downloads>http://download.eclipse.org/tools/uml2/scripts/downloads.php</downloads>
      <update>http://download.eclipse.org/tools/uml2/updates/</update>
      <depends>http://download.eclipse.org/downloads/drops/S-3.2M2-200509231000/eclipse-SDK-3.2M2-linux-gtk.tar.gz</depends>
      <depends>http://download.eclipse.org/tools/emf/downloads/drops/2.2.0/I200510270200/emf-sdo-xsd-SDK-I200510270200.zip</depends>
    </summary>
  </entry>
</feed>

Sample WTP Feed

<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>WTP Builds</title>
  <link rel="self" type="application/atom+xml" href="http://www.eclipse.org/wtp/"/>
  <updated>2005-10-27T21:49:50Z</updated>
  <author>
    <name>WTP Build Team</name>
  </author>
  <id>http://www.eclipse.org/wtp/news/builds.xml</id>
  <entry>
    <title>[announce] WTP 4.0.0 is available</title>
    <link href="http://download.eclipse.org/webtools/downloads/4.0.0/R200509282050"/>
    <id>http://download.eclipse.org/webtools/downloads/4.0.0/R200509282050</id>
    <updated>2005-09-28T20:50:00Z</updated>
    <summary>
      <tests type="junit">
        <results os="Linux">PASS</testresults>
        <results os="Windows">PENDING</testresults>
        <results os="Mac">FAIL</testresults>
      </tests>
      <tests type="performance">
        <results os="Linux" ws="gtk">PENDING</testresults>
        <results os="Linux" ws="motif">PENDING</testresults>
        <results os="Windows">UNKNOWN</testresults>
        <results os="Mac">SKIPPED</testresults>
      </tests>
      <tests type="api">
        <results>PASS</results>
      </tests>
      <releasenotes>http://www.eclipse.org/wtp/news/release-notes.php?version=4.0.0</releasenotes>
      <downloads>http://download.eclipse.org/tools/wtp/scripts/downloads.php</downloads>
      <update>http://download.eclipse.org/tools/wtp/updates/</update>
      <depends>http://download.eclipse.org/downloads/drops/S-3.2M2-200509231000/eclipse-SDK-3.2M2-linux-gtk.tar.gz</depends>
      <depends>http://download.eclipse.org/tools/emf/downloads/drops/2.2.0/I200510270200/emf-sdo-xsd-SDK-I200510270200.zip</depends>
      <depends>http://download.eclipse.org/tools/uml2/downloads/drops/2.0.0/I200510270300/uml2-SDK-I200510270300.zip</depends>
    </summary>
  </entry>
</feed>

Support For Eclipse.org Jar Signing

So that we can identify which projects' builds are signed, I've implemented an additional node, <build/>, which can take an attribute for <tt style="color:DarkGreen">jars, thus:

<feed xmlns="http://www.w3.org/2005/Atom">
	...
    <summary>
      <build jars="UNSIGNED">http://download.eclipse.org/tools/emf/scripts/downloads-viewer.php?s=2.2.0/S200607081234</build>
	...
    </summary>
</feed>

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

  • UNSIGNED
  • SIGNREADY (prop'd to eclipse.org, ready for signing)
  • BUILDREADY (signed on eclipse.org, ready for bundling)
  • SIGNED (signed & bundled on download page)

Proposed Support For Callisto Status

So that we can identify which projects' have been posted to callisto, I'm thinking of adding another attribute to the <build/> node, thus:

<feed xmlns="http://www.w3.org/2005/Atom">
	...
    <summary>
      <build jars="UNSIGNED" callisto="COMPLETE">http://download.eclipse.org/tools/emf/scripts/downloads-viewer.php?s=2.2.0/S200607081234</build>
	...
    </summary>
</feed>

Status codes here could be:

Code Purpose/Description
BUILDCOMPLETE Have you finished your RC1 bits?
2006-05-02T20:50:00Z When do you expect to finish them?
TPTP If you're waiting for another project, which one(s)?
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

  • For the latest code, see: