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 22: Line 22:
  
 
Dashed arrows are strictly a manual process
 
Dashed arrows are strictly a manual process
 +
 +
==Areas of concern==
 +
 +
===Eclipse technology redistribution===
 +
 +
Orbit provides a centralized clearing house for IP policy approved 3rd party dependencies. At the moment, projects consuming technology from other Eclipse projects do so in a variety of ways.

Revision as of 16:20, 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 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

Areas of concern

Eclipse technology redistribution

Orbit provides a centralized clearing house for IP policy approved 3rd party dependencies. At the moment, projects consuming technology from other Eclipse projects do so in a variety of ways.

Back to the top