Azure-pipelines-tasks: Azure Powershell - Set workingFolder
Similar to the Powershell VSO Build Agent, can we set the workingFolder when instantiating Azure Powershell?
Use Case:
I am trying to download assets from Azure Blob storage to the build machines. From my build logs, the working directory is set to wherever Azure Powershell lives.
2016-01-27T20:16:32.1304033Z Found 5 blob(s)
2016-01-27T20:16:32.1414028Z Downloading to C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agents\default\tasks\AzurePowerShell\1.0.8\
Workaround:
Use $PSScriptRoot to figure out where my script is and go from there.
jpoon
All 8 comments
currently no.
yaananth
on 16 Feb 2016
@ericsciple - let's add this.
bryanmacfarlane
on 21 Apr 2016
I just uploaded the entire task directory up to blob storage accidentally because of this. $PSScriptRoot is a good work-around, but please add support. Thanks!
gregjhogan
on 3 Jun 2016
Added it to backlog Feature: 649929
RoopeshNair
on 24 Aug 2016
@RoopeshNair What is backlog feature 649929? I presume this has been moved to a private VSTS. If that is the case, how can we (the community) be aware of what's going on with this issue?
jpoon
on 24 Aug 2016
Just stumbled upon the same issue, extremely irritating. This should be fixed asap, and if not then there has to be a big fat warning about this behaviour.
letmaik
on 13 Apr 2017
@yaananth @RoopeshNair
Any updates?
Anufryieu
on 20 Dec 2018
Not at this point in time, we haven't been able to get to this.
We do encourage contributions, if you are willing to help.
RoopeshNair
on 21 Dec 2018
Related issues
pharring
路
3Comments
richard-ob
路
3Comments
gregpakes
路
3Comments
timfish
路
3Comments
MichaelWhiteCodingForFun
路
3Comments
Most helpful comment
@ericsciple - let's add this.