Added proxy support for coveragepublisher common task - HTTP_PROXY, HTTPS_PROXY, and NO_PROXY env support #19826
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Task name: Added proxy support for coveragepublisher common task
Description: Added HTTP_PROXY, HTTPS_PROXY, and NO_PROXY env for coveragepublisher common task.
Fix an issue regarding CoveragePublisher.Console connection failing if it needs to go through proxy.
Issue originated from PublishCodeCoverageResults@2 wherein when the build agent is behind a proxy, the task will fail as the outbound connection is not routing/using the proxy correctly.
Documentation changes required: Ideally - Add information regarding the use of the HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variable if proxy is required for outboundconnection
Added unit tests: N
Attached related issue: N (