CBI

From Eclipsepedia

Jump to: navigation, search

The Eclipse Common Build Infrastructure (CBI) is an initiative combining technologies and practices for building Eclipse Software.

Contents

Initiative Goals

Primary

  • Make it really easy to contribute Eclipse projects
    • Make it really easy to copy & modify source
    • Make it really easy to build
    • Make it really easy to test
    • Make it really easy to post a change for review
    • Make it really easy to sign software

Secondary


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.

Next meeting

  • Bi-weekly conference call, Tuesdays 10:00 to 11:00 Eastern timezone. Conference bridge details. Contact andrew dot ross at eclipse dot org if you would like to be added to the Calendar reminder.
  • Code Sprint #2 - in July, 2012

GSoC

There are opportunities for students interested in participating in Google Summer of Code. Please see our list of project ideas and scan for CBI.

Resources

Notable Implementations

Preferred Build Technologies

Hudson

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.

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:

Signing tool

On demand signing tool

Related Topics and Links

Meeting Minutes