Closed fromthewoods closed 3 years ago
Hi @fromthewoods,
thanks for reporting this. This is a known issue in one of the libraries that are used by our task. It does not use the proxy bypass list under some circumstances. Could you set the variable NO_PROXY to an empty value in your pipeline? This should force the library to use the proxy bypass list from the agent configuration. Please let me know if this works for you.
I'm already working on a new version of the task with an updated version of the library. However, we need to test for all on-prem versions of Azure DevOps Server/Team Foundation Server to ensure that this updated library does not break anything there.
Thanks @ReneSchumacher ... that work around seems to work. Any plans for when the updated task will be released?
Hey, sorry for not updating this issue. The latest version 8.0.3 already had the fix, so it should work without seeing the NO_PROXY variable to an empty value.
Closing this issue now as it has been fixed. Please feel free to comment again if you still have problems with proxy configuration and Build Quality Checks.
We just migrated our collection from TFS 2018 deployment to a new Azure DevOps Server 2020 deployment (new servers). This is a new agent on an existing Build server. Below is a log of a build agent step for Build Quality Checks.
Any help on what endpoint it is failing to talk to and how to resolve would be appreciated. It seems like a proxy issue, but the log shows the correct proxy values.