Open wgrthoen opened 5 years ago
https://github.com/microsoft/azure-pipelines-extensions/blob/5811d65241068af68651a1dd0d747bde31ca4443/TaskModules/powershell/RemoteDeployer/JobHelper.ps1#L184
This causes commands that normally finish in a few seconds to exhibit unneeded long delays before they finish in Azure Devops.
I would like the start-sleep configurable in ms from https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/PowerShellOnTargetMachinesV3. If that is not possible, reducing this to 3 or 1 second would at least be much better than the current delay.
Background: I'm calling this function 4-6 times per release depending on the enviroment. The start-sleep adds 2-3 minutes to my release. That's quite a bit on a release that takes about 10 minutes in total without the delays.
@RoopeshNair , Can you please look into this ask?
Any updates?
PR with fix https://github.com/microsoft/azure-pipelines-extensions/pull/639
https://github.com/microsoft/azure-pipelines-extensions/blob/5811d65241068af68651a1dd0d747bde31ca4443/TaskModules/powershell/RemoteDeployer/JobHelper.ps1#L184
This causes commands that normally finish in a few seconds to exhibit unneeded long delays before they finish in Azure Devops.
I would like the start-sleep configurable in ms from https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/PowerShellOnTargetMachinesV3. If that is not possible, reducing this to 3 or 1 second would at least be much better than the current delay.
Background: I'm calling this function 4-6 times per release depending on the enviroment. The start-sleep adds 2-3 minutes to my release. That's quite a bit on a release that takes about 10 minutes in total without the delays.