From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 2/2] gitlab-ci: add Rust-enabled CI job
Date: Mon, 7 Oct 2024 19:13:55 +0100 [thread overview]
Message-ID: <ZwQk4ziQmBLtn8yS@redhat.com> (raw)
In-Reply-To: <20241007171717.1436982-3-pbonzini@redhat.com>
On Mon, Oct 07, 2024 at 07:17:13PM +0200, Paolo Bonzini wrote:
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> .gitlab-ci.d/buildtest.yml | 13 +++++++++++++
> .gitlab-ci.d/containers.yml | 6 ++++++
> 2 files changed, 19 insertions(+)
>
> diff --git a/.gitlab-ci.d/buildtest.yml b/.gitlab-ci.d/buildtest.yml
> index 669c980c4b4..a92e731d6af 100644
> --- a/.gitlab-ci.d/buildtest.yml
> +++ b/.gitlab-ci.d/buildtest.yml
> @@ -120,6 +120,19 @@ build-system-fedora:
> xtensa-softmmu m68k-softmmu riscv32-softmmu ppc-softmmu sparc64-softmmu
> MAKE_CHECK_ARGS: check-build
>
> +build-system-fedora-rust:
Add '-nightly' to the job name too, to match the container its
using.
> + extends:
> + - .native_build_job_template
> + - .native_build_artifact_template
> + needs:
> + job: amd64-fedora-rust-container
> + variables:
> + IMAGE: fedora-rust-nightly
> + CONFIGURE_ARGS: --disable-gcrypt --enable-nettle --disable-docs --enable-rust
You can leave out the crypt+nettle args and just let this
job auto-detect the right one
> + TARGETS: aarch64-softmmu
> + MAKE_CHECK_ARGS: check-build
> + allow_failure: true
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-10-07 18:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 17:17 [PATCH 0/2] dockerfiles, gitlab-ci: add CI job using nightly Rust Paolo Bonzini
2024-10-07 17:17 ` [PATCH 1/2] dockerfiles: add a Dockerfile using a nightly Rust toolchain Paolo Bonzini
2024-10-07 18:12 ` Daniel P. Berrangé
2024-10-07 17:17 ` [PATCH 2/2] gitlab-ci: add Rust-enabled CI job Paolo Bonzini
2024-10-07 18:13 ` Daniel P. Berrangé [this message]
2024-10-07 18:18 ` [PATCH 0/2] dockerfiles, gitlab-ci: add CI job using nightly Rust Daniel P. Berrangé
2024-10-08 9:03 ` Paolo Bonzini
2024-10-08 9:20 ` Daniel P. Berrangé
2024-10-08 9:45 ` Paolo Bonzini
2024-10-08 9:56 ` Daniel P. Berrangé
-- strict thread matches above, loose matches on Subject: below --
2024-10-09 9:01 Paolo Bonzini
2024-10-09 9:01 ` [PATCH 2/2] gitlab-ci: add Rust-enabled CI job Paolo Bonzini
2024-10-09 9:07 ` Daniel P. Berrangé
2024-10-09 12:55 ` Alex Bennée
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=ZwQk4ziQmBLtn8yS@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=manos.pitsidianakis@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).