[news.eclipse.tools.buckminster] Re: Buckminster updating / change-list

[eclipse@xxxxxxxxxxx (Peter M. Murray)]

Hi Henrik,

Hudson has a concept of an SCM module which is responsible for:

* checking out the project's specified source
* polling and reporting (yes or no) if the sources required have changed 
since the checkout (or last update)
* updating the sources and (optionally)reporting a log of changes, 
comments, users, etc if available

Buckminster as it stands is great for the first responsibility, but 
doesn't have any functionality for the latter two.

It seems to me that most of the Buckminster readers (CVS, SVN, p2 sites, 
urls) can provide these additional functionalities if desired (at least 
the updating and polling, in some cases without change-log)

We could then extend the current Buckminster/Hudson integration to include 
an SCM module for seamless CI integration.  You'd just specify the 
Buckminster for the SCM, type in the cquery URL, then specify a 
Buckminster build-step to perform whatever build operation you desire.

Right now, I have Hudson check out my Subversion sources (which 
unfortunately requires that they share a common root folder and then use a 
"local" Buckminster source to wire-up my sources for building.  This means 
I have to manually sync my Hudson configuration with the dependencies in 
my plugin projects.  

Only Buckminster has enough context to perform these operations without 
hard-wiring dependencies etc.

Does that explain the use-case?

Cheers,

pete