Skip to contentSkip to conversation

Azure CI: Drop Windows host tools builds

PATCH In review Tom Rini 2 participants 4 messages May 15 – Jul 26

lore
Share & tools
lore

Tom Rini

author
#0 lore raw

PATCH 1/1 Azure CI: Drop Windows host tools builds

In preparation for being able to support more recent OpenSSL versions, we need to add support for the OpenSSL Provider API. This in turn isn't something that MSYS has all of the required packages to support. Given a lack of user feedback that these tools are still used in this manner, remove Windows host tool builds from CI.

---
This is intended for the next branch, and to allow for a more visible part of the removal to be made now. This means v2026.07 will be the last version to support MSYS for host tool builds.

---
 .azure-pipelines.yml | 28 ----------------------------
 1 file changed, 28 deletions(-)
.azure-pipelines.yml +0 -28
index 4417ef4e5a50..b2a59bafa83d 100644
@@ -1,5 +1,4 @@
 variables:
-  windows_vm: windows-2022
   ubuntu_vm: ubuntu-24.04
   macos_vm: macOS-14
   ci_runner_image: trini/u-boot-gitlab-ci-runner:noble-20251013-23Jan2026
@@ -44,33 +43,6 @@ variables:
 stages:
 - stage: testsuites
   jobs:
-  - job: tools_only_windows
-    displayName: 'Ensure host tools build for Windows'
-    pool:
-      vmImage: $(windows_vm)
-    steps:
-      - powershell: |
-          (New-Object Net.WebClient).DownloadFile("https://github.com/msys2/msys2-installer/releases/download/2021-06-04/msys2-base-x86_64-20210604.sfx.exe", "sfx.exe")
-        displayName: 'Install MSYS2'
-      - script: |
-          sfx.exe -y -o%CD:~0,2%\
-          %CD:~0,2%\msys64\usr\bin\bash -lc " "
-          %CD:~0,2%\msys64\usr\bin\bash -lc "pacman --noconfirm -Syuu"
-          %CD:~0,2%\msys64\usr\bin\bash -lc "pacman --noconfirm -Syuu"
-        displayName: 'Update MSYS2'
-      - script: |
-          %CD:~0,2%\msys64\usr\bin\bash -lc "pacman --noconfirm --needed -Sy make gcc bison flex diffutils openssl-devel libgnutls-devel libutil-linux-devel"
-        displayName: 'Install Toolchain'
-      - script: |
-          echo make tools-only_defconfig tools-only > build-tools.sh
-          %CD:~0,2%\msys64\usr\bin\bash -lc "bash build-tools.sh"
-        displayName: 'Build Host Tools'
-        env:
-          # Tell MSYS2 we need a POSIX emulation layer
-          MSYSTEM: MSYS
-          # Tell MSYS2 not to ‘cd’ our startup directory to HOME
-          CHERE_INVOKING: yes
-
   - job: tools_only_macOS
     displayName: 'Ensure host tools build for macOS X'
     pool:
Signature · 1 line
2.43.0
Reviewed-by on v1 1/1
#1 lore raw

Hi Tom,

Quoted 62 lines · Tom Rini

In preparation for being able to support more recent OpenSSL versions, we need to add support for the OpenSSL Provider API. This in turn isn't something that MSYS has all of the required packages to support. Given a lack of user feedback that these tools are still used in this manner, remove Windows host tool builds from CI.

---
This is intended for the next branch, and to allow for a more visible part of the removal to be made now. This means v2026.07 will be the last version to support MSYS for host tool builds.

---
 .azure-pipelines.yml | 28 ----------------------------
 1 file changed, 28 deletions(-)
.azure-pipelines.yml +0 -29
index 4417ef4e5a50..b2a59bafa83d 100644
@@ -1,5 +1,4 @@
 variables:
-  windows_vm: windows-2022
   ubuntu_vm: ubuntu-24.04
   macos_vm: macOS-14
   ci_runner_image: trini/u-boot-gitlab-ci-runner:noble-20251013-23Jan2026
@@ -44,33 +43,6 @@ variables:
 stages:
 - stage: testsuites
   jobs:
