Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

Automated Solution-Level Builds


Higgins logo 76Wx100H.jpg

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


  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 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)




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.

Back to the top