Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Platform-releng/Galileo"

m
m
Line 10: Line 10:
 
== Everyone can build ==
 
== Everyone can build ==
 
* provide an releng product download that people can download and replicate our build environment. The source build doesn't represent how Eclipse is built.  
 
* provide an releng product download that people can download and replicate our build environment. The source build doesn't represent how Eclipse is built.  
 +
* invoke builds from web ui authenticated by eclipse committer rights with parameters - maintenance build vs i-builds, tests or not etc.
  
  
 
== Further leverage p2 and enhancements to PDE build ==
 
== Further leverage p2 and enhancements to PDE build ==
 
* See [http://wiki.eclipse.org/PDE/Build/Galileo PDE Build Galileo plan] - for example, parallel compilation, fetch using p2, p2 as the packager etc.
 
* See [http://wiki.eclipse.org/PDE/Build/Galileo PDE Build Galileo plan] - for example, parallel compilation, fetch using p2, p2 as the packager etc.
 
  
  
Line 20: Line 20:
 
* incremental build from p2 repository
 
* incremental build from p2 repository
 
* compile at foundation, package locally, depends on availability of the eight vms we use
 
* compile at foundation, package locally, depends on availability of the eight vms we use
* invoke test builds from web ui authenticated by eclipse committer rights
 
 
* Evaluate if platforms, or zips can be removed from the build, with scripts to build with p2
 
* Evaluate if platforms, or zips can be removed from the build, with scripts to build with p2
 +
* Stability - evaluate common failures in build and determine how they can be improved.

Revision as of 15:07, 12 September 2008

Platform Release Engineering Galileo Plan

This document is a work in progress of the major changes that we would like to make during the Galileo release cycle.

Built for speed, faster tests we need

  • Run build with 1.6 vm Bug 237354
  • Run tests in parallel on several machines to reduce testing time


Everyone can build

  • provide an releng product download that people can download and replicate our build environment. The source build doesn't represent how Eclipse is built.
  • invoke builds from web ui authenticated by eclipse committer rights with parameters - maintenance build vs i-builds, tests or not etc.


Further leverage p2 and enhancements to PDE build


Blue sky ideas

  • incremental build from p2 repository
  • compile at foundation, package locally, depends on availability of the eight vms we use
  • Evaluate if platforms, or zips can be removed from the build, with scripts to build with p2
  • Stability - evaluate common failures in build and determine how they can be improved.

Copyright © Eclipse Foundation, Inc. All Rights Reserved.