-  - job: tools_only_windows
-    displayName: 'Ensure host tools build for Windows'
-    pool:
-      vmImage: $(windows_vm)
-    steps:
-      - powershell: |
-          (New-Object Net.WebClient).DownloadFile("https://github.com/msys2/msys2-installer/releases/download/2021-06-04/msys2-base-x86_64-20210604.sfx.exe", "sfx.exe")
-        displayName: 'Install MSYS2'
-      - script: |
-          sfx.exe -y -o%CD:~0,2%\
-          %CD:~0,2%\msys64\usr\bin\bash -lc " "
-          %CD:~0,2%\msys64\usr\bin\bash -lc "pacman --noconfirm -Syuu"
-          %CD:~0,2%\msys64\usr\bin\bash -lc "pacman --noconfirm -Syuu"
-        displayName: 'Update MSYS2'
-      - script: |
-          %CD:~0,2%\msys64\usr\bin\bash -lc "pacman --noconfirm --needed -Sy make gcc bison flex diffutils openssl-devel libgnutls-devel libutil-linux-devel"
-        displayName: 'Install Toolchain'
-      - script: |
-          echo make tools-only_defconfig tools-only > build-tools.sh
-          %CD:~0,2%\msys64\usr\bin\bash -lc "bash build-tools.sh"
-        displayName: 'Build Host Tools'
-        env:
-          # Tell MSYS2 we need a POSIX emulation layer
-          MSYSTEM: MSYS
-          # Tell MSYS2 not to ‘cd’ our startup directory to HOME
-          CHERE_INVOKING: yes
-
   - job: tools_only_macOS
     displayName: 'Ensure host tools build for macOS X'
     pool:
--
Quoted 2 lines

2.43.0

How should we document this use of WSL to run the tools on Windows?

Regards,
Simon

author
#2 lore raw
Quoted 70 lines · Simon Glass

Hi Tom,

Quoted 62 lines · Tom Rini

In preparation for being able to support more recent OpenSSL versions, we need to add support for the OpenSSL Provider API. This in turn isn't something that MSYS has all of the required packages to support. Given a lack of user feedback that these tools are still used in this manner, remove Windows host tool builds from CI.

---
This is intended for the next branch, and to allow for a more visible part of the removal to be made now. This means v2026.07 will be the last version to support MSYS for host tool builds.

---
 .azure-pipelines.yml | 28 ----------------------------
 1 file changed, 28 deletions(-)
.azure-pipelines.yml +0 -29
index 4417ef4e5a50..b2a59bafa83d 100644
@@ -1,5 +1,4 @@
 variables:
-  windows_vm: windows-2022
   ubuntu_vm: ubuntu-24.04
   macos_vm: macOS-14
   ci_runner_image: trini/u-boot-gitlab-ci-runner:noble-20251013-23Jan2026
@@ -44,33 +43,6 @@ variables:
 stages:
 - stage: testsuites
   jobs:
-  - job: tools_only_windows
-    displayName: 'Ensure host tools build for Windows'
-    pool:
-      vmImage: $(windows_vm)
-    steps:
-      - powershell: |
-          (New-Object Net.WebClient).DownloadFile("https://github.com/msys2/msys2-installer/releases/download/2021-06-04/msys2-base-x86_64-20210604.sfx.exe", "sfx.exe")
-        displayName: 'Install MSYS2'
-      - script: |
-          sfx.exe -y -o%CD:~0,2%\
-          %CD:~0,2%\msys64\usr\bin\bash -lc " "
-          %CD:~0,2%\msys64\usr\bin\bash -lc "pacman --noconfirm -Syuu"
-          %CD:~0,2%\msys64\usr\bin\bash -lc "pacman --noconfirm -Syuu"
-        displayName: 'Update MSYS2'
-      - script: |
-          %CD:~0,2%\msys64\usr\bin\bash -lc "pacman --noconfirm --needed -Sy make gcc bison flex diffutils openssl-devel libgnutls-devel libutil-linux-devel"
-        displayName: 'Install Toolchain'
-      - script: |
-          echo make tools-only_defconfig tools-only > build-tools.sh
-          %CD:~0,2%\msys64\usr\bin\bash -lc "bash build-tools.sh"
-        displayName: 'Build Host Tools'
-        env:
-          # Tell MSYS2 we need a POSIX emulation layer
-          MSYSTEM: MSYS
-          # Tell MSYS2 not to ‘cd’ our startup directory to HOME
-          CHERE_INVOKING: yes
-
   - job: tools_only_macOS
     displayName: 'Ensure host tools build for macOS X'
     pool:
--
Quoted 2 lines

2.43.0

Quoted 1 line

How should we document this use of WSL to run the tools on Windows?

I suppose the bit about WSL that many of the TI platforms have copy/pasted could be moved up to a more generic location.

Signature · 1 line
Tom
author
#3 lore raw
In reply to Tom Rini
Quoted 8 lines · Tom Rini

In preparation for being able to support more recent OpenSSL versions, we need to add support for the OpenSSL Provider API. This in turn isn't something that MSYS has all of the required packages to support. Given a lack of user feedback that these tools are still used in this manner, remove Windows host tool builds from CI.

[...]

Applied to u-boot/main, thanks!

[1/1] Azure CI: Drop Windows host tools builds

      commit: d99ad807509dcb7197a33261a269b5144e5e4acc
Signature · 1 line
Tom