Move nix-eval-jobs from nix-community to NixOS

[Mic92]

Since hydra now depends on it, it only make sense if ownership goes back to the NixOS org.
I would continue to maintain it, but also like to give the Nix/hydra team a say in this project (which I am also both part of).

cc @NixOS/nix-team @NixOS/hydra-maintainers

[roberth]

👍
Makes sense, and could be described as inevitable.

Let's do it decisively. Questions:

• Will the nix team or hydra team own this? Or should a new team be formed? (I suspect not, but correct me)
• Can nix-eval-jobs be integrated into Nix?
• Is the project in good shape?

[Ericson2314]

1. It could be co-owned by both teams. I don't really care. (Why would I care? I'll be on both teams :))
2. I'm open to that.
3. Yes. @Mic92 has done a good job. I've helped out with bumping to lastest nix version for Hydra too.

[xokdvium]

Can nix-eval-jobs be integrated into Nix?

As a useful data point, Lix has also done that and it seems to be working out well.

We could do that too and that should make the maintenance quite a bit easier in the long run. I'm not sure how we could have infra team co-own that too. Maybe separate owners with commit bit to the nix repo?

[dasJ]

No spoilers, please. There is no Hydra team ;)

On that note, I think that bringing it closer to Nix (maybe even into the codebase) while providing a CLI interface for Hydra and friends (buildbot-nix?) is the more logical thing to do since this will allow us (Hydra) to not bother with C++ anymore

[zowoq]

@Mic92 Currently nix-eval-jobs is using the community buildbot for CI, do you want to continue using it or switch to different CI?

I'd need to make the github app public and update the allowlist after the repo is moved if you want to continue using the community buildbot.

[Mic92]

Can nix-eval-jobs be integrated into Nix?

As a useful data point, Lix has also done that and it seems to be working out well.

We could do that too and that should make the maintenance quite a bit easier in the long run. I'm not sure how we could have infra team co-own that too. Maybe separate owners with commit bit to the nix repo?

I think moving the repo would be a good first step to discuss this integration. Merging is definitely an option, but I also don't want to put to much of a burden on the Nix CI that is currently already taking quiet a while to run. Maybe there is a way to make that faster first before adding more tests to it.

[Mic92]

@Mic92 Currently nix-eval-jobs is using the community buildbot for CI, do you want to continue using it or switch to different CI?

I prefer switching to a different CI.