Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster dev » Continuous integration as a first-class feature in Eclipse 4.0
Continuous integration as a first-class feature in Eclipse 4.0 [message #15201] Thu, 10 April 2008 20:05 Go to next message
Neale Upstone is currently offline Neale UpstoneFriend
Messages: 50
Registered: July 2009
Member
Hi,

I've not got myself onto the learning curve for Buckminster yet, I've
restricted myself to some coffee and lunch sessions looking at some of
the demos you've done.

I was looking at Bucky because I've (finally) moved our project onto a
more professional footing, doing some continuous integration (using
Luntbuild, and Eclipse-exported Ant files).

Seeing that we've got the thinking around E4 going on, then I think
there's a big area where Eclipse/JDT is awkward, and that is: continuous
integration.

Perhaps CI would be a good target for e4 (or should I say e4.01, as e4
was released on 1st April ;), and it seems that Buckminster is a key
part of the system (in that you have UI tools, plus headless build
capability).

Is this part of your vision for Buckminster?

I'd much rather be doing something along those lines, than submitting a
trail of patches to Export->Ant buildfile, which is currently the case.


As some background, I picked the Ant export route as I had plain old
java projects, but now I've OSGied (thus now have a PDE export bug to
resolve :)

Looking around, it certainly appears that some fast track to CI is
needed, given that there are a mix of implementations across different
Eclipse projects.

Cheers,

Neale
Re: Continuous integration as a first-class feature in Eclipse 4.0 [message #15270 is a reply to message #15201] Fri, 11 April 2008 06:35 Go to previous message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3229
Registered: July 2009
Senior Member
Hi Neale,
We are certainly thinking about CI and any help and/or ideas of how to best integrate Buckminster
with tools like CruiseControl, Hudson, Continuum, Luntbuild, etc. would be greatly appreciated. This
is an area where we could really use some help.

E4 is on our radar but we have no concrete plans yet.

Kind Regards,
Thomas Hallgren


Neale wrote:
> Hi,
>
> I've not got myself onto the learning curve for Buckminster yet, I've
> restricted myself to some coffee and lunch sessions looking at some of
> the demos you've done.
>
> I was looking at Bucky because I've (finally) moved our project onto a
> more professional footing, doing some continuous integration (using
> Luntbuild, and Eclipse-exported Ant files).
>
> Seeing that we've got the thinking around E4 going on, then I think
> there's a big area where Eclipse/JDT is awkward, and that is: continuous
> integration.
>
> Perhaps CI would be a good target for e4 (or should I say e4.01, as e4
> was released on 1st April ;), and it seems that Buckminster is a key
> part of the system (in that you have UI tools, plus headless build
> capability).
>
> Is this part of your vision for Buckminster?
>
> I'd much rather be doing something along those lines, than submitting a
> trail of patches to Export->Ant buildfile, which is currently the case.
>
>
> As some background, I picked the Ant export route as I had plain old
> java projects, but now I've OSGied (thus now have a PDE export bug to
> resolve :)
>
> Looking around, it certainly appears that some fast track to CI is
> needed, given that there are a mix of implementations across different
> Eclipse projects.
>
> Cheers,
>
> Neale
Previous Topic:Re: [buckminster-dev] CVS authentication issue...
Next Topic:[buckminster-dev] question about generators and/or 'just in time' building of dependencies
Goto Forum:
  


Current Time: Thu Nov 27 13:39:12 GMT 2014

Powered by FUDForum. Page generated in 0.04011 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software