Dedicated build agents

Can I add a dedicated agent to my Jenkins instance?

Yes, we can connect external machines to your Jenkins instance. For Linux and macOS agents, we recommend connecting them via SSH. It means that the machine must be addressable on the internet with an SSH port open. For Windows agents (or other agents where SSH is not possible), agents can be connected via WebSocket. The connection will be at the initiative of the agents (rightfully called inbound agents in this case), meaning that the Jenkins instance will have little control over the connection. The advantage is that the agent machine does not need to be addressable on the internet and can run entirely behind a firewall. See Jenkins documentation for more information. Note that we don't support inbound agents over direct TCP connection.

Please note, due to increased security concerns, the requirements for external dedicated agents are stricter now.

Attaching a dedicated agent can be requested via a HelpDesk ticket.

What kind of dedicated agents are provided by the Eclipse Foundation?

The Eclipse Foundation provides some shared resources to projects. At this time we provide:

• Riscv64 servers based on VisionFive2 SOC boards, with 8 GB RAM, 4 cores, 960 GB SSD Nvme storage. At this point, we estimate that each machine can host up to 4 containers with oversubscription.

  Containers are delivered with latest (at the moment of container creation) Ubuntu https://hub.docker.com/r/riscv64/ubuntu/ and with the following tooling:

  • Temurin JDK 21 LTS https://adoptium.net/en-GB/temurin/releases/?arch=riscv64&version=21
  • Maven 3.9.9
  • Ant 1.10.5

  Additional packages installed:

  • build-essential
  • libboost-all-dev
  • libssl-dev
  • libgtk-3-dev
  • libglu1-mesa-dev
  • libgtk-3-dev

  This will be mostly on a first-come-first-serve basis. If more projects need more compute time on riscv64, we will need to delegate projects to cloud services like Scaleway at some point.