Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

Difference between revisions of "CBI"

(Signing tool)
(Signing tool)
Line 97: Line 97:
===Signing tool===
===Signing tool===
* [[:CBI:Maven Plugins for Signing Artifacts]]
* [ Maven plugins for signing artifacts]
* [ On demand signing tool]
* [ On demand signing tool]

Revision as of 13:30, 19 July 2013

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

What is CBI

The core of CBI today is Maven with the Tycho plugins. The Tycho plugins teach Maven how to build (and consume) Eclipse plugins and OSGi bundles. This enables building Eclipse projects with "maven clean install" just as one would build other Maven projects.

Common services such as the Jar signing facility, MacOS signing facility, and Windows signing facility are also included with CBI. Other tools and services may be included in the future as the need arises.

Over time mature templates and common pom.xml files will be provided that set common values finely honed with experience.

One might go so far as to include Git, Hudson, the build slaves, and Nexus (aka. the artifact repository & server side of Maven) as part of CBI since they are also common and crucial to builds.

Gerrit, Bugzilla, and the Downloads site are closely related. Some might consider them part of CBI as well.

Who is using it?

There's a list of projects building with CBI available.

The Eclipse Foundation would like to have more than 50% of projects building with CBI by end of 2013.

Initiative Goals


  • 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


  • Get all Eclipse projects building their software on Eclipse Foundation hardware.
  • Enable the Long Term Support Program.
  • Make it easy for people to build custom Eclipse distributions.

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

See the conference bridge details. Contact andrew dot ross at eclipse dot org if you would like to be added to the Calendar reminder. The dates the upcoming calls are as follows:

  • November 15th, 9am EST



Tutorials, News, and other resources

Eclipse platform CBI build

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.


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

Related Topics and Links


Meeting Minutes

Back to the top