Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » Automating a build and release from command line
Automating a build and release from command line [message #375824] Thu, 01 May 2008 14:41 Go to next message
Tas Frangoullides is currently offline Tas FrangoullidesFriend
Messages: 195
Registered: July 2009
Senior Member
Hi,

I have a project which currently uses PDE build. I am considering
replacing this with buckminster but have questions regarding what
buckminster can do. Here is what the build currently does:

1. Obtain and extract target sdk and other dependecies such as emf
2. Get source code, depeneding or N, I or R build and using tags in map
files
3. Build SDK Feature
4 Get test source code, again depending on N, I or R build and using tags
in map files
5. Build tests
6. Deploy SDK and Tests to a new target environment
7. Execute tests and gether results
8. Publish to appropriate (N,I or R) update site.

How feasible is it to achieve similar results using buckminster? If you
can give me some pointer or suggest places to dig I'd be very grateful.

Thanks,
Tas
Re: Automating a build and release from command line [message #375827 is a reply to message #375824] Fri, 02 May 2008 07:17 Go to previous message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Tas Frangoullides wrote:
> Hi,
>
> I have a project which currently uses PDE build. I am considering
> replacing this with buckminster but have questions regarding what
> buckminster can do. Here is what the build currently does:
>
> 1. Obtain and extract target sdk and other dependecies such as emf

Buckminster can do one of two things.
1. It can automatically install features into a target platform, thus
building a target platform from a feature set. It requires you do create
a materialization spec (an MSPEC) that appoints a TargetPlatform
materializer.
2. Instead of installing into a target platform, Buckminster can import
plug-ins into your workspace.

> 2. Get source code, depeneding or N, I or R build and using tags in map
> files 3. Build SDK Feature

Buckminster has a special provider for PDE Map files. The maps chosen
could be controlled by a URL with parameter expansion, i.e.

http://your.company.org/some/path/{0}/maps

or similar. The property can be defined in a CQUERY or passed to the
resolver from the command line.


> 4 Get test source code, again depending on N, I or R build and using
> tags in map files

The PDE map file provider will recognize the tags that it finds in the map.

> 5. Build tests
> 6. Deploy SDK and Tests to a new target environment
> 7. Execute tests and gether results
> 8. Publish to appropriate (N,I or R) update site.
>
All of this can be done with Buckminster actions that call on ant.
Buckminster will know where everything is and pass this on to your ant
tasks.

> How feasible is it to achieve similar results using buckminster? If you
> can give me some pointer or suggest places to dig I'd be very grateful.
>
I think it is very feasible. Aside from our documentation I think you
should take a look at the build system of Buckminster itself. The source
is readilly available in our SVN
( http://dev.eclipse.org/svnroot/tools/org.eclipse.buckminster /trunk).
While it doesn't use all of the above, it does most of it. The main
component is the one named 'org.eclipse.buckminster'. It has a
buckminster.cspec that appoints several ant-tasks found in scripts under
the folder 'make'.

Kind Regards,
Thomas Hallgren
Previous Topic:How do I build an eclipse feature
Next Topic:Materializing multiple versions of a plugin
Goto Forum:
  


Current Time: Fri Mar 29 14:27:07 GMT 2024

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

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

Back to the top