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 "CBI/Distribution"
< CBI
| Line 19: | Line 19: | ||
ECO - Eclipse technology is consumed by the ecosystem at large | ECO - Eclipse technology is consumed by the ecosystem at large | ||
| − | Red arrows denote a path that would be useful, but may not exist today | + | Red arrows denote a path that would be useful, but may not exist today |
| + | |||
| + | Dashed arrows are strictly a manual process | ||
Revision as of 15:29, 15 February 2012
This page tracks information related to how code, configuration, build artifacts, bundles, packages, and more are distributed at Eclipse.
Overview
1 - Hudson executes the build (or local developer initiates manually)
2 - Code and config is cloned from git
3 - Libraries are downloaded from either a) Orbit b) maven.eclipse.org c) downloads.eclipse.org
4 - The build executes, outputs p2 repositories
5 - Packaging takes place, outputs packages
CQ - 3rd party libraries are reviewed and approved/rejected. Approved libraries are stored in Orbit
ECO - Eclipse technology is consumed by the ecosystem at large
Red arrows denote a path that would be useful, but may not exist today
Dashed arrows are strictly a manual process