Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Automated Solution-Level Builds"
(→Implementation) |
|||
Line 17: | Line 17: | ||
===Implementation=== | ===Implementation=== | ||
− | * We've not yet decided on the tool (Maven, CruiseControl, Buckminster, etc.) that we'll use on the Azigo build | + | * We've not yet decided on the tool (Maven, CruiseControl, Buckminster, etc.) that we'll use on the Azigo build service |
+ | * The Higgins build service will continue to use the home-made build system until we can one by one cut over to using Buckminster |
Revision as of 15:23, 15 July 2009
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
This page describes our plan for getting to solution-level automated (nightly) builds.
Requirements
- 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.
- 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.
- Only if it is impossible to create a Buckminster build script, then it is acceptable to 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.
- Azigo build service SHOULD pull binaries wherever possible from the Higgins download site. Only compile from source if no-such Higgins binary gets autobuilt.
Services
Implementation
- We've not yet decided on the tool (Maven, CruiseControl, Buckminster, etc.) that we'll use on the Azigo build service
- The Higgins build service will continue to use the home-made build system until we can one by one cut over to using Buckminster