!zghijEASpYQWYFzriI:nixos.org

Hydra

387 Members
111 Servers

Load older messages


SenderMessageTime
21 Jan 2022
@kenran_:matrix.orgkenran_ That's good to know! Right now the experimental machine I'm on has a separate volume attached that I can increase in size, but /var is still on the primary disk, which is quite small. So that won't scale at all sadly. 09:14:27
@janne.hess:helsinki-systems.dedas_j Currently running du for that on our machine. But you should also worry about your postgres database (no retention here) and your nix store (there is gcroot handling but the store can temporarily grow pretty large) 09:16:03
@janne.hess:helsinki-systems.dedas_j * Currently running du for that on our machineThe Hydra directory is only 20G for us. But you should also worry about your postgres database (no retention here) and your nix store (there is gcroot handling but the store can temporarily grow pretty large) 09:16:30
@kenran_:matrix.orgkenran_ (I mean, I could do the same thing I'm doing with /nix/store and mount -o bind,ro ... some directory on the volume "over" /var as well, but that seems error-prune.) 09:16:46
@kenran_:matrix.orgkenran_
In reply to @janne.hess:helsinki-systems.de
Currently running du for that on our machineThe Hydra directory is only 20G for us. But you should also worry about your postgres database (no retention here) and your nix store (there is gcroot handling but the store can temporarily grow pretty large)
Thanks for looking :)
09:17:11
@kenran_:matrix.orgkenran_So far I tried making the one 13GB-dir that's the reason for the bloat smaller, to no avail. Maybe I'll just try deleting it.09:17:40
@kenran_:matrix.orgkenran_ How would I go about pulling git sources from a custom GitLab instance? 10:07:25
@janne.hess:helsinki-systems.dedas_jLike you would use git10:07:47
@janne.hess:helsinki-systems.dedas_j * Like you would use git clone10:07:54
@kenran_:matrix.orgkenran_Oh sorry, didn't mean to send it already, I was still researching and accidentally hit Enter. I mean a private GitLab instance.10:08:05
@janne.hess:helsinki-systems.dedas_jah auth?10:08:17
@janne.hess:helsinki-systems.dedas_j hydra will just call git with HOME=/var/lib/hydra as the hydra user 10:08:50
@janne.hess:helsinki-systems.dedas_j This means that this git will pick up private keys in /var/lib/hydra/.ssh if they are owned by the hydra user 10:09:09
@kenran_:matrix.orgkenran_Yes exactly. I personally pull via SSH, so I guess I'd have to put some SSH key somewhere.10:09:25
@kenran_:matrix.orgkenran_
In reply to @janne.hess:helsinki-systems.de
This means that this git will pick up private keys in /var/lib/hydra/.ssh if they are owned by the hydra user
Currently skimming https://github.com/NixOS/hydra/issues/555, which seems to go well with what you wrote. Thanks for clarifying who does the pull.
10:09:57
@kenran_:matrix.orgkenran_I found out I can eval the jobset interactively as said one linked issue further, which makes debugging easier :)10:10:14
@kenran_:matrix.orgkenran_ das_j: Thank you very much, I'm quite some steps further now. I can actually pull, but I'm getting error: access to URI 'https://github.com/NixOS/nixpkgs/archive/b8512aa7f532794ceb8fa31840cbc8e2f1e60432.tar.gz' is forbidden in restricted mode. This looks like our nix expression which uses a pinned version is not allowed to be downloaded, but it just smells like sandboxing and is probably something easy to get working. 10:54:12
@janne.hess:helsinki-systems.dedas_jYou need to disable the restricted mode for this11:00:08
@janne.hess:helsinki-systems.dedas_jhttps://github.com/NixOS/hydra/pull/888 would do that properly but you can also just patch it out of hydra because the PR is not merged11:00:20
@janne.hess:helsinki-systems.dedas_j Just add this to postPatch of your Hydra package in the meantime: sed -i 's/evalSettings.restrictEval = true/evalSettings.restrictEval = false/' "$(find -name hydra-eval-jobs.cc)" 11:01:27
@janne.hess:helsinki-systems.dedas_j also cc grahamc (he/him) what about that PR? ๐Ÿ‘€ 11:01:35
@janne.hess:helsinki-systems.dedas_j * also cc grahamc (he/him) what about the aforementioned PR? ๐Ÿ‘€ 11:01:48
@kenran_:matrix.orgkenran_Ah, nice, that's your PR :D The PR #981 is merged though, wouldn't setting the option (where though?) suffice?11:03:45
@janne.hess:helsinki-systems.dedas_jpure eval != restricted eval though :D11:04:20
@kenran_:matrix.orgkenran_Oh, my bad11:04:59
@kenran_:matrix.orgkenran_ Woo, it's working, thanks again (I've never used postPatch, but I've just applied your PR as patch instead). 11:35:18
@kenran_:matrix.orgkenran_ Now LDAP login to go (not my job), and serving /nix/store to our soon-to-be-legacy GitLab jobs, and that was it :) 11:36:01
@janne.hess:helsinki-systems.dedas_j
In reply to @kenran_:matrix.org
Now LDAP login to go (not my job), and serving /nix/store to our soon-to-be-legacy GitLab jobs, and that was it :)
Hydra can do the serviing stuff as well but I recommend setting up a dedicated binary cache server like https://github.com/thoughtpolice/eris
11:37:07
@janne.hess:helsinki-systems.dedas_jit's slightly faster by not including an entire CI with web framework ;)11:37:26
@grahamc:nixos.org@grahamc:nixos.org
In reply to @janne.hess:helsinki-systems.de
https://github.com/NixOS/hydra/pull/888 would do that properly but you can also just patch it out of hydra because the PR is not merged
Iโ€™m not sure you even need that patch for that. I think you can add GitHub to allowed uriโ€™s.
11:40:24

Show newer messages


Back to Room ListRoom Version: 6