Discussion: Replacement Jenkins Server

[steelhead31]

As part of #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

[andrew-m-leonard]

Other option:

• We should expect a transfer of "capacity" from the old to the new jenkins instance, with that in mind, could a variation of (1) be evaluated, like "storage" saving when some builds move to the new... also maybe existing savings already done could reduce storage?