From 651d5026244d385b14d8c936fbc71ff65e14e5d7 Mon Sep 17 00:00:00 2001 From: Pietro Gagliardi Date: Sun, 7 Apr 2019 00:43:41 -0400 Subject: [PATCH] That didn't quite work --- azure-pipelines/windows-setup-mingw.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/azure-pipelines/windows-setup-mingw.yml b/azure-pipelines/windows-setup-mingw.yml index b6c9e9be..d259a371 100644 --- a/azure-pipelines/windows-setup-mingw.yml +++ b/azure-pipelines/windows-setup-mingw.yml @@ -8,6 +8,7 @@ steps: $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" - echo "abcdef##vso[task.prependpath]$chocopath" + dir $chocopath | Write-Error + Write-Error "##vso[task.prependpath]$chocopath" exit 1 displayName: 'Set Up MinGW-w64'