From 36ab47314482f4fed9f158ba98dd4b9301c5b676 Mon Sep 17 00:00:00 2001 From: David Wilson Date: Thu, 26 Jan 2017 06:51:15 -0800 Subject: [PATCH] Produce a static VSIX package name on AppVeyor This change causes our build script to always produce a VSIX package called PowerShell-insiders.vsix so that PowerShell scripts can easily download the packages using the permalink: https://www.appveyor.com/docs/packaging-artifacts/#permalink-to-the-last-successful-build-artifact --- vscode-powershell.build.ps1 | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/vscode-powershell.build.ps1 b/vscode-powershell.build.ps1 index 9535493a6f..a6a1671edf 100644 --- a/vscode-powershell.build.ps1 +++ b/vscode-powershell.build.ps1 @@ -93,13 +93,16 @@ task Package { Copy-Item -Recurse -Force ..\PowerShellEditorServices\module\PowerShellEditorServices .\modules } - Write-Host "`n### Packaging PowerShell-$($script:ExtensionVersion).vsix`n" -ForegroundColor Green + Write-Host "`n### Packaging PowerShell-insiders.vsix`n" -ForegroundColor Green exec { & node ./node_modules/vsce/out/vsce package } + + # Change the package to have a static name for automation purposes + Move-Item .\PowerShell-$($script:ExtensionVersion).vsix .\PowerShell-insiders.vsix } task UploadArtifacts -If { $env:AppVeyor } { - Push-AppveyorArtifact .\PowerShell-$($script:ExtensionVersion).vsix + Push-AppveyorArtifact .\PowerShell-insiders.vsix } # The default task is to run the entire CI build