From: Finn Behrens <me@kloenk.de>
To: rust-for-linux@vger.kernel.org
Cc: linux@petabyte.dev, Joerg Thalheim <joerg@thalheim.io>
Subject: Rust-for-Linux Hydra CI
Date: Fri, 16 Apr 2021 10:27:56 +0200 [thread overview]
Message-ID: <04861911-1275-449E-BE54-C6871B53F4A3@kloenk.de> (raw)
[-- 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 --]
next reply other threads:[~2021-04-16 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 8:27 Finn Behrens [this message]
2021-04-16 12:48 ` Rust-for-Linux Hydra CI Christine Dodrill
2021-04-16 13:00 ` Miguel Ojeda
2021-04-16 13:07 ` Finn Behrens
2021-04-16 13:09 ` Christine Dodrill
2021-04-16 13:12 ` Finn Behrens
2021-04-16 13:22 ` Miguel Ojeda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=04861911-1275-449E-BE54-C6871B53F4A3@kloenk.de \
--to=me@kloenk.de \
--cc=joerg@thalheim.io \
--cc=linux@petabyte.dev \
--cc=rust-for-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).