Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New CI for NixOS infra/nix #542

Closed
Mic92 opened this issue Jan 29, 2025 · 5 comments
Closed

New CI for NixOS infra/nix #542

Mic92 opened this issue Jan 29, 2025 · 5 comments

Comments

@Mic92
Copy link
Member

Mic92 commented Jan 29, 2025

With the sunset of magic nix cache our CI will slow down both in the infra repo and the nix repo. Here a few options with decreasing preference.
Builds in both repos are not security relevant as we only test without using the resulting artifacts:

  1. Deploy buildbot on ofborg infra. Simon said there should be enough building capacity and it's just a matter of current priorities (time)
  2. Use nix-community build infra. Easy to setup and well maintained. People will probably argue against it with artificial reasons.
  3. Use GitHub runner with cachix or flakehub cache. This will be the slowest variant (needs to download from the cache all the time) also it requires only few changes in the existing ci integration. Also doesn't work for pull requests from outside the repo.

We could also do combinations of the above i.e start with 2 and move on to 1.

I currently use my own buildbot for the wiki infra and the merge-bot. Would be also cool to migrate that to something else.

@sedlund
Copy link
Member

sedlund commented Jan 29, 2025

For other lurkers that were not aware:
https://determinate.systems/posts/magic-nix-cache-free-tier-eol/

@zowoq
Copy link

zowoq commented Jan 31, 2025

Use nix-community build infra.

We want to keep our build infra (not just our cache) separate from the NixOS org until the legal issues surrounding distributing unfree packages are addressed.

@Mic92
Copy link
Member Author

Mic92 commented Jan 31, 2025

@zowoq could you clarify who "we" is?

@Mic92
Copy link
Member Author

Mic92 commented Jan 31, 2025

Since we are out of time, I went for cachix. I talked to the people working on ofborg and they still need some time. At the time, only I have administrative access to the cache. I requested org access to fix that: #544

@Mic92
Copy link
Member Author

Mic92 commented Jan 31, 2025

Follow up NixOS/org#65

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants