[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cross-project-issues-dev] Build Documentation
- From: Miles Parker <milesparker@xxxxxxxxx>
- Date: Tue, 5 Apr 2011 20:25:15 -0700
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=F0J+C2hk0RoUU79ib9ElHN99SbrlaRLfoJKfAb2J23pxxXZgg8XYVUt0YI4r9G4IG6 r/tCUYkRRSC50djvimHQDH71G3DhaWT2xCrUemV9sqjygS5YHAAc+tornPdDkPi81hV5 9a5MdZetksSUdmzTo1u+Kr1nrVjlH3LYpmaW4=
FWLIMOBW Athena was a really noble effort, even though in the end you had to maintain many of the same PDE artifacts so it probably wasn't a good long-term approach. Long term maintainability and external tools support was the reason that I ended up having to replace it with the Buckminster approach, otherwise I'd still be using it. But the Athena approach and intention of a common build infrastructure was right on. It might even be that there are still bits of the promotion infrastructure, PDE / ant bits etc.. that could be useful in a "CBI2".
On Apr 5, 2011, at 8:02 PM, Wayne Beaton wrote:
> FWIW, AFAIK Athena is no longer being actively developed. While it is
> being used (and should reasonable continue to be used) by some projects
> today, I recommend against adopting it for new builds.
> I've created a general landing page for bulids to the wiki . All:
> your comments/additions are appreciated.
>  http://wiki.eclipse.org/Development_Resources/Builds
> On 04/05/2011 06:05 PM, Miles Parker wrote:
>> I should have mentioned that AMP is using Buckminster. I'm almost an anti-case because I've got so many weird dependency issues and I seem to find every difficult case imaginable. But I have worked hard to keep the overall build-time (hudson) configuration as simple as possible and whenever possible to put the logic into a single build system. https://hudson.eclipse.org/hudson/job/amp-nightly/configure
>> I can't speak to tycho, but the principal advantage of Buckminster is that it handles all aspect so of provisioning in an open-ended way but with sensible defaults. The set of artifacts is a bit overwhelming at first so the Buckminster guide is worth a good scan. But once you have a Buckminster build working the really cool thing is that you can use it to provision your development setup as well. So I can now simply grab the Classic Eclipse build, import my project releng directory, open up a cquery file, click Resolve.. and all of my plugins are installed and all of the projects for my build are imported into the workspace.
>> On Apr 5, 2011, at 1:08 PM, Scott Lewis wrote:
>>> Hi Mark,
>>> On 4/5/2011 11:52 AM, Mark Russell wrote:
>>>> Thanks for the input. We wrote a custom build system based off of PDE but using Groovy to drive the build. I want to move to a more "standard" system as I move the code to Eclipse.
>>>> Which projects are using Buckminster?
>>> I don't know how many/which other projects are using Buckminster for their builds, but ECF is using it...in combination with the PDE, Athena and other scripts, Maven and Jenkins...and are quite happy with it. Fyi...here's the server:
>>>  https://build.ecf-project.org/jenkins/
>>> cross-project-issues-dev mailing list
>> cross-project-issues-dev mailing list
> cross-project-issues-dev mailing list