Home » Archived » Buckminster » Continous Integration & Delivery of eclipse projects fo Beginners(I'm puzzled by the question of how to set up a reliable infrastructure for headless builds and continous delivery of eclipse projects.)
 Continous Integration & Delivery of eclipse projects fo Beginners [message #1007279] |
Tue, 05 February 2013 10:50  |
 Lukas Olbrich
Messages: 17
Registered: October 2010 |
Junior Member |
|
|
Hello everyone,
We're a startup, which is actually a spin-off from the university, and want to migrate the build infrastructure from the university's servers to our own servers.
Taking that step, I was thinking about reimplementing our build infrastructure.
Our current structure is:
- version control via git
- reviews via gerrit
- continuous integration via tycho in jenkins, automatically triggered via gerrit events
- continous delivery via a custom script which copies files via ftp to our p2 update site and manipulates the xml files, imho a dirty hack concerning composite.xml.
What I do not like about the described solution above is the redundancy concerning structure and dependencies: The eclipse structure -features,
plugins and so forth- has to be translated to the maven/tycho-structure -poms, modules and so forth- even though both carry equal information.
Also, the release process is tedious.
Well, now we were planning on using atlassian products because of the integration of jira/greenhopper with the gitrepo/review environment.
However, before we reimplement the infrastructure I wanted to ask you guys for recommendations: Can anyone tell me, how the official eclipse projects are continously integrated and delivered? Is it via buckminster? (sorry for being a rookie).
I'd really appreciate a brief overview on working infrastructures. Maybe, this information will add some pieces to my puzzle.
Cheers, Lukas
[Updated on: Tue, 05 February 2013 12:32] Report message to a moderator |
|
|
| Re: Continous Integration & Delivery of eclipse projects fo Beginners [message #1007995 is a reply to message #1007279] |
Fri, 08 February 2013 09:38  |
|
On 02/05/2013 11:50 AM, Lukas Olbrich wrote:
> Well, now we were planning on using atlassian products because of the
> integration fact of jira/greenhopper and with the dev environment.
> However, before we reimplement the infrastructure I wanted to ask you
> guys for recommendations: Can anyone tell me, how the official eclipse
> projects are continously integrated and delivered? Is it via
> buckminster? (sorry for being a rookie).
> I'd really appreciate a brief overview on working infrastructures.
> Maybe, this information will add some pieces to my puzzle.
As far as I know, Xtext, EMF and CDO rely on Buckminster (besides
Buckminster itself :) and Hudson (but I don't have any official eclipse
project myself).
With Buckminster you don't have redundancy concerning structure and
dependencies
I personally use it for some of my projects, namely
http://xsemantics.sourceforge.net/
http://code.google.com/a/eclipselabs.org/p/emf-components/
and we also rely on Gerrit and Jenkins for continuous integration
(these are not product based projects)
I also recently wrote some tutorials about Buckminster (and headless
builds): http://www.lorenzobettini.it/tag/buckminster/
hope this helps
Lorenzo
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
|
|
|
| Re: Continous Integration & Delivery of eclipse projects fo Beginners [message #1016364 is a reply to message #1007279] |
Wed, 06 March 2013 09:04 |
Christophe Bouhier
Messages: 937
Registered: July 2009 |
Senior Member |
|
|
Hi Lukas,
I recently started to setup a build-infra for the our products (with no
prior legacy system), What I found usefull, is to check out the releng
code for some of the technologies using Jenkins or Hudson and Bucky.
I.e. the cdo releng stuff, can be insightful.
check out from their git repo and have a look here:
http://wiki.eclipse.org/CDO/Release_Engineering
Cheers Christophe
On 05-02-13 11:50, Lukas Olbrich wrote:
> Hello everyone,
> We're a startup, which is actually a spin-off from the university, and
> want to migrate the build infrastructure from the university's servers
> to our own servers.
> Taking that step, I was thinking about reimplementing our build
> infrastructure.
> Our current structure is:
>
> version control via git
> reviews via gerrit
> continuous integration via tycho in jenkins, automatically triggered via
> gerrit events
> continous delivery via a custom script which copies files manually via
> ftp to our p2 update site, imho a dirty hack concerning composite.xml.
>
> What I do not like about the described solution above is the redundancy
> concerning structure and dependencies: The eclipse structure -features,
> plugins and so forth- has to be translated to the maven/tycho-structure
> -poms, modules and so forth- even though both carry equal information.
> Also, the release process is tedious.
>
> Well, now we were planning on using atlassian products because of the
> integration fact of jira/greenhopper and with the dev environment.
> However, before we reimplement the infrastructure I wanted to ask you
> guys for recommendations: Can anyone tell me, how the official eclipse
> projects are continously integrated and delivered? Is it via
> buckminster? (sorry for being a rookie).
> I'd really appreciate a brief overview on working infrastructures.
> Maybe, this information will add some pieces to my puzzle.
>
> Cheers, Lukas
|
|
|
Goto Forum:
Current Time: Thu Apr 18 22:48:31 GMT 2024
Powered by FUDForum. Page generated in 0.01544 seconds |
] 
Search
Help
Register
Login
Home
