Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Eclipse Build Available RSS Feeds"
m (→Latest Code) |
(→Sample Feeds) |
||
Line 3: | Line 3: | ||
[http://wiki.eclipse.org/index.php?title=Eclipse_Build_Available_RSS_Feeds&action=history Recent changes to this document] | [http://wiki.eclipse.org/index.php?title=Eclipse_Build_Available_RSS_Feeds&action=history Recent changes to this document] | ||
− | == Sample | + | == Sample Feeds == |
<ul> | <ul> | ||
− | <li> | + | <li>Samples feed files can be seen in CVS here: [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.releng.basebuilder/plugins/org.eclipse.build.tools/data/?only_with_tag=releng_test /cvsroot/eclipse/org.eclipse.releng.basebuilder/plugins/org.eclipse.build.tools/data/] |
− | <li> | + | <li>Most of the contents of the <tt style="color:DarkGreen"><build/></tt> node are optional. The schema for these examples is located [[Eclipse_Build_Available_RSS_Schema|here]]. For tasks used to create/modify/view or respond to feeds, see [[#Latest_Code]].</li> |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</ul> | </ul> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Support For Eclipse.org Jar Signing == | == Support For Eclipse.org Jar Signing == | ||
− | So that we can identify which projects' builds are signed, | + | So that we can identify which projects' builds are signed, the <tt style="color:DarkGreen"><build/></tt> node can take an attribute for <tt style="color:DarkGreen">jars</tt>, thus: |
− | + | <feed xmlns="http://www.w3.org/2005/Atom"> | |
− | <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" | |
− | </feed | + | '''jars="''UNSIGNED''"''' |
− | + | type="S"> | |
+ | ... | ||
+ | </summary> | ||
+ | </feed> | ||
I'm thinking of 5 status codes, assuming the current jar signing process continues as proposed: | I'm thinking of 5 status codes, assuming the current jar signing process continues as proposed: | ||
Line 183: | Line 38: | ||
== Support For Build Type == | == Support For Build Type == | ||
− | So that we can identify what type of build a given entry is, | + | So that we can identify what type of build a given entry is, these values can be specified for a <tt style="color:DarkGreen">type</tt> attribute: |
− | <build | + | <build |
− | http://download.eclipse.org/ | + | 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 | :*N : Nightly | ||
Line 219: | Line 77: | ||
== Support For Callisto Status == | == Support For Callisto Status == | ||
− | So that we can identify which projects' have been posted to | + | So that we can identify which projects' have been posted to Callisto, there's an attribute on the <tt style="color:DarkGreen"><build/></tt> 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: | Status codes here could be: |
Revision as of 16:19, 31 May 2006
Contents
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:
Code | Purpose/Description |
NONE (or "") | not part of Callisto or unknown status |
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? |
Latest Code
The latest code can be found in CVS, currently in the releng_test branch:
The latest XML Schema is here:
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>)
- Ant task (and shell wrapper) to validate a feed against the latest schema
Additional Information
- For more on the Atom 1.0 spec, see http://www.ietf.org/rfc/rfc4287.txt.