servo / servo/project

Self-hosted runners

Open
#180 4 comments 0 reactions 1 assignee View on GitHub

@delan is already working on this.

Since Feb 24, 2026.

funding funding: approved
Dominant language
No language data
Stars
254
Forks
13
PR merge metrics
No merged PRs in 30d

Description

Summary

The idea is to add dedicated servers for CI runners so we can speed up CI time.

Also add dedicated servers for benchmarking.

A proposal by a group of contributors was done back in July 2024: https://github.com/servo/project/issues/94#issuecomment-2252262955

And in July 2025 a proposal for benchmarking: https://github.com/servo/project/issues/160

Current cost: 404 EUR/month

  • 104 EUR/month - ci0.servo.org, general self-hosted runners
  • 104 EUR/month - ci1.servo.org, general self-hosted runners
  • 104 EUR/month - ci2.servo.org, general self-hosted runners
  • 46 EUR/month - ci3.servo.org, self-hosted runners for benchmarking
  • 46 EUR/month - ci4.servo.org, self-hosted runners for benchmarking
Type

Shared resources

Cost

404 EUR/month

Periodicity

Recurring monthly payment

Benefits

This helps us to reduce CI times in Servo significantly.

Also the benchmarking runners allow to get accurate data when measuring Servo performance.

Risks

Slower CI times will make the project less appealing to contribute to.

Also current benchmarking results are inaccurate as we don't use a dedicated machine.

Alternatives

A few alternatives were considered at https://github.com/servo/project/issues/88#issuecomment-2134485100

Finally Hetzner was the provider selected.

Administrator

@delan has been in charge of this.

Experience

@delan has experience administrating servers and has been doing this since we setup things for Servo.

Other comments

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.