fix(ops/machines): set build-dir Nix setting
It looks like setting TMPDIR did not have the desired effect. I still see a bunch of recent nix-build directories in /tmp. Let's use the dedicated nix.conf setting, maybe it does do the job. Change-Id: I17dc1e33bd0f20707adfbf9ad925251ac9aa77a5 Reviewed-on: https://cl.snix.dev/c/snix/+/30171 Autosubmit: Florian Klink <flokli@flokli.de> Reviewed-by: Ryan Lahfa <masterancpp@gmail.com> Tested-by: besadii
This commit is contained in:
parent
d07107d688
commit
91c752549c
1 changed files with 3 additions and 6 deletions
|
|
@ -27,12 +27,6 @@ in
|
||||||
};
|
};
|
||||||
};
|
};
|
||||||
|
|
||||||
# Put builds in /var/tmp as it can be quite big and would cause spurious
|
|
||||||
# failures from time to time: https://git.snix.dev/snix/snix/issues/82
|
|
||||||
systemd.services.nix-daemon.serviceConfig.Environment = [
|
|
||||||
"TMPDIR=/var/tmp"
|
|
||||||
];
|
|
||||||
|
|
||||||
services.depot.buildkite = {
|
services.depot.buildkite = {
|
||||||
enable = true;
|
enable = true;
|
||||||
agentCount = 32;
|
agentCount = 32;
|
||||||
|
|
@ -43,6 +37,9 @@ in
|
||||||
system.switch.enableNg = false;
|
system.switch.enableNg = false;
|
||||||
nix.nrBuildUsers = 256;
|
nix.nrBuildUsers = 256;
|
||||||
nix.settings.max-jobs = 64;
|
nix.settings.max-jobs = 64;
|
||||||
|
# Put builds in /var/tmp as it can be quite big and would cause spurious
|
||||||
|
# failures from time to time: https://git.snix.dev/snix/snix/issues/82
|
||||||
|
nix.settings.build-dir = "/var/tmp";
|
||||||
|
|
||||||
networking = {
|
networking = {
|
||||||
useNetworkd = true;
|
useNetworkd = true;
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue