Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CBI"
(→Initiative Goals) |
m (Added category) |
||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 3: | Line 3: | ||
==What is CBI== | ==What is CBI== | ||
| − | The | + | 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 [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 19: | Line 33: | ||
* Get all Eclipse projects building their software on Eclipse Foundation hardware. | * Get all Eclipse projects building their software on Eclipse Foundation hardware. | ||
* Enable the [http://wiki.eclipse.org/EclipseLTS Long Term Support Program]. | * Enable the [http://wiki.eclipse.org/EclipseLTS Long Term Support Program]. | ||
| + | * Make it easy for people to build custom Eclipse distributions. | ||
| Line 44: | 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== | ||
| − | * [ | + | * [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 73: | 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=== | ||
| Line 101: | Line 122: | ||
* [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]] | ||
Revision as of 10:57, 22 February 2013
The Eclipse Common Build Infrastructure (CBI) is an initiative combining technologies and practices for building Eclipse Software.
Contents
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
- mailing list cbi-dev
Bugs
- CBI 1.0
- CBI 2.0
- List of All Bugs (Product = CBI)
Tutorials, News, and other resources
- Tycho tutorial by Lars Vogel
- Video discussing JBoss tools use of Tycho
- Workshops being developed
- Building Eclipse SDK locally with Maven
- Sonar at Eclipse.org !
- Tycho and CBI Adoption: Feedback from the trenches
- Eclipse Scout builds with CBI
Eclipse platform CBI build
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
- Reference Card
- Packaging Types
Nexus
Signing tool
Related Topics and Links
FAQ
- See your Frequently Asked Question list