Wednesday, March 21, 2012 1:57 PM
I Have a problem to connect TFS 2010 SP1 via clc of TEE-11: 504 error, you know.
By eclipse plugin also i have problems to connect. But at the end I changed Global Proxy Setting from Native to Manual and it got working.
To Resolve conflicts with new non-modal Resolve window in Work Area is getting better.
Is it possible to connect TFS 2010 SP1 via clc of TEE-11?
I want to check Merge with External tool workflow.
P. S. I feed up our Linux team with jam tommorow last two years.
- Edited by maxmiracle Wednesday, March 21, 2012 2:02 PM
Wednesday, March 21, 2012 5:25 PM
yeah it is possible to connect from CLC TEE-11 to TFS 2010 SP1. It seems that you are having proxy issues so as you configured the proxy settings from Eclipse, you also need to configure a proxy for the CLC to use. You can configure a proxy for the CLC by setting the environment variable HTTP_PROXY to the URL of your proxy. Please let me know if that didn't work for you.
I am not sure what you need to know about merge with external tool. You can do merge with external tool both from the plugin and the CLC. You can define an external merge tool for the plugin by going to the preferences, navigate to Team, Team Foundation Server, Merge tool and configure any tool there. You can define an external merge tool for the CLC by setting the environment variable TF_MERGE_COMMAND to the path of your merge tool and the arguments it needs. Please ket me know if that does not answer your question.
Thursday, March 22, 2012 8:36 AM
I found the way how to test clc - I set global proxy settings to direct access. It works.
My tfs works in ethernet without any proxy.
I want to configure tf clc on Linux system.
tf dir -login:"companydomain\user","pass" -collection:"http://tfs:8080/tfs/collectionName"
An error occurred: The SOAP endpoint http://tfs:8080/tfs/collectionName/Services/v3.0/LocationService.asmx could not be contacted. HTTP status: 504
But at the browser link http://tfs:8080/tfs/collectionName/Services/v3.0/LocationService.asmx works!
So tfs server is in list of excluded addresses of proxy in global settings.
If i set direct connect in os settings the command becomes to work.
I need system proxy settings to access internet via proxy but tfs-clc should connect directly to the tfs server.
How to configure the case?
Is Parameter GLOBAL_PROXY eliminated in clc of TEE-11?
Thursday, March 22, 2012 3:13 PMModerator
As you've noticed, we've made a number of changes to the connection experience in the TEE 11 Beta. First we added support in the TFS plug-in for Eclipse for connecting to tfspreview.com. Second, after listening to feedback from users, we discovered that while our connection profiles were very powerful, they were also sometimes confusing.
We took the steps to simplify the connection experience as much as possible and match the Visual Studio getting started experience as much as possible.
Here's the new process for determining the HTTP proxy to use in the Command-Line Client:
If the environment variable HTTP_PROXY is set, we will simply use that.
We next examine the Java system properties: http.proxyHost, http.proxyPort and http.nonProxyHosts as documented in the Java 1.4.2 Networking Properties guide. If your host is NOT included in the http.nonProxyHosts system property, then we will use the value of http.proxyHost and http.proxyPort as your HTTP proxy. (For HTTPS connections, we use the https. system properties.)
Some JVMs are better about setting this from the system configuration than others. For example, JVMs on Mac OS will set them from system properties, while others will not.
We'd recommend that you add your TFS server to the http.nonProxyHost system property for the beta release, but we'd appreciate feedback if we can make this easier for you to configure.
Friday, March 23, 2012 9:27 AM
Thank you for information about new tricky algorithm.
In your shell you should unset HTTP_PROXY for tf-clc.
Why does algorithm do not use NO_PROXY environment variable (list of excluded hosts of the system proxy)?
If in a system HTTP_PROXY is set, http.proxyHost, http.proxyPort and http.nonProxyHosts will never be fired!
In Linux HTTP_PROXY, NO_PROXY are system variables by default.
You should use HTTP_PROXY with NO_PROXY or do not use at all.
- Marked As Answer by maxmiracle Friday, March 23, 2012 9:27 AM
Friday, March 23, 2012 3:25 PMModerator
I appreciate the input.
I agree regarding the NO_PROXY environment variable. I'll look into this further.