From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>,
Bin Meng <bin.meng@windriver.com>
Cc: qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Simon Glass" <sjg@chromium.org>,
"Thomas Huth" <thuth@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Paweł Poławski" <ppolawsk@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Palmer Dabbelt" <palmer@rivosinc.com>
Subject: Re: [PATCH-for-8.0] gitlab-ci: Remove job building EDK2 firmware binaries
Date: Fri, 10 Mar 2023 14:49:19 +0100 [thread overview]
Message-ID: <03a66cae-4822-7cd2-8dd3-106e8b3f4334@linaro.org> (raw)
In-Reply-To: <CAFEAcA8hDiWBXPhKmo=AsS5wfu8wKf2YbxwF4p7xRSWrCW4xEg@mail.gmail.com>
On 10/3/23 14:38, Peter Maydell wrote:
> On Fri, 10 Mar 2023 at 13:33, Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
>>
>> When we introduced this Gitlab-CI job in commit 71920809ce
>> ("gitlab-ci.yml: Add jobs to build EDK2 firmware binaries"),
>> the naive plan was to have reproducible binaries by downloading
>> what this job would build, testing it and eventually committing
>> it. With retrospective, nothing happened 3 years later and this
>> job is just bitrotting:
>>
>> Step 1/3 : FROM ubuntu:18.04
>> 18.04: Pulling from library/ubuntu
>> mediaType in manifest should be
>> 'application/vnd.docker.distribution.manifest.v2+json' not
>> 'application/vnd.oci.image.manifest.v1+json'
>>
>> Remove this job to avoid wasting maintenance and CI ressources.
>
> Does the same thing hold for the opensbi job ?
Cc'ing Bin, I have no idea.
next prev parent reply other threads:[~2023-03-10 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 13:32 [PATCH-for-8.0] gitlab-ci: Remove job building EDK2 firmware binaries Philippe Mathieu-Daudé
2023-03-10 13:38 ` Peter Maydell
2023-03-10 13:49 ` Philippe Mathieu-Daudé [this message]
2023-03-13 2:09 ` Bin Meng
2023-03-13 8:51 ` Philippe Mathieu-Daudé
2023-03-13 9:35 ` Bin Meng
2023-03-13 10:01 ` Philippe Mathieu-Daudé
2023-03-13 10:08 ` Bin Meng
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=03a66cae-4822-7cd2-8dd3-106e8b3f4334@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=bin.meng@windriver.com \
--cc=bleal@redhat.com \
--cc=kraxel@redhat.com \
--cc=palmer@rivosinc.com \
--cc=peter.maydell@linaro.org \
--cc=ppolawsk@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sjg@chromium.org \
--cc=thuth@redhat.com \
--cc=wainersm@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).