azure: Move to vs2017-win2016 platform build host
RFC 1/1 azure: Move to vs2017-win2016 platform build host
Azure is moving to remove the vs2015-win2012r2 platform build host. The two suggested new platforms to use are vs2017-win2016 and windows-2019. For now, move up to vs2017-win2016.
---
I'm sending this as RFC as it fails to build for i686 but builds for x86_64 and I'm out of my depth on fixing that. Can you please take a look Bin? Thanks!
--- .azure-pipelines.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
.azure-pipelines.yml +1 -1
@@ -1,5 +1,5 @@ variables: - windows_vm: vs2015-win2012r2 + windows_vm: vs2017-win2016 ubuntu_vm: ubuntu-18.04 ci_runner_image: trini/u-boot-gitlab-ci-runner:bionic-20200112-17Jan2020 # Add '-u 0' options for Azure pipelines, otherwise we get "permission
Signature · 1 line
2.17.1
Tom Rini <[email protected]> schrieb am Mo., 27. Jan. 2020, 22:23:
Quoted 11 lines
Azure is moving to remove the vs2015-win2012r2 platform build host. The two suggested new platforms to use are vs2017-win2016 and windows-2019. For now, move up to vs2017-win2016.
Cc Bin Meng <[email protected]>Signed-off-by Tom Rini <[email protected]>---
I'm sending this as RFC as it fails to build for i686 but builds forx86_64and I'm out of my depth on fixing that. Can you please take a look Bin? Thanks!
Is this build publicly available? I just failed to find it, having no experience with azure whatsoever...
Regards,
Simon
---
Quoted 18 lines
.azure-pipelines.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-).azure-pipelines.yml +1
-2@@ -1,5 +1,5 @@ variables: - windows_vm: vs2015-win2012r2 + windows_vm: vs2017-win2016 ubuntu_vm: ubuntu-18.04 ci_runner_image: trini/u-boot-gitlab-ci-runner:bionic-20200112-17Jan2020 # Add '-u 0' options for Azure pipelines, otherwise we get "permission --2.17.1
Quoted 14 lines · Simon Goldschmidt
Tom Rini <[email protected]> schrieb am Mo., 27. Jan. 2020, 22:23:
Quoted 11 lines
Azure is moving to remove the vs2015-win2012r2 platform build host. The two suggested new platforms to use are vs2017-win2016 and windows-2019. For now, move up to vs2017-win2016.
Cc Bin Meng <[email protected]>Signed-off-by Tom Rini <[email protected]>---
I'm sending this as RFC as it fails to build for i686 but builds forx86_64and I'm out of my depth on fixing that. Can you please take a look Bin? Thanks!
Quoted 2 lines
Is this build publicly available? I just failed to find it, having no experience with azure whatsoever...
Good question. I've had much less luck getting Azure stuff visible and linked to GitHub than Travis. But,
https://dev.azure.com/u-boot/u-boot/_build/results?buildId=232&view=logs&j=46ec4386-7228-5f2a-c0d8-953fe6fd5add&t=505270a7-c05a-5eb8-50bd-fd2d6c43911b
is the failure.
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200127/0645612a/attachment.sig>
Hi Simon,
Quoted 15 lines · Simon Goldschmidt
Tom Rini <[email protected]> schrieb am Mo., 27. Jan. 2020, 22:23:
Quoted 11 lines
Azure is moving to remove the vs2015-win2012r2 platform build host. The two suggested new platforms to use are vs2017-win2016 and windows-2019. For now, move up to vs2017-win2016.
Cc Bin Meng <[email protected]>Signed-off-by Tom Rini <[email protected]>---
I'm sending this as RFC as it fails to build for i686 but builds forx86_64and I'm out of my depth on fixing that. Can you please take a look Bin? Thanks!
Quoted 3 lines
Is this build publicly available? I just failed to find it, having no experience with azure whatsoever...
Yes it's publicly available and free service to open source projects.
You need a Microsoft account, and in your github account, search Azure pipelines from the github marketplace and install it to your github account.
It will prompt you to the Azure pipeline website and prompt you to log in using your Microsoft account. Follow the instructions then. Good luck.
Regards,
Bin
Hi Tom,
Quoted 11 lines · Tom Rini
Azure is moving to remove the vs2015-win2012r2 platform build host. The two suggested new platforms to use are vs2017-win2016 and windows-2019. For now, move up to vs2017-win2016.
Cc Bin Meng <[email protected]>Signed-off-by Tom Rini <[email protected]>---
I'm sending this as RFC as it fails to build for i686 but builds forx86_64and I'm out of my depth on fixing that. Can you please take a look Bin? Thanks!
I've looked at this issue. It was probably caused by the upstream MSYS2 Windows binary has not been updated to work with win2016 yet.
I tried this patch today, and the Windows host tools build looks goood. See:
https://dev.azure.com/bmeng/GitHub/_build/results?buildId=151&view=results
Quoted 9 lines
--- .azure-pipelines.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-).azure-pipelines.yml +0
-0
.azure-pipelines.yml
Quoted 7 lines
.azure-pipelines.yml +1
-2@@ -1,5 +1,5 @@ variables: - windows_vm: vs2015-win2012r2 + windows_vm: vs2017-win2016 ubuntu_vm: ubuntu-18.04 ci_runner_image: trini/u-boot-gitlab-ci-runner:bionic-20200112-17Jan2020 # Add '-u 0' options for Azure pipelines, otherwise we get "permission --
Regards,
Bin
Bin Meng
Tested-byQuoted 16 lines · Bin Meng
Hi Tom,
Quoted 11 lines · Tom Rini
Azure is moving to remove the vs2015-win2012r2 platform build host. The two suggested new platforms to use are vs2017-win2016 and windows-2019. For now, move up to vs2017-win2016.
Cc Bin Meng <[email protected]>Signed-off-by Tom Rini <[email protected]>---
I'm sending this as RFC as it fails to build for i686 but builds forx86_64and I'm out of my depth on fixing that. Can you please take a look Bin? Thanks!
Quoted 5 lines
I've looked at this issue. It was probably caused by the upstream MSYS2 Windows binary has not been updated to work with win2016 yet.
I tried this patch today, and the Windows host tools build looks goood. See:
https://dev.azure.com/bmeng/GitHub/_build/results?buildId=151&view=results
All Azure builds passed
I see this patch was assigned to me on patchwork, I will take this patch via the x86 tree.
Regards,
Bin
Quoted 24 lines · Bin Meng
Quoted 16 lines · Bin Meng
Hi Tom,
Quoted 11 lines · Tom Rini
Azure is moving to remove the vs2015-win2012r2 platform build host. The two suggested new platforms to use are vs2017-win2016 and windows-2019. For now, move up to vs2017-win2016.
Cc Bin Meng <[email protected]>Signed-off-by Tom Rini <[email protected]>---
I'm sending this as RFC as it fails to build for i686 but builds forx86_64and I'm out of my depth on fixing that. Can you please take a look Bin? Thanks!Quoted 5 lines
I've looked at this issue. It was probably caused by the upstream MSYS2 Windows binary has not been updated to work with win2016 yet.
I tried this patch today, and the Windows host tools build looks goood. See:
https://dev.azure.com/bmeng/GitHub/_build/results?buildId=151&view=results
Quoted 6 lines
All Azure builds passed
Tested-by Bin Meng <[email protected]>I see this patch was assigned to me on patchwork, I will take this patch via the x86 tree.
applied to u-boot-x86, thanks!