CBI can mean different things. Not only "Common Build Infrastructure", but also "Continuous Build Improvement". So whether you just joined the Eclipse community or have been around for a long time, this talk will give you an update what's new with CBI and how you can make use of it for your own project.
The Eclipse Common Build Infrastructure (CBI) is an initiative combining technologies and practices for building, testing, deploying and delivering Eclipse software. At it's core, CBI uses Maven with Tycho plugins to build Eclipse plugins and OSGi bundles. This should make it as easy as typing "mvn clean install" to build any Eclipse plugin.
As part of the CBI initiative the Eclipse Foundation offers build infrastructure like Hudson instances, build nodes, Git repositories, Gerrit, Nexus, SonarQube and signing services to reduce the setup time for new projects and advertise common practices for all parts of the software delivery process.
This talk will focus on the following topics:
- Short introduction to CBI
- Build infrastructure issues and remedies
- From HIPPs to JIPPs - Jenkins replaces Hudson as the default CI server for Eclipse projects
- Outlook: what's planned for the future?