You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some derivations use limited hardware resources, such as KVM in NixOS tests.
It would be great if there was a way to limit the max-jobs used for derivations that require these resources, so that conflicts can be avoided.
Proposed solution
An derivation attribute could be added, containing a list of "resource names" that a derivation requires. Then, in nix-conf, the maximum number of concurrent builds for derivations that need each resource can be defined.
Alternative solutions
max-jobs can be set globally while building such derivations, but this prevents their dependencies from building concurrently too, which isn't ideal.
Is your feature request related to a problem?
Some derivations use limited hardware resources, such as KVM in NixOS tests.
It would be great if there was a way to limit the
max-jobs
used for derivations that require these resources, so that conflicts can be avoided.Proposed solution
An derivation attribute could be added, containing a list of "resource names" that a derivation requires. Then, in
nix-conf
, the maximum number of concurrent builds for derivations that need each resource can be defined.Alternative solutions
max-jobs
can be set globally while building such derivations, but this prevents their dependencies from building concurrently too, which isn't ideal.Additional context
Checklist
Add 👍 to issues you find important.
The text was updated successfully, but these errors were encountered: