| 3 Jan 2025 |
 emily | right, ouch. (but I guess at least it also increases what would be saved on the x86) | 17:16:48 |
 liberodark | The x86_64 builder will be ready in about 1 week.
For risc-v we would need more information, I have a few servers but for a builder it seems to me that we need a pioneer which is quite slow as standard.
But it's what works best at the moment. | 17:20:14 |
| emily | I think we probably don't have the sources as a community to give RISC-V higher tier support right now | 17:20:48 |
| emily | IIRC it was unclear whether any available RISC-V hardware could keep up with Hydra load and not drag down the other architectures right now | 17:21:09 |
| emily | and Hydra would definitely need multiple of the best RISC-V machines money can buy at the minimum | 17:21:44 |
 hexa | I'm totally paying for taxes as needed, given that the foundation basically uses the dutch state as a vehicle | 17:22:02 |
| hexa | * I'm totally pro paying for taxes as needed, given that the foundation basically uses the dutch state as a vehicle | 17:22:08 |
| hexa | and I have strong opinions on the implications of an 8% tax rate | 17:22:21 |
| hexa | liberodark: I generally trust K900's judgement on RISC-V, but at the same time it would be good to gauge performance. | 17:23:28 |
| liberodark | I allow myself a question if you want.
- ofborg is a rebot that helps to verify commits?
- nixos-community builder helps to build on the fly?
- hydra allows to check a specific state when a release is released?
| 17:24:21 |
| liberodark | I will give you access to a pioneer. | 17:25:13 |
| emily | Hydra builds everything users use, on both the stable and unstable branches | 17:25:18 |
| emily | the community builders are used by contributors to test builds | 17:25:29 |
| liberodark | * I will give you access to a pioneer. So that you can test it on your side. | 17:25:36 |
| emily | (while reviewing code or developing it themselves) | 17:25:38 |
| emily | ofborg temporarily doesn't exist, but usually provides automated builds across all platforms for pull requests before they're merged | 17:25:56 |
| liberodark | * I allow myself a question if you want.
- ofborg is a robot that helps to verify commits?
- nixos-community builder helps to build on the fly?
- hydra allows to check a specific state when a release is released?
| 17:26:00 |
| emily | community builders and ofborg have some overlap in use case, Hydra is the most critical thing | 17:26:09 |
| emily | (IIRC the AArch64 community builder was the same machine as the ofborg aarch64-linux builder? but I could be wrong) | 17:26:29 |
| hexa | Appreciated. | 17:26:40 |
| emily | notably ofborg and the community builders are "untrusted", many people can trigger builds on them and they are not considered secure | 17:26:57 |
| emily | Hydra is critical infrastructure, so few people have access to it and it does not trust builds from ofborg or the community builders at all | 17:27:19 |
| emily | Hydra only builds what is actually merged into branches, or things that people with sufficient Hydra permissions set up to be built (e.g. for wide-scale testing) | 17:27:43 |
| liberodark | I understand better, it's clearer and it answers my questions, thank you for your clarifications. emily | 17:28:12 |
 Grimmauld (moving to @grimmauld:grapevine.grimmauld.de) | I understand the community builder is there for community projects and build jobs too big to be feasible on local systems. What exactly are the typical requirements to get access? There have been a couple build jobs i ran so far that took a couple hours each on normal hardware, so far i decided to just build via github actions. But that can only go so far. And the documentation i could find all basically said "open a PR and see what happens", but that feels very spongy.
(For the record, i have other IRL obligations currently, so not relevant until maybe august, but figured i'd ask if the topic were community builders rn) | 21:42:56 |
 Gaétan Lepage | Well, according to me, you will be granted access if you show that you would use it to contribute to ...well, nix (community) projects.
Apart from this, I don't think like that there is hard requirements. | 21:45:14 |
| Gaétan Lepage | AFAIK, It's not really supposed to be used for personal stuff. | 21:45:36 |
| Grimmauld (moving to @grimmauld:grapevine.grimmauld.de) | specifically, i was compiling different linux kernels with different patches for various apparmor features. Those patches are a part of only ubuntu currently, but bringing them to nix would kinda require a builder for it to be any fun developing | 22:09:20 |
| emily | that seems plenty in-scope | 22:10:12 |
| emily | I think any builds you need to do in the course of contributing to Nixpkgs are fine (within the constraints of not hogging all the resources forever of course, but it's often pretty quiet on the boxes) | 22:10:42 |
