Closed FatalMerlin closed 4 years ago
Hi all,
I found that #65 does in fact not work in Azure DevOps Pipelines. (Re-)Fixes #59.
As stated by the PR creator
I did not try to run it via Azure DevOps.
Azure DevOps transforms all variables to uppercase, so we have to check for uppercase proxy variables.
See here (StackOverflow) and here (VS Developer Community).
Additionally I added a check for undefined, since undefined process.env.VARIABLE is, well undefined:
undefined
$ node > process.env.http_proxy 'http://127.0.0.1:3128/' > process.env.obviously_undefined_env_var // undefined >
This might be relevant to you @sandorfr
thanks
Hi all,
I found that #65 does in fact not work in Azure DevOps Pipelines. (Re-)Fixes #59.
As stated by the PR creator
Azure DevOps transforms all variables to uppercase, so we have to check for uppercase proxy variables.
See here (StackOverflow) and here (VS Developer Community).
Additionally I added a check for
undefined
, since undefined process.env.VARIABLE is, wellundefined
: