Skip to main content
Jump to: navigation, search

Difference between revisions of "CBI"

(Initiative Goals)
(Docker Hub)
 
(94 intermediate revisions by 13 users not shown)
Line 1: Line 1:
The Eclipse Common Build Infrastructure (CBI) is an initiative combining technologies and practices for building Eclipse Software.
+
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.
  
==Initiative Goals==
+
= Goals =
 +
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.
  
===Primary===
+
= Asking for Help =
* 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 sign software
+
** Make it really easy to post a change for review
+
  
 +
* 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
  
===Secondary===
+
= Service Level Agreement (SLA) =
* Get all Eclipse projects building their software on Eclipse Foundation hardware.
+
* Enable the [http://wiki.eclipse.org/EclipseLTS Long Term Support Program].
+
  
 +
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.
  
There is a strong link between CBI and the [http://wiki.eclipse.org/EclipseLTS 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.
+
Please see [[IT_SLA]] for more information on the Eclipse Foundation IT Services SLA.
  
It is our hope that this project develops an offering that is compelling so that many projects will move to use it.
+
= Provided Services =
  
==Next meeting==
+
== CI Environment (Jenkins) ==
  
* 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.
+
We provide dedicated Jenkins instances to projects. See also [[Jenkins]].
* [http://wiki.eclipse.org/CBI/Code_Sprint_April_11_2012 Code Sprint #1] - in Ottawa, Canada
+
* Code Sprint #2 - in July, 2012
+
  
==GSoC==
+
Jenkins is a continuous integration (CI) server used on Eclipse Foundation servers for Eclipse projects as part of the [[CBI|Common Build Infrastructure (CBI)]]. Jenkins instances are maintained by the Eclipse Webmasters/Release Engineers. List of Jenkins Instances Per Project (JIPP):
  
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].
+
* https://ci.eclipse.org/ (standalone / Kubernetes cluster)
  
==Resources==
+
NOTE: JIPP instances are being migrated from a standalone implementation to a Kubernetes cluster implementation.
* 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==
+
=== Requesting a JIPP instance ===
* [[CBI/Eclipse Platform Build]] see the [[CBI/Eclipse Platform Build Roadmap]]
+
* [http://www.fosslc.org/drupal/content/tycho-good-bad-and-ugly Video discussing JBoss tools use of Tycho]
+
  
==Preferred Build Technologies==
+
Please [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=CI-Jenkins&short_desc=JIPP%20Request%20for%20project%20XXX 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.
  
===Hudson===
+
{{important|Security issues| There may be security issues related to using the Gerrit plugin, more especially when allowing the CI system to write directly to the code repos and downloads area. If you request plugins other than those installed by default, webmasters may not be able to help troubleshoot any issues that you may encounter with your instance.}}
  
* The Eclipse [http://hudson.eclipse.org Hudson instance]; and
+
=== What's provided? ===
* Hudson projects using [https://hudson.eclipse.org/hudson/view/Tycho%20+%20Maven/ Maven and Tycho].
+
  
===Maven===
+
Each Eclipse Project has access to one Jenkins instance (JIPP), including the following:
  
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.
+
* (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
  
* [[Maven/Parent POM|Parent Maven POM]] for Eclipse projects;
+
=== Additional Resource Packs ===
* [[Minerva#Signing|Signing Builds]] using Maven; and
+
* [[Maven|Maven repository support at Eclipse]].
+
  
===Tycho===
+
Each Eclipse Project has access to one Resources Pack for building. For some projects, that may not be enough. Projects sponsored by [https://www.eclipse.org/membership/exploreMembership.php Eclipse Membership] (via Project Lead) have additional Packs, based on [https://www.eclipse.org/membership/become_a_member/membershipTypes.php membership level]. These Packs can be allocated to projects. See the [[Jenkins#About_resource_packs_and_quotas|Jenkins wiki page]] to see how packs translate to Jenkins builds.
  
Tycho is focused on a Maven-centric, manifest-first approach to building Eclipse plug-ins, features, update sites, RCP applications and OSGi bundles.
+
* Some resources are only available to [https://www.eclipse.org/membership/become_a_member/membershipTypes.php Enterprise and Strategic members].
 +
* Enterprise and Strategic members can engage with the Foundation to acquire additional Packs.
  
Helpful links:
+
{| class="wikitable" style="float: left; width:48%"
 +
|+ style="text-align: center;caption-side:top; color:#e76700;font-size:150%"|''Resource Pack''
 +
|-
 +
! scope="row"| Agent type
 +
| style="text-align: center" | Linux (containerized, no root)
 +
|-
 +
! scope="row"| vCPU
 +
| style="text-align: center" | 2 (burst to 4)
 +
|-
 +
! scope="row"| RAM
 +
| style="text-align: center" | 8GiB
 +
|-
 +
! scope="row"| Disk
 +
| style="text-align: center" | 50GB
 +
|-
 +
! scope="row"| External slave support
 +
| style="text-align: center" | Yes
 +
|}
  
* [[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]
 
  
==Related Topics and Links==
+
{| class="wikitable" style="float: right; width:48%"
* [http://wiki.eclipse.org/EclipseLTS Long Term Support]
+
|+ style="text-align: center;caption-side:top; color:#5E97F6;font-size:150%"|''Dedicated Agent''
* [http://wiki.eclipse.org/Build_Technologies List of Build Technologies]
+
|-
 +
! scope="row"| Agent type
 +
| style="text-align: center" | Linux/Windows/macOS (VMs)
 +
|-
 +
! scope="row"| vCPU
 +
| style="text-align: center" | 4
 +
|-
 +
! scope="row"| RAM
 +
| style="text-align: center" | 8GiB
 +
|-
 +
! scope="row"| Disk
 +
| style="text-align: center" | 100GB
 +
|}
  
==Meeting Minutes==
+
==== Resource Packs Included in Membership ====
* [http://wiki.eclipse.org/CBI/Jan10_2012 January 10, 2012]
+
* [http://wiki.eclipse.org/CBI/Jan24_2012 January 24, 2012]
+
* [http://wiki.eclipse.org/CBI/Feb7_2012 February 7, 2012]
+
* [http://wiki.eclipse.org/CBI/March6_2012 March 6, 2012]
+
* [http://wiki.eclipse.org/CBI/Mar20_2012 March 20, 2012]
+
  
==FAQ==
+
Eclipse Foundation Member Organizations have access to Resource Packs based on their [https://www.eclipse.org/membership/become_a_member/membershipTypes.php membership level].
  
===What does the CBI build of the Eclipse platform do?===
+
{| class="wikitable"
 +
|+ style="text-align: center;caption-side:top; color:#239F60;font-size:150%"|''Membership Level and Resource Packs''
 +
|-
 +
! scope="col" style="background-color: #fff; border-top: 1px solid white;border-left: 1px solid white;border-bottom: 1px solid white"|
 +
! scope="col"| Not a member
 +
! scope="col" colspan="2"| Solution
 +
! scope="col"| Enterprise
 +
! scope="col" colspan="3"| Strategic
 +
|-
 +
! scope="row" style="background-color: #fff; border-top: 1px solid white;border-left: 1px solid white"|
 +
| style="text-align: center" | —
 +
| style="text-align: center" | [$0, $15k)
 +
| style="text-align: center" | [$15k, $20k]
 +
| style="text-align: center" | [$50k, $100k]
 +
| style="text-align: center" | [$25k, $50k)
 +
| style="text-align: center" | [$50k, $100k)
 +
| style="text-align: center" | [$100k, $500k]
 +
|-
 +
! scope="row"| Resource packs
 +
| style="text-align: center" | 1
 +
| style="text-align: center" | 1
 +
| style="text-align: center" | 2
 +
| style="text-align: center" | 4
 +
| style="text-align: center" | 3
 +
| style="text-align: center" | 5
 +
| style="text-align: center" | 10
 +
|-
 +
! scope="row" | Dedicated Agents
 +
| style="text-align: center" | N/A
 +
| style="text-align: center" | N/A
 +
| style="text-align: center" | N/A
 +
| style="text-align: center" | 0
 +
| style="text-align: center" | 0
 +
| style="text-align: center" | 0
 +
| style="text-align: center" | 2
 +
|}
  
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.
+
{{important|Windows and macOS agents|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. These agents have common dependencies like JDK, Maven, etc installed. If your build requires specific/special dependencies you might need to setup your own external build agent instead.}}
  
 +
==== Assigning Resource Packs to a Project ====
  
===What is the link between CBI & LTS?===
+
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.
  
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.
+
{{note|Important| When asking for packs for your project, please ensure that project leads and your organization representatives are copied to the bugzilla ticket. We require approval from project leads but assume immediate approval from organization representatives. We strongly advise you seek authorization internally to your organization before opening such a request though. Should conflictual requests arise, the organization representatives will be asked to actively arbitrate.}}
  
 +
To assign a pack to a project, please [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=CI-Jenkins&short_desc=Assign%20resource%20pack%20to%20project%20NAME_OF_THE_PROJECT file a Bug].
  
===Won't CBI be kept behind a firewall at Eclipse?===
+
''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.''
  
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.
+
==== Sponsored Projects ====
  
 +
We maintain a public [https://docs.google.com/spreadsheets/d/e/2PACX-1vQGhAH2b-BdoW5MAgmCG8NLfAjZMe7fIgsYNtUMREmIeAXmAPjDkZOx1OHaz0-INS51TGN41C3zcbI8/pubhtml?gid=832654757&single=true list of sponsored projects]. We also maintain a list of the [https://docs.google.com/spreadsheets/d/e/2PACX-1vQGhAH2b-BdoW5MAgmCG8NLfAjZMe7fIgsYNtUMREmIeAXmAPjDkZOx1OHaz0-INS51TGN41C3zcbI8/pubhtml?gid=746314272&single=true Member Organizations benefits]. On this last spreadsheet, you can also check how many Resource Packs each organization have left for project sponsoring.
  
===Will my project be forced to move to CBI?===
+
== CI Environment (Third-party) ==
  
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.
+
If you host your Eclipse project git repository at Github, we also support some third-party services:
 +
* ''TravisCI''. [https://travis-ci.com/ 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 [https://github.com/eclipse/ 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 [https://wiki.eclipse.org/GitHub#Project_dedicated_organization 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 [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=CI-Jenkins opening a bug].
  
===Isn't this just yet-another-build system at Eclipse?===
+
{{important|Third party build services (e.g., Travis) limitations|The Eclipse Foundation's IT Team is responsible for the credentials (OSSRH, SSH and GPG keys...) it creates for projects. Keeping track of where credentials are disseminated is crucial for security reasons. As long as we have no automation in place to set/update/remove credentials on 3rd party build services, we don't put any credential on such services. For instance, it means that you can't use them to publish to Maven Central, or to upload build results to download.eclipse.org.}}
  
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.
+
== 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.
 +
 
 +
=== Webhooks ===
 +
 
 +
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 [https://developer.github.com/webhooks/ 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:
 +
 
 +
* repo:status
 +
* repo_deployment
 +
* write:discussion
 +
 
 +
See the [https://developer.github.com/apps/building-oauth-apps/understanding-scopes-for-oauth-apps 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 [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=GitHub 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).
 +
 
 +
== Docker Hub ==
 +
 
 +
The Eclipse Foundation owns the [https://hub.docker.com/u/eclipse 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.
 +
 
 +
In all cases, requests should be directed to [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Outside%20Services bugzilla].
 +
 
 +
==Nexus/Maven repository==
 +
 
 +
See [[Services/Nexus]].
 +
 
 +
==Signing tool==
 +
 
 +
* [https://git.eclipse.org/c/cbi/org.eclipse.cbi.git/tree/maven-plugins/README.md Maven plugins for signing artifacts]
 +
* [[IT_Infrastructure_Doc#Sign_my_plugins.2FZIP_files.3F|On demand signing tool]]
 +
 
 +
==Eclipse Platform / plugins specific tooling==
 +
 
 +
=== 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 use Tycho you can add the p2 repo to the <repositories> section of your pom.xml file. Something similar to this:
 +
 
 +
<source lang="xml">
 +
    <repository>
 +
      <id>license-feature</id>
 +
      <url>http://download.eclipse.org/cbi/updates/license/</url>
 +
      <layout>p2</layout>
 +
    </repository>
 +
</source>
 +
 
 +
In any particular feature which you need the license you can use the usual feature.xml section:
 +
 
 +
<source lang="xml">
 +
<?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"/>
 +
....
 +
</source>
 +
 
 +
=== 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]].
 +
 
 +
= Resources =
 +
* [https://dev.eclipse.org/mailman/listinfo/cbi-dev cbi-dev]
 +
* See our [[CBI/FAQ|Frequently Asked Question list]]
 +
 
 +
 
 +
[[Category:CBI]] [[Category:Releng]] [[Category:Jenkins]]

Latest revision as of 09:29, 10 November 2020

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.

Goals

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

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.

Provided Services

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):

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.

Important.png
Security issues
There may be security issues related to using the Gerrit plugin, more especially when allowing the CI system to write directly to the code repos and downloads area. If you request plugins other than those installed by default, webmasters may not be able to help troubleshoot any issues that you may encounter with your instance.


What's provided?

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.
Resource Pack
Agent type Linux (containerized, no root)
vCPU 2 (burst to 4)
RAM 8GiB
Disk 50GB
External slave support Yes


Dedicated Agent
Agent type Linux/Windows/macOS (VMs)
vCPU 4
RAM 8GiB
Disk 100GB

Resource Packs Included in Membership

Eclipse Foundation Member Organizations have access to Resource Packs based on their membership level.

Membership Level and Resource Packs
Not a member Solution Enterprise Strategic
[$0, $15k) [$15k, $20k] [$50k, $100k] [$25k, $50k) [$50k, $100k) [$100k, $500k]
Resource packs 1 1 2 4 3 5 10
Dedicated Agents N/A N/A N/A 0 0 0 2
Important.png
Windows and macOS agents
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. These agents have common dependencies like JDK, Maven, etc installed. If your build requires specific/special dependencies you might need to setup your own external build agent instead.


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.

Note.png
Important
When asking for packs for your project, please ensure that project leads and your organization representatives are copied to the bugzilla ticket. We require approval from project leads but assume immediate approval from organization representatives. We strongly advise you seek authorization internally to your organization before opening such a request though. Should conflictual requests arise, the organization representatives will be asked to actively arbitrate.


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.

Important.png
Third party build services (e.g., Travis) limitations
The Eclipse Foundation's IT Team is responsible for the credentials (OSSRH, SSH and GPG keys...) it creates for projects. Keeping track of where credentials are disseminated is crucial for security reasons. As long as we have no automation in place to set/update/remove credentials on 3rd party build services, we don't put any credential on such services. For instance, it means that you can't use them to publish to Maven Central, or to upload build results to download.eclipse.org.


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.

Webhooks

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:

  • repo:status
  • repo_deployment
  • write:discussion

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).

Docker Hub

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.

In all cases, requests should be directed to bugzilla.

Nexus/Maven repository

See Services/Nexus.

Signing tool

Eclipse Platform / plugins specific tooling

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 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.

Resources

Back to the top