The Eclipse Common Build Infrastructure (CBI) is an initiative combining technologies and practices for building Eclipse Software.
- Get all Eclipse projects building their software on Eclipse Foundation hardware.
- Use and provide reference examples of best of breed build technologies and processes.
- Enable the Long Term Support Program.
There is a strong link between CBI and the Long Term Support Program which enables a marketplace of companies providing maintenance and support for Eclipse technologies for durations far beyond typical community support. Please NOTE: CBI features will be available to community.
It is our hope that this project develops an offering that is compelling so that many projects will move to use it.
- Conference call, March 20, 2012, 10:00 to 11:00 Eastern. Please contact Andrew dot Ross at Eclipse dot org to be added to the invitation (which has the conference bridge details)
- Information session @ EclipseCon, Wednesday March 28, 10:15 to 12:00 Eastern. This session will be in Reston Suites A, on the second floor.
There are opportunities for students interested in participating in Google Summer of Code. Please see our list of project ideas and scan for CBI.
Preferred Build Technologies
Maven 3.0 drives the builds. Projects are expected to provide standard Maven 3.0 POM files for their builds. The builds should be built in such a way that they can be run on the local workstation, or on the Eclipse build server. Note that builds can only be signed on the Eclipse build server.
- Parent Maven POM for Eclipse projects;
- Signing Builds using Maven; and
- Maven repository support at Eclipse.
Tycho is focused on a Maven-centric, manifest-first approach to building Eclipse plug-ins, features, update sites, RCP applications and OSGi bundles.