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 "CBI/Distribution"

< CBI
Line 6: Line 6:
  
 
1 - Hudson executes the build (or local developer initiates manually)
 
1 - Hudson executes the build (or local developer initiates manually)
 +
 
2 - Code is cloned from git
 
2 - Code is cloned from git
 +
 
3 - Libraries are downloaded from either a) Orbit b) maven.eclipse.org c) downloads.eclipse.org
 
3 - Libraries are downloaded from either a) Orbit b) maven.eclipse.org c) downloads.eclipse.org
 +
 
4 - The build executes, outputs p2 repositories
 
4 - The build executes, outputs p2 repositories
 +
 
5 - Packaging takes place, outputs packages
 
5 - Packaging takes place, outputs packages
 +
 
CQ - 3rd party libraries are reviewed and approved/rejected. Approved libraries are stored in Orbit
 
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
 
ECO - Eclipse technology is consumed by the ecosystem at large

Revision as of 15:26, 15 February 2012

This page tracks information related to how code, configuration, build artifacts, bundles, packages, and more are distributed at Eclipse.

Overview

Distribution today.png

1 - Hudson executes the build (or local developer initiates manually)

2 - Code 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

Back to the top