Gitea runners cluster #90
Labels
No Label
dns
exploration
gitea
mail
new stuff
services
software
art
backup
big
blocked
bug
crash report
disputed
documentation
duplicate
enhancement
good first issue
logging
nixos
question
salt
security
servers n' hardware
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Blocks
#6 Move to `Projects`
oysteikt/mpvipc-async
#85 Automate tests, coverage, documentation and releases
Projects/mysqladm-rs
Reference: Drift/issues#90
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Setting up my cluster of three Dell Optiplex 5050 and two 7040 as nodes to run gitea runners for PVVs CI/CD (giving them to PVV if we actually decide to put it into permanent production.)
I am researching and planing an implementation of the cluster. Proposal next drift meeting
Name is Lupine
of interest: https://git.clan.lol/clan/clan-infra/src/branch/main/modules/web01/gitea/actions-runner.nix via https://discourse.nixos.org/t/gitea-nix-actions-runner-setup/35279
I think the plan for this was to use ansible, and the 6 optiplex nodes on the top of the server pile at PVV as our main runners. If anything, we might want to reference either https://github.com/nodiscc/xsrv/tree/master/roles/gitea_act_runner or https://github.com/morbidick/ansible-role-act_runner
See https://git.pvv.ntnu.no/Drift/gitea-runner-cluster
Not sure if this is any better, but dam the ui looks good.
https://buildbot.net/
https://search.nixos.org/options?query=buildbot
https://buildbot.thalheim.io/#/builders/588/builds/32