Several weeks ago I blogged a lot about headless build and mainly about the problems I encountered to set up this build. I must admit that it was difficult and long to have the final build working properly but I also MUST admit than the benefits are now really appreciable.
These benefits are mainly :
- Each time we have to release our features I feel confident. First, I am confident about the content of the packages thanks to automation. Then I am also confident about the compiled code build in the packages thanks to the integration of our J-Unit tests in the build.
- The workload to perform the release thanks to the headless build can be summed-up by: ./manu-linux-build.sh build.all. In other words, it’s FREE. Who wants a release ?? You or you ? You ? No problem I can do that in one click !! You need an engineering release ? Ok here it is !!!
If your are not already building your Eclipse’s product automatically I strongly encourage you to get started with headless build.
Manu
April 29, 2009 at 2:40 pm |
Getting the Headless build going is the first step. Now to make it continuous:
http://intellectualcramps.blogspot.com/2009/04/eclipse-development-process-technical_29.html
April 29, 2009 at 9:21 pm |
By the way: Hudson works great for continuous builds. It’s easy to set up and there are lots of 3rd party extensions.
https://hudson.dev.java.net/
April 30, 2009 at 8:28 pm |
… have you tried Athena?
http://wiki.eclipse.org/Common_Build_Infrastructure/Getting_Started/Build_In_Eclipse
Works in Eclipse, commandline, in Hudson, etc.