Azure DevOps Service version: 4.2.491
Azure Agent version: 2.192.0
Azure Agent OS: Windows Server 2019 build 17763.2183
Since updating to the latest version of the Azure DevOps Service on 6 Oct 2021, executing the task ‘Push Package(s) to Octopus’ (Task version 4) results in the ‘–proxy’ flag being added to the push command executed by the task. In our case, this change was breaking and blocked a part of our release pipeline.
octo.cmd push “–server=[server]” “–apiKey=[key]” “–package=[package]”
octo.cmd push “–server=[server]” “–apiKey=[key]” “–package=[package]” “–proxy=[proxy]”
To the best of my knowledge, our proxy settings for this server haven’t changed. As such, I am speculating that the task now automatically detects user proxy settings (i.e. the user LAN settings configurable via Internet Explorer) and adds them to the command.
If my speculation is correct, this is a potentially breaking change. Could I suggest adding a checkbox to the task that allows users to opt-in to this behaviour, instead of providing it by default?
Please let me know if no such change exists and I will go and re-check my assumptions
Thanks for your time,