Honor proxy settings

See original GitHub issue

PR #62 already introduced proxy support by using getHttpProxyConfiguration in order to get the proxy settings used by the current agent.

Somehow the calls common.setProxy() are still commented out? Why?

Currently the task is unable to install the tfx-cli package behind a corporate proxy…

cc @jessehouwing

Issue Analytics

State:
Created 5 years ago
Comments:5

Top GitHub Comments

1reaction

axelheercommented, Aug 26, 2020

Since I ran into this again, for further reference:

- pwsh: |
    Write-Host "##vso[task.setvariable variable=NPM_CONFIG_PROXY;]$env:AGENT_PROXYURL"
    Write-Host "##vso[task.setvariable variable=NPM_CONFIG_HTTPS-PROXY;]$env:AGENT_PROXYURL"
  displayName: 'Setup NPM proxy configuration'

- task: TfxInstaller@3
  inputs:
    version: 'v0.8.x'
  displayName: 'Install TFX'

- pwsh: |
    Write-Host "##vso[task.setvariable variable=NPM_CONFIG_PROXY;]"
    Write-Host "##vso[task.setvariable variable=NPM_CONFIG_HTTPS-PROXY;]"
  displayName: 'Reset NPM proxy configuration'

This sets the npm proxy just for the TFX installer…

0reactions

jessehouwingcommented, Sep 28, 2018

I can’t make it work “right”, generic proxy config with “everything through proxy” works, but many corps require fancy exclusions and other things. You can configure Node on the machine to handle your proxy correctly, you can set the environment variables, that way the task won’t have to deal with it at all. That’s currently my preferred stance.