- 
                Notifications
    You must be signed in to change notification settings 
- Fork 2.7k
Description
Task name
DownloadPipelineArtifactV2
Task version
No response
Environment type (Please select at least one enviroment where you face this issue)
- Self-Hosted
- Microsoft Hosted
- VMSS Pool
- Container
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Linux
Question
Our agent was not configured with proxy during setup - if we set up proxy at the agent level, different tasks behave differently, some of them respect agent-level proxy settings, some others require explicit HTTP_PROXY env vars at the task-level. If it turns out specific task respect agent-level proxy settings and we don't want to use proxy in this task, we need to use NO_PROXY env and hope it will work or configure .proxybypass at the agent-level. In the end we decided agent will run without proxy, and if any task in our pipelines requires outbound via proxy, it should be handled on task-by-task basis.
Now, looks like in such scenario we cannot use DownloadPipelineArtifactV2 which is baked into the agent. Our agent does not have explicit outbound access to *.blob.core.windows.net. If we try to set up:
env: 
  HTTP_PROXY: $(proxy)
at the DownloadPipelineArtifactV2 task level, it is not respected?
Are there any workarounds or we should really revisit our approach regarding proxy?