From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: devel@edk2.groups.io
Cc: Sean Brogan <sean.brogan@microsoft.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Andrew Fish <afish@apple.com>, Ray Ni <ray.ni@intel.com>,
Abner Chang <abner.chang@hpe.com>,
Nickle Wang <nickle.wang@hpe.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: [PATCH v2 0/5] Use windows-2019 VM Image
Date: Fri, 1 Apr 2022 21:31:51 -0400 [thread overview]
Message-ID: <20220402013156.2640-1-mikuback@linux.microsoft.com> (raw)
From: Michael Kubacki <michael.kubacki@microsoft.com>
REF:https://bugzilla.tianocore.org/show_bug.cgi?id=3890
REF:https://bugzilla.tianocore.org/show_bug.cgi?id=3891
Pipelines are currently building against VS2019 and use the
"windows-latest" VM image in Azure Pipelines. The "windows-latest"
image recently moved its toolchain to VS2022, so VS2019 is no
longer found.
To immediately address the issue with no change in build behavior,
this series updates YAML files in the repository using
"windows-latest" to "windows-2019".
V2 Changes:
Introduces additional changes to get pipelines back working
in addition to the original windows-2019 change originally
scoped for the patch series.
1. Add patch v2 [1/5] to use Python 3.8 to work around an issue
when updating a tar file web_dependency.
2. Add patch v2 [5/5] to update the GCC ARM compiler.
Cc: Sean Brogan <sean.brogan@microsoft.com>
Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Cc: Andrew Fish <afish@apple.com>
Cc: Ray Ni <ray.ni@intel.com>
Cc: Abner Chang <abner.chang@hpe.com>
Cc: Nickle Wang <nickle.wang@hpe.com>
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Michael Kubacki (5):
.azurepipelines: Use Python 3.8
.azurepipelines: Use windows-2019 VM image
EmulatorPkg: Use windows-2019 VM image
OvmfPkg: Use windows-2019 VM image
BaseTools/Bin: Update GCC ARM compiler version
.azurepipelines/Ubuntu-PatchCheck.yml | 2 +-
.azurepipelines/Windows-VS2019.yml | 2 +-
.azurepipelines/templates/platform-build-run-steps.yml | 2 +-
.azurepipelines/templates/pr-gate-steps.yml | 2 +-
BaseTools/Bin/gcc_aarch64_linux_ext_dep.yaml | 8 ++++----
BaseTools/Bin/gcc_arm_linux_ext_dep.yaml | 8 ++++----
EmulatorPkg/PlatformCI/.azurepipelines/Windows-VS2019.yml | 2 +-
OvmfPkg/PlatformCI/.azurepipelines/Windows-VS2019.yml | 2 +-
8 files changed, 14 insertions(+), 14 deletions(-)
--
2.28.0.windows.1
next reply other threads:[~2022-04-02 1:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 1:31 Michael Kubacki [this message]
2022-04-02 1:31 ` [PATCH v2 1/5] .azurepipelines: Use Python 3.8 Michael Kubacki
2022-04-02 1:31 ` [PATCH v2 2/5] .azurepipelines: Use windows-2019 VM image Michael Kubacki
2022-04-02 1:31 ` [PATCH v2 3/5] EmulatorPkg: " Michael Kubacki
2022-04-02 1:31 ` [PATCH v2 4/5] OvmfPkg: " Michael Kubacki
2022-04-02 1:31 ` [PATCH v2 5/5] BaseTools/Bin: Update GCC ARM compiler version Michael Kubacki
2022-04-02 1:36 ` [edk2-devel] [PATCH v2 0/5] Use windows-2019 VM Image Sean
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-list 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=20220402013156.2640-1-mikuback@linux.microsoft.com \
--to=devel@edk2.groups.io \
/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