From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Wainer dos Santos Moschetta <wainersm@redhat.com>, qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Willian Rampazzo" <willianr@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH v2 2/2] gitlab-ci: Add a job to build virtiofsd standalone
Date: Thu, 29 Apr 2021 15:22:13 +0200 [thread overview]
Message-ID: <a19827af-7300-bb04-4124-a54f409b42aa@redhat.com> (raw)
In-Reply-To: <d64aa1d2-6fc3-4c4b-fa0d-2f3721ab7e9a@redhat.com>
On 4/29/21 3:16 PM, Wainer dos Santos Moschetta wrote:
> Hi,
>
> On 4/29/21 5:33 AM, Philippe Mathieu-Daudé wrote:
>> Add a job which builds virtiofsd without any emulation or tool.
>>
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> ---
>> https://gitlab.com/philmd/qemu/-/jobs/1222007991
>> Duration: 7 minutes 48 seconds
>> ---
>> .gitlab-ci.yml | 13 +++++++++++++
>> 1 file changed, 13 insertions(+)
>>
>> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
>> index 52d65d6c04f..ba3c7ade6ca 100644
>> --- a/.gitlab-ci.yml
>> +++ b/.gitlab-ci.yml
>> @@ -800,6 +800,19 @@ build-libvhost-user:
>> - meson
>> - ninja
>> +build-virtiofsd-fedora:
>> + <<: *native_build_job_definition
>> + needs:
>> + job: amd64-fedora-container
>> + variables:
>> + IMAGE: fedora
>> + CONFIGURE_ARGS: --enable-virtiofsd
>> + --disable-system --disable-user --disable-tools --disable-docs
>> + artifacts:
>> + expire_in: 2 days
>> + paths:
>> + - build/tools/virtiofsd/virtiofsd
>> +
>
> Why it needs the executable archived?
I assumed if there were testing jobs as next stage, this is what they
would consume? I copy/pasted from another job and adapted, but you are
right, it is pointless. AnyhowI understood this job has been discarded
during review.
Thanks for having a look!
Phil.
prev parent reply other threads:[~2021-04-29 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 8:33 [PATCH v2 0/2] virtiofsd: Meson build fix Philippe Mathieu-Daudé
2021-04-29 8:33 ` [PATCH v2 1/2] meson: Select 'have_system' when virtiofsd is enabled Philippe Mathieu-Daudé
2021-04-29 8:44 ` Peter Maydell
2021-04-30 7:45 ` Paolo Bonzini
2021-04-29 13:50 ` Connor Kuehl
2021-04-29 15:15 ` Philippe Mathieu-Daudé
2021-04-29 15:18 ` Dr. David Alan Gilbert
2021-04-29 8:33 ` [PATCH v2 2/2] gitlab-ci: Add a job to build virtiofsd standalone Philippe Mathieu-Daudé
2021-04-29 8:43 ` Daniel P. Berrangé
2021-04-29 9:41 ` Philippe Mathieu-Daudé
2021-04-29 13:16 ` Wainer dos Santos Moschetta
2021-04-29 13:22 ` Philippe Mathieu-Daudé [this message]
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=a19827af-7300-bb04-4124-a54f409b42aa@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=dgilbert@redhat.com \
--cc=f4bug@amsat.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=willianr@redhat.com \
/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).