Skip to main content
Jump to: navigation, search

Difference between revisions of "Automated Solution-Level Builds"

m (Implementation)
 
(8 intermediate revisions by 3 users not shown)
Line 7: Line 7:
 
# The "top level" solution-level build scripts (one per solution) MUST run on a non-Eclipse server (because the builds must integrate many non-Higgins-redistributable libraries, tools and components). They will run on an azigo.com build server.  
 
# The "top level" solution-level build scripts (one per solution) MUST run on a non-Eclipse server (because the builds must integrate many non-Higgins-redistributable libraries, tools and components). They will run on an azigo.com build server.  
 
# These top level scripts SHOULD invoke whereever possible the nightly build scripts for whatever components can be built on the eclipse Higgins build server.
 
# These top level scripts SHOULD invoke whereever possible the nightly build scripts for whatever components can be built on the eclipse Higgins build server.
# No enhancements shall be made to the existing "home-made" Higgins build system. Any component that requires new features in our home-made build system MUST instead create and deploy a Buckminster build script.
+
# No enhancements shall be made to the existing "home-made" Higgins build system. Any component that requires new features in our home-made build system MUST instead create a script for the <TBD> Higgins build service.
# Only if it is impossible to create a Buckminster build script to build a particular component, then it is acceptable to instead use the build system on the Azigo build server (this tool has not yet been chosen). Why? because we MUST try to do whatever building can be done on the Higgins build server as is possible.
+
# Only if it is impossible for a particular component (or solution) to create a build script for the <TBD> Higgins build service is it ALLOWED instead use the build system on the Azigo build server (this tool has not yet been chosen).
 
# Top level scripts MUST pull the non-Higgins-redistributable JARs, libraries, and in some cases source code from a (new) local azigo SVN server.
 
# Top level scripts MUST pull the non-Higgins-redistributable JARs, libraries, and in some cases source code from a (new) local azigo SVN server.
 
# Azigo build service SHOULD pull binaries wherever possible from the Higgins download site. Only compile from source if no-such Higgins binary gets autobuilt.
 
# Azigo build service SHOULD pull binaries wherever possible from the Higgins download site. Only compile from source if no-such Higgins binary gets autobuilt.
 +
# [Valery] The solution should support builds for native solutions (Windows, Linux and OSX)
  
===Services===
+
=== Services ===
 
+
 
[[Image:Higgins-builds-1.1.100.png|center]]
 
[[Image:Higgins-builds-1.1.100.png|center]]
  
 
===Implementation===
 
===Implementation===
* We've not yet decided on the tool (Maven, CruiseControl, Buckminster, etc.) that we'll use on the Azigo build service
+
Hudson is used on the Higgins build service. The Azigo build service uses two nodes which work on Windows and Mac OS. It allows making of platform specific builds.
* The Higgins build service will continue to use the home-made build system until we can one by one cut over to using Buckminster
+

Latest revision as of 11:53, 13 October 2010

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

Higgins logo 76Wx100H.jpg

This page describes our plan for getting to solution-level automated (nightly) builds.

Requirements

  1. The "top level" solution-level build scripts (one per solution) MUST run on a non-Eclipse server (because the builds must integrate many non-Higgins-redistributable libraries, tools and components). They will run on an azigo.com build server.
  2. These top level scripts SHOULD invoke whereever possible the nightly build scripts for whatever components can be built on the eclipse Higgins build server.
  3. No enhancements shall be made to the existing "home-made" Higgins build system. Any component that requires new features in our home-made build system MUST instead create a script for the <TBD> Higgins build service.
  4. Only if it is impossible for a particular component (or solution) to create a build script for the <TBD> Higgins build service is it ALLOWED instead use the build system on the Azigo build server (this tool has not yet been chosen).
  5. Top level scripts MUST pull the non-Higgins-redistributable JARs, libraries, and in some cases source code from a (new) local azigo SVN server.
  6. Azigo build service SHOULD pull binaries wherever possible from the Higgins download site. Only compile from source if no-such Higgins binary gets autobuilt.
  7. [Valery] The solution should support builds for native solutions (Windows, Linux and OSX)

Services

Higgins-builds-1.1.100.png

Implementation

Hudson is used on the Higgins build service. The Azigo build service uses two nodes which work on Windows and Mac OS. It allows making of platform specific builds.

Copyright © Eclipse Foundation, Inc. All Rights Reserved.