@AndresFreundTec@mastodon.social
Post #1075296
2026-04-09 20:17 UTC
Replies (3)
-
@AndresFreundTec@mastodon.social 2026-04-09 20:29
For our own compute we've been averaging daily: - 1464 core hours (full cores, not SMT) - 396 of which were windows (visible due to the licensing cost) - 40GB of artifacts - doesn't include macos, which I can't track as easily, due to being self hosted runners So we will likely need something where we can continue to provide compute ourselves, to keep this affordable.
-
@Cs137@chaos.social 2026-04-09 20:19
@AndresFreundTec @WoodpeckerCI might be an option
-
@deepbluev7@nheko.io 2026-04-09 21:39
@AndresFreundTec@mastodon.social We are using tart with gitlab-ci. It is not clear yet, if that will also get shut down in the near future, since that was their VM software, but at least for now it seems to still be maintained, so maybe that would be an option? For Windows we just use gitlab-ci with a custom runner, that starts libvirt VMs. It is quite flexible and probably could be made to fit most things, but it does take some effort to setup and maintenance as well as compute hardware. However we already run our own Gitlab as well, so it is quite likely, that our solution is not a good fit at all for you. But I do think running your own CI hardware using open-source tools wasn't a bad idea.