Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Re: Europa Build Workshop Report - RSS Feeds

Thanks Nick, That link,
along with the description in this mailing list append gave me the level of getting started I needed.

It might be nice to add a section in that wiki document on what problem(s) are being solved,
or, what the "driving forces" are, but don't think there's a need for any other document.

So otherwise, hope you enoy(ed) your vacation! :)
Maybe by the time you get back, I'll be able to work through some of the examples you provide,
and give better feedback.

Nick Boldt <codeslave@xxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

10/02/2006 02:23 AM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Re: [cross-project-issues-dev] Re: Europa Build Workshop Report        -        RSS        Feeds

Thanks, David.

I guess I should have included a link to this page:

As to the best path to getting started, I'd suggest extracting the code
from CVS and having a look at the examples provided:

  cvs -d :pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/eclipse -q checkout
  -r releng_test -d

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

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 (
* 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.

As to build types - the notion of build type has been there since the
get-go, but the restriction in the schema forcing <build type=""/> to
adhere to a mere 5 possible values (N, I, M, S, R) is new. In the past I
also had extra types for identifying callisto builds from non-callisto
builds, but I've changed the way that's done and expanded it to include
both status and "extra info":

That said... thanks for the feedback. I guess I need to beef up the
documentation around this, or at least make it easier to find. If you think
it'd be useful, I'll draft something akin to the link you provided below
when I'm back from vacation (Oct 10).


Nick Boldt :: Software Developer, IBM Toronto Lab
Eclipse Modeling Framework ::
905/413/4308 (t/l 969) :: codeslave@xxxxxxxxxx

            David M Williams                                              
  >                                                 To
            Sent by:                  Cross project issues                
            cross-project-iss         <cross-project-issues-dev@eclipse.o
            ues-dev-bounces@e         rg>                                
            10/01/2006 11:44          Re: [cross-project-issues-dev] Re:  
            PM                        Europa Build Workshop Report -      
                                      RSS  Feeds                          
            Please respond to                                            
              Cross project                                              

> New code and schema for RSS publishing and watching are in CVS. Please
> review it, and per the dates set forth at the Europa Build Workshop,
> provide any comments or feedback before Oct 13, after which point the
> schema will be considered "mostly" frozen.
> php/Europa_Build_Workshop_Report#RSS_Action_Items

> Thanks!

Thanks Nick ... but, wwhhaaaaatt?  :)
I spent 30 or so minutes clicking around going from wiki document to cvs
raw repository listing to bugzilla,
and ... you know how slow I am ... I could not really find what I was
looking for, and could not get a sense of
what the "big picture" was.

One thing I was looking for was one of those evolving design documents,
similar to,
my favorite example,

Its always helpful to have a central document that describes the problem
that's attempting to be solved, the
proposed solution, how the solution evolves, and, even, holes in the
solution, or cases not handled,
and finally the detailed "how to" acheive the solution (for both providers
to achieve, and
clients to achieve).

Another thing I couldn't find was a description of the "types" of builds.
... I'm pretty sure I saw
somewhere that "Nightly", "Integration", "Milestone", etc., were recently
added to some schema, but could
not find that in my 30 minute search.

The reason I was looking for the definitions of "types" was that I suspect
the whole notion "continuous" vs.
"declared" is not included, (and, I think it'd have to be, for our WTP
builds, at least, to convey their proper meaning).

So, apologies if I just missed it in my 30 minute search, but ... I'm
hoping even that too is useful feedback for you?
cross-project-issues-dev mailing list

cross-project-issues-dev mailing list

Back to the top