- Dresden
- https://spaceboyz.net/~astro/
- Joined on
2019-04-18
artiq-full.nix: use sinaraSystemsSrc just as build input
Interesting. I have no experience publishing channels.
Updated.
2469638fd0
artiq-full.nix: copy <sinaraSystemsSrc> into generatedNix
6c954f9387
artiq-full.nix: use sinaraSystemsSrc just as build input
artiq-full.nix: use sinaraSystemsSrc just as build input
6cd9176433
hydra/artiq.json: use my fork
77fb07f37b
artiq-full: split code generation into artiq-board-generated jobset
b810407aa9
artiq: move stable to nixpkgs 20.09
e39f359122
bump sipyco
049de83093
artiq-full: build hw3
gitea notification token syntax
Keeping it authorization
was my oversight in #13. I am sorry for delivering broken code.
In the GithubStatus plugin the authorization
key's value is copied as-is into the HTTP header…
hydra: add patch for, configure giteastatus plugin
e94fc3ea85
hydra: add patch for, configure giteastatus plugin
a145decd12
hydra: add patch for, configure giteastatus plugin
a145decd12
hydra: add patch for, configure giteastatus plugin
6ef06b5d0b
nixops: open port 6000 on rpi2
169876e211
nixbld: add account creation note to gitea signin page
b03087717a
nixops: rpi-5 server (WIP)
7cf7847a81
nixops: add creotech to experimental users
copies of sinara-systems are needlessly installed
extras
would have to be moved out of generatedNix
(which uses sinaraSystemsSrc
before generating the $out/default.nix
).
Still thinking about solutions...
report build results in Git web interfaces
GiteaStatus plugin upstream PR: https://github.com/NixOS/hydra/pull/849
Would you like this as an additional patch for the hydra config in it-infra?
hydra evaluations are slow
(Issue pertains to artiq-full)
It's a consequence of our changes to avoid repeated Vivado runs. (#1)
For Nix to know what inputs to build, it now has to generate Cargo and Vivado input for each…