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

CBI/Distribution

< CBI
Revision as of 17:15, 15 February 2012 by Andrew.ross.eclipse.org (Talk | contribs) (Areas of concern)

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. People picking up this technology are left to discover the chain of transitive dependencies.

This is an issue for Eclipse projects, and also for technology outside of Eclipse that uses Eclipse components.

Move to Long Term Support

The LTS program must ensure that all dependencies are available from an Eclipse Foundation controlled source.

Back to the top