From 21591e4f6f77174b07ed19cfcc47cbb9ffae89ee Mon Sep 17 00:00:00 2001 From: Pietro Gagliardi Date: Sun, 7 Apr 2019 01:11:18 -0400 Subject: [PATCH] Hm, Chocolatey is being annoying... --- azure-pipelines/windows-setup-mingw.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/azure-pipelines/windows-setup-mingw.yml b/azure-pipelines/windows-setup-mingw.yml index d259a371..03e487c1 100644 --- a/azure-pipelines/windows-setup-mingw.yml +++ b/azure-pipelines/windows-setup-mingw.yml @@ -5,6 +5,9 @@ parameters: steps: - powershell: | + WriteError "$env:ChocolateyInstall" + dir "$env:ChocolateyInstall" | Write-Error + dir "$env:ChocolateyInstall\lib" | Write-Error $chocopath = where.exe choco.exe | Get-Item # apparently they didn't think to add this functionality from the start (multiple joins was only added in PowerShell 6 and Azure Pipelines is using 5.x), and the direct-CLR approach actually behaves differently (and I would need to check which version of .net Azure Pipelines is using anyway, since our use case isn't one of those cases where it behaves differently) $chocopath = Join-Path -Path $chocopath.Directory -ChildPath "install" | Join-Path -ChildPath "${{ parameters.which }}" | Join-Path -ChildPath "bin"