Closed Thilas closed 4 years ago
I just splitted my initial commit in 2 to better understand the actual change I'm proposing here (i.e. the 2nd commit).
What about the tasks versioning? Do I need to bump the versions myself in each relevant json files or is it automatic?
@jbramwell, any chance you could review this PR soon? Thank you.
This PR aims at using the
PowerShell3
execution handler instead of the deprecatedPowerShell
one. This change requires to get arguments of the ps1 scripts differently (i.e. using$env:INPUT_XXX
variables). I didn't identify anything else to patch given the tasks logic. See https://github.com/microsoft/azure-pipelines-task-lib/tree/master/powershell for more details.A more robust way to go would be to directly rely on VstsTaskSdk module. But this would require either to commit and push this module for each task or to restore it on the fly when building the extension (both locally and in the CI).
NB: ps1 files were removed in a previous commit (mistake?). I reverted this in order to patch the scripts.
Fixes #12.