Difference between revisions of "CBI"

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.

Jump to: navigation, search

Revision as of 11:17, 16 November 2012

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

1 Initiative Goals
- 1.1 Primary
- 1.2 Secondary
2 Next meeting
3 Resources
- 3.1 Bugs
4 Tutorials, News, and other resources
5 Eclipse platform CBI build
6 Preferred Build Technologies
7 Related Topics and Links
8 FAQ
9 Meeting Minutes

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.

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

Eclipse platform CBI build

CBI/Eclipse Platform Build see the CBI/Eclipse Platform Build Roadmap

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

Signing tool

On demand signing tool

FAQ

See your Frequently Asked Question list

Meeting Minutes

January 10, 2012
January 24, 2012
February 7, 2012
March 6, 2012
March 20, 2012
Code Sprint #1, April 11, 2012 - in Ottawa, Canada
April 17, 2012
May 1, 2012
May 15, 2012
May 29, 2012
June 12, 2012
June 26, 2012
July 25, 2012
November 15, 2012

Retrieved from "https://wiki.eclipse.org/index.php?title=CBI&oldid=322391"

@@ Line 8: / Line 8: @@
 ** 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
-** Make it really easy to post a change for review
 ===Secondary===
@@ Line 23: / Line 22: @@
 ==Next meeting==
-* Bi-weekly conference call, Tuesdays 10:00 to 11:00 Eastern timezone. [http://wiki.eclipse.org/CBI/Conference Conference bridge details]. Contact andrew dot ross at eclipse dot org if you would like to be added to the Calendar reminder.
+See the [http://wiki.eclipse.org/CBI/Conference 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:
-* [http://wiki.eclipse.org/CBI/Code_Sprint_April_11_2012 Code Sprint #1] - in Ottawa, Canada
+* November 15th, 9am EST
-* 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 [http://wiki.eclipse.org/Google_Summer_of_Code_2012_Ideas project ideas and scan for CBI].
 ==Resources==
 * mailing list [https://dev.eclipse.org/mailman/listinfo/cbi-dev cbi-dev]
-* [https://bugs.eclipse.org/bugs/buglist.cgi?action=wrap&product=CBI&list_id=38248 List of Bugs] (Product = CBI)
-==Notable Implementations==
+===Bugs===
-* [[CBI/Eclipse Platform Build]] see the [[CBI/Eclipse Platform Build Roadmap]]
+* [https://bugs.eclipse.org/bugs/buglist.cgi?action=wrap;product=CBI;version=1.0;list_id=2249872 CBI 1.0]
+* [https://bugs.eclipse.org/bugs/buglist.cgi?action=wrap;product=CBI;version=2.0;list_id=2249872 CBI 2.0]
+* [https://bugs.eclipse.org/bugs/buglist.cgi?action=wrap&product=CBI&list_id=38248 List of All Bugs] (Product = CBI)
+==Tutorials, News, and other resources==
+* [http://www.vogella.com/articles/EclipseTycho/article.html Tycho tutorial by Lars Vogel]
 * [http://www.fosslc.org/drupal/content/tycho-good-bad-and-ugly Video discussing JBoss tools use of Tycho]
+* [http://wiki.eclipse.org/CBI/Workshops Workshops being developed]
+* [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 !]
+==Eclipse platform CBI build==
+* [[CBI/Eclipse Platform Build]] see the [[CBI/Eclipse Platform Build Roadmap]]
 ==Preferred Build Technologies==
@@ Line 62: / Line 66: @@
 * [[Tycho|Tycho project]] information, including [[Tycho/Demo Projects|demo projects]]; and
 * [http://waynebeaton.wordpress.com/2010/09/23/building-woolsey-with-maven-and-tycho/ Building Woolsey with Maven and Tycho]
+* [[Tycho/Reference_Card|Reference Card]]
+* [[Tycho/Packaging_Types|Packaging Types]]
+===Signing tool===
+[http://wiki.eclipse.org/IT_Infrastructure_Doc#Sign_my_plugins.2FZIP_files.3F On demand signing tool]
 ==Related Topics and Links==
 * [http://wiki.eclipse.org/EclipseLTS Long Term Support]
 * [http://wiki.eclipse.org/Build_Technologies List of Build Technologies]
+==FAQ==
+* See your [http://wiki.eclipse.org/CBI/FAQ Frequently Asked Question list]
 ==Meeting Minutes==
@@ Line 73: / Line 87: @@
 * [http://wiki.eclipse.org/CBI/March6_2012 March 6, 2012]
 * [http://wiki.eclipse.org/CBI/Mar20_2012 March 20, 2012]
+* [http://wiki.eclipse.org/CBI/Code_Sprint_April_11_2012 Code Sprint #1, April 11, 2012] - in Ottawa, Canada
-==FAQ==
+* [http://wiki.eclipse.org/CBI/Apr17_2012 April 17, 2012]
+* [http://wiki.eclipse.org/CBI/May1_2012 May 1, 2012]
-===What does the CBI build of the Eclipse platform do?===
+* [http://wiki.eclipse.org/CBI/May15_2012 May 15, 2012]
+* [http://wiki.eclipse.org/CBI/May29_2012 May 29, 2012]
-Answer: The CBI build of the Eclipse platform is intended to produce the same output as the PDE build, and thus facilitate packaging without noticeable change. The noticeable difference the CBI build of the platform makes is ease of use to build the platform. For example, the prototype has consistently demonstrated that a newcomer without prior experience can build the Eclipse platform with under 30 minutes of effort on a machine with a supported JDK & Maven.
+* [http://wiki.eclipse.org/CBI/June12_2012 June 12, 2012]
+* [http://wiki.eclipse.org/CBI/June26_2012 June 26, 2012]
+* [http://wiki.eclipse.org/CBI/July25_2012 July 25, 2012]
-===What is the link between CBI & LTS?===
+* [http://wiki.eclipse.org/CBI/November15_2012 November 15, 2012]
-Answer: The Long Term Support program is aimed at enabling organizations to support and maintain Eclipse software far into the future, for decades if needed. Part of the program enables maintenance committers working on behalf of the company to fix issues. Ensuring a very easy to use, very easy to maintain, and portable build was essential to the program. The fact that a build with these attributes also provides much benefit to the community was another good reason to do CBI.
-===Won't CBI be kept behind a firewall at Eclipse?===
-Answer: No, the work done for CBI will be public and available and projects will be encouraged to leverage them. In the future, there may be some enhanced tools and features based on CBI designed to make Long Term Support (LTS) easier/more efficient/more effective. These might be available to members of the LTS working group only and enable a business model which supports the Eclipse Foundation.
-===Will my project be forced to move to CBI?===
-Answer: No, there are no plans for forcing projects to use CBI. But if CBI develops the way we intend, you'll likely feel there's much good value to use it and decide to move to CBI on your own. Part of the benefit include the really easy to use & powerful build. Part of the benefit is that using CBI allows the Eclipse Foundation's release engineer to provide some assistance to ensure your project has a really good build. Another important part of the CBI initiative is a Continuous integration facility and build farm maintained by the Eclipse Foundation... so you don't need to create & maintain one yourself somewhere else.
-===Isn't this just yet-another-build system at Eclipse?===
-Answer: In truth, many of the technologies involved with CBI such as Maven, Tycho, Hydson, Git, etc. were already in use by a number of projects who consider them to be best of breed. In addition, they were/are being considered by others. Thus in a way, CBI is an evolutionary effort building on momentum in the community. Technologies such as Maven and Nexus (the artefact storage repository often used with Maven) are ubiquitous and very popular.

Breadcrumbs