Jump to: navigation, search

Difference between revisions of "CBI"

(Secondary)
(License Bundle)
 
(9 intermediate revisions by 4 users not shown)
Line 12: Line 12:
  
 
Gerrit, Bugzilla, and the Downloads site are closely related. Some might consider them part of CBI as well.
 
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 [http://wiki.eclipse.org/CBI/Projects 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==
 
==Initiative Goals==
Line 52: Line 59:
 
* [http://www.vogella.com/blog/2012/10/08/building-eclipse-sdk-locally-with-maven/ Building Eclipse SDK locally with Maven]
 
* [http://www.vogella.com/blog/2012/10/08/building-eclipse-sdk-locally-with-maven/ Building Eclipse SDK locally with Maven]
 
* [http://mickaelistria.wordpress.com/2012/10/08/sonar-at-eclipse-org/ Sonar at Eclipse.org !]
 
* [http://mickaelistria.wordpress.com/2012/10/08/sonar-at-eclipse-org/ Sonar at Eclipse.org !]
 +
* [http://youtu.be/KJUfLvXiTSw Tycho and CBI Adoption: Feedback from the trenches]
 +
* [http://www.bsiag.com/scout/?p=678 Eclipse Scout builds with CBI]
  
 
==Eclipse platform CBI build==
 
==Eclipse platform CBI build==
* [[CBI/Eclipse Platform Build]] see the [[CBI/Eclipse Platform Build Roadmap]]
+
* [http://wiki.eclipse.org/Platform-releng/Platform_Build Eclipse Platform Build based on CBI] see the [[CBI/Eclipse Platform Build Roadmap]]
  
 
==Preferred Build Technologies==
 
==Preferred Build Technologies==
Line 81: Line 90:
 
* [[Tycho/Reference_Card|Reference Card]]
 
* [[Tycho/Reference_Card|Reference Card]]
 
* [[Tycho/Packaging_Types|Packaging Types]]
 
* [[Tycho/Packaging_Types|Packaging Types]]
 +
 +
===Nexus===
 +
 +
[[Services/Nexus]]
  
 
===Signing tool===
 
===Signing tool===
  
[http://wiki.eclipse.org/IT_Infrastructure_Doc#Sign_my_plugins.2FZIP_files.3F On demand signing tool]
+
* [http://git.eclipse.org/c/cbi/org.eclipse.cbi.maven.plugins.git/tree/README Maven plugins for signing artifacts]
 +
* [http://wiki.eclipse.org/IT_Infrastructure_Doc#Sign_my_plugins.2FZIP_files.3F On demand signing tool]
 +
 
 +
==CBI License bundle==
 +
 
 +
We offer a P2 repository containing the org.eclipse.license bundle which is located at:
 +
 
 +
    http://download.eclipse.org/cbi/updates/license/
 +
 
 +
This URL is a composite P2 repo containing the license bundle.
 +
 
 +
 
 +
If you are using Tycho you can add the p2 repo to the <repositories> section of your pom.xml file. Something similar to this:
 +
 
 +
<pre>
 +
    <repository>
 +
      <id>license-feature</id>
 +
      <url>http://download.eclipse.org/cbi/updates/license/</url>
 +
      <layout>p2</layout>
 +
    </repository>
 +
</pre>
 +
 
 +
 
 +
In any particular feature which you need the license you can use the usual feature.xml section:
 +
 
 +
<pre>
 +
<?xml version="1.0" encoding="UTF-8"?>
 +
<feature
 +
      id="org.eclipse.help"
 +
      label="%featureName"
 +
      version="2.0.0.qualifier"
 +
      provider-name="%providerName"
 +
      plugin="org.eclipse.help.base"
 +
      license-feature="org.eclipse.license"
 +
      license-feature-version="1.0.0.qualifier">
 +
....
 +
</pre>
  
 
==Related Topics and Links==
 
==Related Topics and Links==
Line 109: Line 158:
 
* [http://wiki.eclipse.org/CBI/July25_2012 July 25, 2012]
 
* [http://wiki.eclipse.org/CBI/July25_2012 July 25, 2012]
 
* [http://wiki.eclipse.org/CBI/November15_2012 November 15, 2012]
 
* [http://wiki.eclipse.org/CBI/November15_2012 November 15, 2012]
 +
* [http://wiki.eclipse.org/CBI/January8_2013 January 8, 2013]
 +
 +
[[Category:CBI]]

Latest revision as of 08:33, 18 October 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

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

  • 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

Resources

Bugs

Tutorials, News, and other resources

Eclipse platform CBI build

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:

Nexus

Services/Nexus

Signing tool

CBI License bundle

We offer a P2 repository containing the org.eclipse.license bundle which is located at:

   http://download.eclipse.org/cbi/updates/license/

This URL is a composite P2 repo containing the license bundle.


If you are using Tycho you can add the p2 repo to the <repositories> section of your pom.xml file. Something similar to this:

    <repository>
      <id>license-feature</id>
      <url>http://download.eclipse.org/cbi/updates/license/</url>
      <layout>p2</layout>
    </repository>


In any particular feature which you need the license you can use the usual feature.xml section:

<?xml version="1.0" encoding="UTF-8"?>
<feature
      id="org.eclipse.help"
      label="%featureName"
      version="2.0.0.qualifier"
      provider-name="%providerName"
      plugin="org.eclipse.help.base"
      license-feature="org.eclipse.license"
      license-feature-version="1.0.0.qualifier"> 
....

Related Topics and Links

FAQ

Meeting Minutes