You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, we found that after setting up the Proxy, although the automatic update usually works, the original regular release operation for the intranet will become an error of being unable to find the domain location. Can the self-hosted agent have an independent parameter only provided for the automatic update of the self-hosted agent instead of being applied universally, which will affect the original call for the local scheduling task?
Describe your feature request here
We need a Proxy on our intranet to update the self-hosted agent automatically. Like this:
.\config --proxyurl http://proxy:port --proxyusername "xxx" --proxypassword "yyy"
However, we found that after setting up the Proxy, although the automatic update usually works, the original regular release operation for the intranet will become an error of being unable to find the domain location. Can the self-hosted agent have an independent parameter only provided for the automatic update of the self-hosted agent instead of being applied universally, which will affect the original call for the local scheduling task?
Like provide
--updateagentproxyurl
parameter:.\config --updateagentproxyurl http://proxy:port --proxyusername "xxx" --proxypassword "yyy"
The text was updated successfully, but these errors were encountered: