 Continous Integration & Delivery of eclipse projects fo Beginners [message #1007279] |
Tue, 05 February 2013 05: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 07:32] Report message to a moderator |
|
|
] 
Search
Help
Register
Login
Home
