Hydra | 377 Members | |
| 109 Servers |
| Sender | Message | Time |
|---|---|---|
| 30 Nov 2022 | ||
| 13:12:16 | ||
| 1 Dec 2022 | ||
I am setting up a Hydra instance, and I would like the jobs that produce deployment artifacts to not trigger deploys unless all checks have passed. It is easy enough to add all the checks to the buildInputs of the artifact jobs, but that causes a lot of spurious rebuilding. Is there a better way to achieve what I'm trying to do? | 00:29:14 | |
You're looking for an "aggregate" jobset. There are some examples in Nixpkgs, I believe (look for release.nix or similarly-named files in nixos/). Also present in the Nix (the tool) flake, and probably the Hydra flake / repo as well. | 00:40:14 | |
| * You're looking for an "aggregate" job. There are some examples in Nixpkgs, I believe (look for `release.nix` or similarly-named files in `nixos/`). Also present in the Nix (the tool) flake, and probably the Hydra flake / repo as well. | 00:40:40 | |
| Is it normal that my hydra queries narinfos from itself or did I mess something up? | 10:18:55 | |
| It will use any substituter, including itself if configured as substituter | 10:20:23 | |
| Do I want this or does that slow down things? I have the feeling that sometimes jobs just stale a longer time which may be related to that. | 10:21:05 | |
Also is warning: 7 concurrent database updates; PostgreSQL may be stalled normal? postgres itself seems to be happy. | 10:21:16 | |
In reply to @sandro:supersandro.deI don't think it makes any sense. It pushes the required store paths to builders anyway and substituting from itself will never yield any success | 10:21:38 | |
In reply to @sandro:supersandro.deThat's normal | 10:21:43 | |
In reply to @janne.hess:helsinki-systems.dethanks for clarifying. Then I can turn it off and maybe hydra gets going faster | 10:25:05 | |
| it feels usually a bit slow for running one concurrent build | 10:25:20 | |
| Would you recommend to increase narinfo-cache-negative-ttl when you rebuild from stage0? Would there be anything else you would suggest to set? | 11:17:37 | |
| maybe disable use of binary caches completely if you're doing that? | 11:18:00 | |
| I am only doing it for one job of 8 | 11:19:22 | |
In reply to @janne.hess:helsinki-systems.deby default, the builders do substitute tho. it's like nix-copy-close -s. | 12:35:08 | |
| 13:08:37 | ||
| 14:38:26 | ||
| How do I reset an error message like?
My hydra machines file looks like | 15:00:06 | |
| 3 Dec 2022 | ||
| does anybody want to take a look at https://github.com/NixOS/hydra/pull/1263? %) | 12:10:50 | |
| 4 Dec 2022 | ||
| 14:19:49 | ||
| 5 Dec 2022 | ||
In reply to @cole-h:matrix.orgThanks Cole, this does look like what I need. | 00:22:06 | |
What's the status of determinate's terraform hydra provider? I see a few open PRs and a latest commit on main from August - is it under active development internally, feature complete, something else? | 00:24:50 | |
In reply to @jackdk:matrix.org(This is my personal opinion, not that of my employer) I consider it fairly feature complete. 2 of the 3 draft PRs that touch the actual provider depend on upstream PRs being merged. That 3rd draft PR implements support for something that has been merged upstream, but I just never got around to finishing it 🤷 | 16:31:46 | |
| Thanks very much. | 21:42:28 | |
| 6 Dec 2022 | ||
| 12:16:07 | ||
| 14:10:23 | ||
| 7 Dec 2022 | ||
| 09:10:18 | ||
| 9 Dec 2022 | ||
| So, after fiddling around with containerized hydra on aarch64 server and trying to get it working as a builder (and not really getting anywhere with that), we decided to go for a hydra (master) running directly on ubuntu+nix without containers. All docs I have found so far talk about installation on x86 and nixos. Any pointers to docs about installation on ubuntu+nix and/or aarch64, would be appreciated. | 08:31:52 | |
In reply to @terwiz:matrix.orgThat sounds like a path of great resistance. I don't think anyone really does that :/ | 09:14:42 | |