Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [europa-build-workshop] Re: [cross-project-issues-dev] RSS Feeds And The Projects What Use 'Em 
Bjorn:

Sounds perfectly logical to check all the components, but I wonder if
it's necessary if the +2 and +3 components all depend on the +1 and +2
components. For example, TPTP depends on Platform, EMF and UML2; UML2
depends on Platform and EMF, and of course EMF depends on Platform. In
this scenario, you COULD cause a respin when Platform changes, but
you'd have to respin when EMF drops its update, when UML2 drops its
update (potentially twice if UML2 respins for BOTH Platform and EMF
updates), and finally respin again for the updated TPTP drop.

That might be the behaviour you want, but it might also be overkill.
If you ONLY watch TPTP, you'll get the composite result of a new
Platform+EMF+UML2+TPTP in one go, instead of as many as 7 updates
(Platform x 1, EMF x 1, UML2 x 2, TPTP x 3).

Beyond the design aspects of this, I'm interested in how easy it will
be for you to collect

  {
    check the RSS feed
    if there is a new build then $something_changed = true
  }

Additionally, do you plan to implement a type of hierarchical
response? Is a change to TPTP, for example, more "important" than one
to EMF, since it includes updates to 4 projects instead of just 2? Or
are all projects considered equal in that 'any feed changed' == 'time
to respond' ?

Cheers,

Nick

On 11/13/06, Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx> wrote:


 I was planning to, but haven't yet implemented, so perhaps it's a bad idea, watch them all. Something like:

 $something_changed = false
 foreach( Europa project )
   check the RSS feed
   if there is a new build then $something_changed = true
 endfor
 if $something_changed then
   recreate the daily/nightly Europa test update site
   publish the Europa daily/nightly Europa test update site RSS feed
 endif

 Of course this test update site will often be broken because it will rebuild/"regather the jars" multiple times as the Europa projects rebuild in sequence but it will provide early feedback to the projects about how consumable-into-the-big-Europa build their builds are.

 Obviously the publicly consumable Europa update site will have to be manually triggered based on "go-no-go" from each project.

 Comments?

 Nick Boldt wrote:

Bjorn:

 Thanks for the response. Do you mean you'll be consuming from *all* of Europa? That's going to be a rather complex watch script. Perhaps you only need to watch a few of the projects within Europa, or would you be watching a feed set up for the Europa UM site, rather than the individual components projects/sites/feeds?

 If you encounter usability issues, let me know and we can work together to make the underlying ant tasks easier to use when watching multiple parallel and serial feeds.

 -N



>
> On 11/12/06, Bjorn Freeman-Benson < bjorn.freeman-benson@xxxxxxxxxxx> wrote:
>
>        1) I'd like a show of hands from everyone who's publishing and/or watching
> [ ] Publishing Feed(s)
> [ ] Watching Feed(s)
>
>       Not yet - still working on the Orbit build (with David), the Dash build, and the Europa unification/summary build-thingy. I intend to publish from Orbit and Dash, and consume from Europa.
>
>  - Bjorn
>
>
> >
> >
>

>
   ________________________________



_______________________________________________
europa-build-workshop mailing list
europa-build-workshop@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/europa-build-workshop


_______________________________________________
europa-build-workshop mailing list
europa-build-workshop@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/europa-build-workshop

Back to the top