The Eclipse Common Build Infrastructure (CBI) is an initiative combining infrastructure, services, technologies and best practices for building, testing and delivering software at the Eclipse Foundation.
- 1 Goals
- 2 Asking for Help
- 3 Service Level Agreement (SLA)
- 4 Provided Services
- 4.1 CI Environment (Jenkins)
- 4.2 CI Environment (Third-party)
- 4.3 GitHub and Bot Accounts
- 4.4 Docker Hub
- 4.5 Nexus/Maven repository
- 4.6 Signing tool
- 4.7 Eclipse Platform / plugins specific tooling
- 5 Resources
Primary goals of the CBI initiative are:
- Make it easy for anyone to contribute to Eclipse projects.
- Make it easy for projects to follow open governance and transparency best practices.
- Provide a set of industry-grade services (or integration with some widely adopted 3rd party services) for building and distributing Eclipse projects.
Asking for Help
- Need help actually building your code: ask your project mentors, or ask on the Common Build mailing list (cbi-dev). There are no dumb questions.
- Subscribe to cbi-dev here: https://dev.eclipse.org/mailman/listinfo/cbi-dev
Service Level Agreement (SLA)
Most CBI services are Tier 2 - Best Effort, which means they are expected to be available at all times, and rapid restoration can be expected in the event of an outage. Eclipse Strategic Members can contact Webmaster in certain cases of off-hours support.
Please see IT_SLA for more information on the Eclipse Foundation IT Services SLA.
CI Environment (Jenkins)
We provide dedicated Jenkins instances to projects. See also Jenkins.
Jenkins is a continuous integration (CI) server used on Eclipse Foundation servers for Eclipse projects as part of the Common Build Infrastructure (CBI). Jenkins instances are maintained by the Eclipse Webmasters/Release Engineers. List of Jenkins Instances Per Project (JIPP):
- https://ci.eclipse.org/ (standalone / Kubernetes cluster)
NOTE: JIPP instances are being migrated from a standalone implementation to a Kubernetes cluster implementation.
Requesting a JIPP instance
Please file a bug against Eclipse Foundation > Community > CI-Jenkins to request your project's own instance. Please ensure your project lead can +1 the request. Please specify if you wish to grant write access to your download area and/or code repositories.
Each Eclipse Project has access to one Jenkins instance (JIPP), including the following:
- (1) Jenkins instance, with (1) Resources Pack (see below)
- Membership-sponsored projects may allocate more resources (see below)
- Digital signing Service: Java JAR, Java Cryptography Extensions, Windows Portable Executable with Microsoft Authenticode, macOS application bundles.
- Packaging service: Apple Disk Image (.dmg), Linux Flatpak
- Disk space: Ephemeral for builds, permanent for release builds.
- (1) 1vCPU/3.75G/30G Linux Virtual Server (if needed) (courtesy of Microsoft Azure). Projects sponsored by Strategic Members can engage with the Foundation to get out of spec Virtual Server.
- Access to worldwide download mirrors
Additional Resource Packs
Each Eclipse Project has access to one Resources Pack for building. For some projects, that may not be enough. Projects sponsored by Eclipse Membership (via Project Lead) have additional Packs, based on membership level. These Packs can be allocated to projects. See the Jenkins wiki page to see how packs translate to Jenkins builds.
- Some resources are only available to Enterprise and Strategic members.
- Enterprise and Strategic members can engage with the Foundation to acquire additional Packs.
|Agent type||Linux (containerized, no root)|
|vCPU||2 (burst to 4)|
|External slave support||Yes|
|Agent type||Linux/Windows/macOS (VMs)|
Resource Packs Included in Membership
Eclipse Foundation Member Organizations have access to Resource Packs based on their membership level.
|Not a member||Solution||Enterprise||Strategic|
|—||[$0, $15k)||[$15k, $20k]||[$50k, $100k]||[$25k, $50k)||[$50k, $100k)||[$100k, $500k]|
Note that Windows and macOS agents (shared and headless - not suitable to run UI tests) can be added to your Jenkins instance. In this case, each shared headless agent count for 1 resource packs.
Assigning Resource Packs to a Project
Resource Packs are assigned by Member organizations of the Eclipse Foundation to Eclipse Projects they sponsor. Packs are assigned as a whole to a single project (i.e., can’t split Packs across multiple projects). A member can assign several packs to a single project.
To assign a pack to a project, please file a Bug.
By default, resource packs are assigned build agents. In some cases, it may be required to scale up the Jenkins master. In such case, we can allocate resource packs to the master instance.
We maintain a public list of sponsored projects. We also maintain a list of the Member Organizations benefits. On this last spreadsheet, you can also check how many Resource Packs each organization have left for project sponsoring.
CI Environment (Third-party)
If you host your Eclipse project git repository at Github, we also support some third-party services:
- TravisCI. TravisCI is free to use for open source projects, but you should be aware that it limits to 5 the number of executors per organizations. It means that only 5 builds can run concurrently in any organization. If your repositories are part of the Eclipse organization, you may face long delays between the trigger and the actually start of the job. If it's your case, and would like to stick to TravisCI for building, we suggest you ask to move to a dedicated organization.
- CircleCI. https://circleci.com/
- Azure Pipelines. https://azure.microsoft.com/en-us/services/devops/pipelines/
If an environment is not listed in the unsupported list, you can ask whether it can be supported by opening a bug.
GitHub and Bot Accounts
The Eclipse Foundation can create a bot user that can be used from your Jenkins (JIPP) instance to build branches and pull requests, push, tag, and comment on the repo.
We don't share the credentials of those bots for external usage (e.g., to use it with a private, behind firewall Jenkins instance, or with third-party services). Those bots have the same set of permissions as a committer and it would be against the Eclipse Development Process to give those permissions to anybody. Likewise, we don't grant any elevated permissions on repositories or organizations to any other bot account.
However, we can setup webhooks for you. We create webhooks that can only receive the following events:
- Branch or tag creation (Branch or tag created)
- Branch or tag deletion (Branch or tag deleted)
- Pull requests (Pull request opened, closed, reopened, edited, assigned, unassigned, review requested, review request removed, labeled, unlabeled, synchronized, ready for review, locked, or unlocked)
- Pushes (Git push to a repository)
See the GitHub developer documentation for more information.
Personal Access Token
We can also create personal access token for the bot account. We create tokens with only the following scopes:
See the GitHub developer documentation about scopes and OAuth for more information.
Getting admin permissions on project's GitHub repositories
Project leads may require admin level access to their project's GitHub repositories. If that is the case, please open a new bug with your request. To be eligible to such permission level, your project must be in the mature phase and the request shall be highly motivated, so please tell us why you need that access (this information will be handy when sorting out the more general solution).
The Eclipse Foundation owns the eclipse organization and a couple of other project specific organizations at https://hub.docker.com. You can ask to get a repository being created on one of these organizations. We will set permissions so that committers have write access to this repo (you will need to share your Docker Hub ID with us).
You can also ask us to create a project specific organization. The organization name needs to follow the pattern eclipse<projectname>.
Note that we don't grant admin permissions on any Eclipse Foundation owned organization. We recognize that this means that you will have to go through us for all new repo creation, but we can't grant organizations-wide admin permission assigned to committers for security reasons.
Eclipse Platform / plugins specific tooling
CBI license bundle
We offer a P2 repository containing the `org.eclipse.license` bundle which is located at:
This URL is a composite P2 repo containing the license bundle.
If you use 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"/> ....
p2 repo checks
A set of "tests" which create reports or can be ran as unit tests that check to correctness of p2 repositories. That is partially just "correctness" in general (such as, that jars are signed, etc.) but more so that repositories conform to the requirements of the Eclipse Simultaneous release (such as, that jars have correct "Provider names", licenses, etc.). For more information, see See CBI/p2repoAnalyzers/Repo Reports.
p2 repo aggregator
A tool to combine several p2 repositories. Among other things, it makes sure they all have consistent constraints (that is, can be "installed together") unlike a raw p2 mirror task. For more information see CBI/aggregator.