Difference between revisions of "CBI/Projects"

Revision as of 10:56, 16 January 2014

Projects that are using CBI today

Eclipse (platform)

These are the repositories included:

• eclipse.platform.runtime
• maven-cbi-plugin
• eclipse.platform
• eclipse.platform.team
• eclipse.jdt.core
• eclipse.platform.ui
• eclipse.platform.ua
• eclipse.platform.releng.tychoeclipsebuilder
• eclipse.platform.common
• rt.equinox.bundles
• eclipse.pde
• rt.equinox.binaries
• eclipse.platform.text
• eclipse.platform.swt
• eclipse-parent
• eclipse.platform.releng
• eclipse.platform.swt.binaries
• eclipse.platform.resources
• scripts
• eclipse.platform.releng.eclipsebuilder
• eclipse.jdt
• rt.equinox.p2
• eclipse.platform.debug
• rt.equinox.framework
• eclipse.pde.build
• eclipse.pde.ui
• eclipse.jdt.debug
• eclipse.jdt.ui
• rt.equinox.incubator
• eclipse.platform.repository
• eclipse.jdt.core.binaries

Mylyn

CDT

EGit

JGit

Gyrex

More details can be found at Gyrex/Contributor_Guide/Builds

Hudson

Tycho

repositories:

• org.eclipse.tycho
• org.eclipse.tycho-demo
• org.eclipse.tycho.extras

m2e

repositories:

• m2e-core
• org.eclipse.m2e.wtp

e4

org.eclipse.e4.tools

GMF Tooling

Scout

repositories:

• org.eclipse.scout-aggregator.git
• org.eclipse.scout.rt.git
• org.eclipse.scout.sdk.git

SWTBot

Nebula

The Nebula build is using Tycho and Sonar. The build uses a continuous deployment strategy.

After source code is checked into the Nebula repository, the build is started automatically. The unit tests are executed and the resulting archives are automatically signed. After the signing process, the repository is pushed to the final location on download.eclipse.org where they can be consumed.

Link to the Nebula build page.

Linux Tools

Jubula

git repository: org.eclipse.jubula.core.git

build@hudson.eclipse.org: nightly

Orion

http://www.eclipse.org/orion/

EPP

Projects that are moving to CBI

Stardust

WTP

Projects that are not moving to CBI

Virgo