adoptium / adoptium/infrastructure

Discussion: Replacement Jenkins Server

Open
#4,453 1 comment 0 reactions 1 assignee Claimed by @steelhead31 View on GitHub
enhancement Infra Machine issue Jenkins Machine Request pmc-agenda
Dominant language
Python
Stars
96
Forks
106
Avg merge
1d 23h
Merged PRs (30d)
13

Description

As part of https://github.com/adoptium/infrastructure/issues/4413

The original plan was to create a second server hosted by Hetzner, with an additional 1TB storage ( Total Budget for this was around E110 / month ( see https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/work_items/7463 for the approval ). This second server was required to allow a gradual transition from the existing Jenkins server and pipelines, to the new code and processes without jeopardising our current "production" jenkins instance. At some point post switch the original machine, may have been repurposed into a development/test jenkins, and potentially resized , or removed and relocated.

However now its time to do this, there is zero capacity at Hetzner within the approved budget, so the above EPIC is now blocked, and we need to decide how to proceed.

Feel free to list options in the comments below, but initially, the following options present themselves..

1. Seek approval for additional budget, in order to create the server within the available capacity at Hetzner ( This would involve an increase from E110 , to E190 / month. As part of this we could identify other cost savings across infrastructure, ( reduce usage of Orka, replacing with GHA runners ).

2. Attempt to do the work on a server hosted elsewhere, that is within the approved budget. Identify a suitable provider , or an existing one.

3. "Split" the current jenkins server, and attempt to host both instances on one server.

Feel free to discuss and add options below..

FYI @sxa , @smlambert , @andrew-m-leonard et al

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.