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"
(→Requirements) |
(→Services Used) |
||
| Line 11: | Line 11: | ||
# 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. | ||
| − | ===Services | + | ===Services=== |
[[Image:Higgins-builds-1.1.100.png|center]] | [[Image:Higgins-builds-1.1.100.png|center]] | ||
Revision as of 14:58, 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.
Services
