Error communicating with TFS server from 1.0.0.1647

Thanks, new build is up.

Nice one, looks like that’s sorted it. Many thanks

Hi Vincent,

I am creating a new repository for first time.I have given repository type as Team Foundation Server and gave server name as http://tfs.humana.com:8080/tfs(we used this to connect to TFS) and given my username as DOMAIN/UserId and password. But its saying "Failed to authenticate with Server please check your username/password" . Can you please help on this?

I had the same behaviour.  Try just using the user name without the domain.

I also tried by removing domain name but still the same error resumes

Can you please provide me the link for latest build to be installed to overcome these errors. Currently we are using ContinuaCI.Server.Setup_x64_1.0.0.1427 to install. Please provide the link which we need to install to get rid of these errors.

Pinned to the top of this forum is the a topic with download links to the latest build :

https://www.finalbuilder.com/Support/Forums/aft/11781.aspx

Now that I’ve got the RC up and running, I’m back to having this same issue.

“Cannot connect with TFS on the server, please check server URL”. The url is correct. I think the issue is that the request has to go from one data center to another (the Continua server is in Vegas, the TFS server is in Atlanta), and it’s timing out.

Is there a way to increase the timeout for the request? I can’t find any settings in the config file(s).

Posted By Christopher Johnson on 26 Apr 2013 02:04 PM
Now that I've got the RC up and running, I'm back to having this same issue.

"Cannot connect with TFS on the server, please check server URL". The url is correct. I think the issue is that the request has to go from one data center to another (the Continua server is in Vegas, the TFS server is in Atlanta), and it's timing out.

Is there a way to increase the timeout for the request? I can't find any settings in the config file(s).

Hi Christopher

The TFS api's we use do not provide any timeout options. I suspect may not be able to use Continua with TFS in this manner. On our local (Gb) network, it can take 20+ seconds to connect to TFS on a good day.. over a wan I would hate to think how long it would take. In our experience, TFS is just slow.. and that's putting it politely. 


Hi Christopher

As you’re using Continua here, I guess you’re using TFS for source control and not running your builds. Maybe using something like Git-TFS (https://github.com/git-tfs/git-tfs) could help here? Pull your source into a local Git repo, then run Continua against that.

I haven’t used it myself - we’re moving away from TFS and replacing it with Git, YouTrack and Continua.

HTH!

Well, the main reason I even want to bother connecting to TFS is so I can source-control the FB projects I'm currently using to do actual deployments. TFS handles the code building, Continua will be the scheduler and FB the deployment tool (at least until the Continua deployment solution is done and I can see if that will work for our needs). Also, for TFS work items if a build fails.


Oh well. It's a moot point, as I'm going to end up with a split deployment environment anyway since the project to eliminate the second data center is on hold now.