forked from lix-project/nix-eval-jobs
README: add check-cache-status and nixpkgs evaluation examples
This commit is contained in:
parent
280de12085
commit
8ef37192bd
14
README.md
14
README.md
|
@ -110,6 +110,20 @@ latest release branch.
|
||||||
|
|
||||||
## FAQ
|
## FAQ
|
||||||
|
|
||||||
|
### How can I check if my package already have been uploaded in the binary cache?
|
||||||
|
|
||||||
|
If you provide the `--check-cache-status`, the json will contain a `"isCached"`
|
||||||
|
key in its json, that is true or false based on the status.
|
||||||
|
|
||||||
|
### How can I evaluate nixpkgs?
|
||||||
|
|
||||||
|
If you want to evaluate nixpkgs in the same way
|
||||||
|
[hydra](https://hydra.nixos.org/) does it, use this snippet:
|
||||||
|
|
||||||
|
```console
|
||||||
|
$ nix-eval-jobs --force-recurse pkgs/top-level/release.nix
|
||||||
|
```
|
||||||
|
|
||||||
### nix-eval-jobs consumes too much memory / is too slow
|
### nix-eval-jobs consumes too much memory / is too slow
|
||||||
|
|
||||||
By default, nix-eval-jobs spawns as many worker processes as there are hardware
|
By default, nix-eval-jobs spawns as many worker processes as there are hardware
|
||||||
|
|
Loading…
Reference in a new issue