[buckminster-dev] Re: mspec problems with released buckminster

[Carsten Reckord <creckord@xxxxxxxxxxxxx>]

Hi Johannes,

On 15.07.2009 19:07, Johannes Utzig wrote:
> I thought buckminster itself provider the means of building platform 
> agnostic
> target.os=${*} ...
> I must admit that it never quite worked for me but I think there's 
> something like that already implemented.
Slight misunderstanding here. What I'd like to do is not a platform-agnostic build, but several platform-specific ones, each with only those 
parts required for that exact platform.

> Thank you very much for the patch, that's what I thought needs to be 
> done. I'll have a look into it, do some tests with matrix builds on my 
> own and bump up a new version today or tomorrow if everything works fine.
I'm looking forward to it :)

> Please let me know when there are other things that you'd like to see in 
> the plugin.

Right now everything finally runs smoothly here, and I'm quite happy with the plugin :D

In the long term a buckminster job type akin to the maven one would be awesome, of course. I've read the thread above about better 
integration with the SCM side of hudson and that definitely sounds great. Aside from that, the only thing I can think of that's missing 
compared to the maven stuff is automatic dependency tracking between jobs, i.e. if build job A has a query with component org.example.a as 
root request and build job B has a query with a dependency to org.example.a, then B could be automatically triggered when A was built 
successfully. In fact, when I find the time in a week or two, I might mess around a bit with hudson build triggers and see if I can come up 
with something like that...


Best regards,
Carsten