Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
CBI
The Eclipse Common Build Infrastructure (CBI) is an initiative combining technologies and practices for building Eclipse Software.
Contents
Initiative Goals
- 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.
It is our hope that this project develops an offering that is compelling so that many projects will move to use it.
Resources
- mailing list cbi-dev
- List of bugzilla tickets (Product = CBI)
Notable Implementations
Preferred Build Technologies
Hudson
- The Eclipse Hudson instance; and
- Hudson projects using Maven and Tycho.
Maven
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
Tycho is focused on a Maven-centric, manifest-first approach to building Eclipse plug-ins, features, update sites, RCP applications and OSGi bundles.
Helpful links:
- Tycho project information, including demo projects; and
- Building Woolsey with Maven and Tycho