Rust-for-Linux Hydra CI

Rust-for-Linux Hydra CI

[Finn Behrens]

[-- Attachment #1: Type: text/plain, Size: 943 bytes --]

Howdy,

The nix-community gave me access to the nix-community hydra. Hydra is the CI tool written for nix builds, and so builds the rust-for-linux tree with nix. The hydra is checking the GitHub rust-for-linux/linux repo for new commits, and then builds these in a nix context (If we want to move to git.kernel.org, hydra can also check there for new commits).

The latest builds can be seen here: https://hydra.nix-community.org/jobset/rust-for-linux/rust and is also uploaded to the nix cache at https://app.cachix.org/cache/nix-community (local nix versions can use those caches to substitute builds, e.g. rustc-nightly)

We could also add vm tests via nixos, and documentation is not generated currently, but if we write nix derivations for that, hydra could also deliver those for download.



CU,
Finn

PS: I’m not sure If this will break if we rebase to a newer linux version, as nix needs a version to find some files.

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: Rust-for-Linux Hydra CI

[Christine Dodrill]

I have been working on implementing a kernel driver in Rust to learn
how to do it and I have a NixOS test for it in case you want to use it
as a starting point: https://github.com/Xe/dev-printerfact-on-nixos.


On Fri, Apr 16, 2021 at 4:33 AM Finn Behrens <me@kloenk.de> wrote:
>
> Howdy,
>
> The nix-community gave me access to the nix-community hydra. Hydra is the CI tool written for nix builds, and so builds the rust-for-linux tree with nix. The hydra is checking the GitHub rust-for-linux/linux repo for new commits, and then builds these in a nix context (If we want to move to git.kernel.org, hydra can also check there for new commits).
>
> The latest builds can be seen here: https://hydra.nix-community.org/jobset/rust-for-linux/rust and is also uploaded to the nix cache at https://app.cachix.org/cache/nix-community (local nix versions can use those caches to substitute builds, e.g. rustc-nightly)
>
> We could also add vm tests via nixos, and documentation is not generated currently, but if we write nix derivations for that, hydra could also deliver those for download.
>
>
>
> CU,
> Finn
>
> PS: I’m not sure If this will break if we rebase to a newer linux version, as nix needs a version to find some files.



-- 
Christine Dodrill
me@christine.website

.i la budza pu cusku lu
 <<.i ko snura .i ko kanro
   .i ko panpi .i ko gleki

Re: Rust-for-Linux Hydra CI

[Miguel Ojeda]

Hi Finn,

On Fri, Apr 16, 2021 at 10:44 AM Finn Behrens <me@kloenk.de> wrote:
>
> The nix-community gave me access to the nix-community hydra. Hydra is the CI tool written for nix builds, and so builds the rust-for-linux tree with nix. The hydra is checking the GitHub rust-for-linux/linux repo for new commits, and then builds these in a nix context (If we want to move to git.kernel.org, hydra can also check there for new commits).
>
> The latest builds can be seen here: https://hydra.nix-community.org/jobset/rust-for-linux/rust and is also uploaded to the nix cache at https://app.cachix.org/cache/nix-community (local nix versions can use those caches to substitute builds, e.g. rustc-nightly)
>
> We could also add vm tests via nixos, and documentation is not generated currently, but if we write nix derivations for that, hydra could also deliver those for download.

This is great! Thanks a lot for moving this forward!

> PS: I’m not sure If this will break if we rebase to a newer linux version, as nix needs a version to find some files.

If we rebase, does it affect negatively Hydra or some of the other
tools? i.e. would we be blocking some other project in some way? If it
is just us seeing a "red" state in the CI, then I think it is fine :)

Cheers,
Miguel

Re: Rust-for-Linux Hydra CI

[Finn Behrens]

Hi,

> On 16. Apr 2021, at 15:00, Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
> 
>> PS: I’m not sure If this will break if we rebase to a newer linux version, as nix needs a version to find some files.
> 
> If we rebase, does it affect negatively Hydra or some of the other
> tools? i.e. would we be blocking some other project in some way? If it
> is just us seeing a "red" state in the CI, then I think it is fine :)

I confirmed that rebasing breaks the build. But yes this is only a red state as the build fails, but it does not block anything. Ofcourse if we get around to build nixos-vm tests those tests are also blocked as there is no kernel that builds and so can be tested. But still, this is only a broken state, and does not affect any other projects.
We can also monitor different branches of the rust-for-linux linux tree, where a rebase in one branch would not affect another branch.

Maybe Christine want’s to add tests, the nix derivations are at https://github.com/rust-for-linux/nix and are automatically updated by hydra, as I should write my finals and not linux tests :-). 

CU,
Finn

Re: Rust-for-Linux Hydra CI

[Christine Dodrill]

I will see what I can get done after work today. I would just submit
the tests as a pull request, right?

On Fri, Apr 16, 2021 at 9:07 AM Finn Behrens <me@kloenk.de> wrote:
>
> Hi,
>
> > On 16. Apr 2021, at 15:00, Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
> >
> >> PS: I’m not sure If this will break if we rebase to a newer linux version, as nix needs a version to find some files.
> >
> > If we rebase, does it affect negatively Hydra or some of the other
> > tools? i.e. would we be blocking some other project in some way? If it
> > is just us seeing a "red" state in the CI, then I think it is fine :)
>
> I confirmed that rebasing breaks the build. But yes this is only a red state as the build fails, but it does not block anything. Ofcourse if we get around to build nixos-vm tests those tests are also blocked as there is no kernel that builds and so can be tested. But still, this is only a broken state, and does not affect any other projects.
> We can also monitor different branches of the rust-for-linux linux tree, where a rebase in one branch would not affect another branch.
>
> Maybe Christine want’s to add tests, the nix derivations are at https://github.com/rust-for-linux/nix and are automatically updated by hydra, as I should write my finals and not linux tests :-).
>
> CU,
> Finn



-- 
Christine Dodrill
me@christine.website

.i la budza pu cusku lu
 <<.i ko snura .i ko kanro
   .i ko panpi .i ko gleki

Re: Rust-for-Linux Hydra CI

[Finn Behrens]

> On 16. Apr 2021, at 15:09, Christine Dodrill <me@christine.website> wrote:
> 
> I will see what I can get done after work today. I would just submit
> the tests as a pull request, right?
> 
Yes, add it to the default.nix, so default.nix returns a package set, hydra evaluates this default.nix (giving it the latest input) and builds every package returned by that function.

CU,
Finn

Re: Rust-for-Linux Hydra CI

[Miguel Ojeda]

On Fri, Apr 16, 2021 at 3:07 PM Finn Behrens <me@kloenk.de> wrote:
>
> I confirmed that rebasing breaks the build. But yes this is only a red state as the build fails, but it does not block anything. Ofcourse if we get around to build nixos-vm tests those tests are also blocked as there is no kernel that builds and so can be tested. But still, this is only a broken state, and does not affect any other projects.
> We can also monitor different branches of the rust-for-linux linux tree, where a rebase in one branch would not affect another branch.

Sounds very good then.

> Maybe Christine want’s to add tests, the nix derivations are at https://github.com/rust-for-linux/nix and are automatically updated by hydra, as I should write my finals and not linux tests :-).

Good luck on your finals!

Cheers,
Miguel