Extend CI test matrix to match PowerShellEditorServices

Author: andyleejordan

.vsts-ci/azure-pipelines-ci.yml

@@ -22,23 +22,41 @@ resources:
     ref: master
 
 jobs:
-- job: Win2019
-  displayName: Windows Server 2019
+- job: PS51_Win2016
+  displayName: PowerShell 5.1 - Windows Server 2016
+  pool:
+    vmImage: vs2017-win2016
+  steps:
+  - template: templates/ci-general.yml
+    parameters:
+      pwsh: false
+
+- job: PS51_Win2019
+  displayName: PowerShell 5.1 - Windows Server 2019
+  pool:
+    vmImage: windows-2019
+  steps:
+  - template: templates/ci-general.yml
+    parameters:
+      pwsh: false
+
+- job: PS7_Win2019
+  displayName: PowerShell 7 - Windows Server 2019
   pool:
     vmImage: windows-2019
   steps:
   - template: templates/ci-general.yml
 
-- job: macOS
-  displayName: macOS 10.15
+- job: PS7_macOS
+  displayName: PowerShell 7 - macOS 10.15
   pool:
     vmImage: macOS-10.15
   steps:
   - template: templates/ci-general.yml
 
-- job: Ubuntu
-  displayName: Ubuntu 20.04
+- job: PS7_Ubuntu
+  displayName: PowerShell 7 - Ubuntu 20.04
   pool:
-    vmImage: Ubuntu-20.04
+    vmImage: ubuntu-20.04
   steps:
   - template: templates/ci-general.yml

.vsts-ci/templates/ci-general.yml

@@ -1,11 +1,18 @@
 parameters:
+  - name: pwsh
+    type: boolean
+    default: true
   - name: usePipelineArtifact
     type: boolean
     default: false
 
 steps:
-- pwsh: $PSVersionTable
+- task: PowerShell@2
   displayName: PowerShell version
+  inputs:
+    targetType: inline
+    script: $PSVersionTable
+    pwsh: ${{ parameters.pwsh }}
 
 - checkout: self
 
@@ -34,12 +41,16 @@ steps:
     archiveFilePatterns: $(Pipeline.Workspace)/PowerShellEditorServices.zip
     destinationFolder: $(Build.SourcesDirectory)/vscode-powershell/modules
 
-- pwsh: |
-    Install-Module InvokeBuild -Scope CurrentUser -Force
-    Invoke-Build
-    Write-Host "##vso[task.setvariable variable=vsixPath]$(Resolve-Path powershell-*.vsix)"
+- task: PowerShell@2
   displayName: Build and test
-  workingDirectory: $(Build.SourcesDirectory)/vscode-powershell
+  inputs:
+    targetType: inline
+    script: |
+      Install-Module InvokeBuild -Scope CurrentUser -Force
+      Invoke-Build
+      Write-Host "##vso[task.setvariable variable=vsixPath]$(Resolve-Path powershell-*.vsix)"
+    workingDirectory: $(Build.SourcesDirectory)/vscode-powershell
+    pwsh: ${{ parameters.pwsh }}
 
 - publish: $(vsixPath)
   artifact: vscode-powershell-vsix-$(System.JobId)

README.md

@@ -21,16 +21,23 @@ not activated by default, but after installing this extension either click "Set
 Theme" or use the [theme picker](https://code.visualstudio.com/docs/getstarted/themes) and
 select "PowerShell ISE" for a fun and familiar experience.
 
-## Platform support
+## Platform Support
 
-- **Windows 7 through 10** with Windows PowerShell v3 and higher, and PowerShell Core
-- **Linux** with PowerShell Core (all PowerShell-supported distributions)
-- **macOS and OS X** with PowerShell Core
+The extension _should_ work anywhere VS Code itself and PowerShell Core 7 or higher is
+[supported][]. For Windows PowerShell, only version 5.1 is supported. Please note that
+PowerShell Core 6 is end-of-life and so not supported. Our test matrix includes the
+following:
+
+- **Windows Server 2016 and 2019** with Windows PowerShell 5.1 and PowerShell Core 7.1.4
+- **macOS 10.15** with PowerShell Core 7.1.4
+- **Ubuntu 20.04** with PowerShell Core 7.1.4
+
+[supported]: https://docs.microsoft.com/en-us/powershell/scripting/powershell-support-lifecycle?view=powershell-7.1#supported-platforms
 
 Read the [installation instructions](https://docs.microsoft.com/en-us/powershell/scripting/components/vscode/using-vscode)
 to get more details on how to use the extension on these platforms.
 
-Read the [troubleshooting guide](./docs/troubleshooting.md) for answers to common questions.
+**Read the [troubleshooting guide](./docs/troubleshooting.md) for answers to common questions.**
 
 ## Features