Create Project - From a repository URL VCS autodetect fails.
After upgrading Team City from version 9 to 2017.1.1 we observed the Create Project - From a repository URL is now failing. The error message indicates it could not connect to the TFS server. We do not use TFS. The TFS plugin log in the TeamCity folder has also started logging this error beginning with our upgrade.
My understanding is Team City parses out the URL and determines VCS from that. It then calls the appropriate plugin/Java jar to perform the operations.
We have two SVN locations, each with different URL pattern. Both are now failing.
Example of URLs:
https://svn.companyname.com/svn/Retail/
https://sourcecode.companyname.com:8443/svn/OurProductRocks
I have read, and appreciate, the great documentation available, including this article: https://confluence.jetbrains.com/display/TCD10/Guess+Settings+from+Repository+URL
I am just confused as to how the behavior changed. Additionally, the documentation indicates the fix for this is to change the VCS under project configuration. But this doesn't exist until after the project gets imported.
Thank you!
Please sign in to leave a comment.
Hi,
Regarding the autodetection, could you send us a screenshot of the input you type, and the result that it detects including error messages, etc? We'll look into why it would be detecting that.
Also, regarding creating the project, you can create the project from scratch, instead of importing, then adding the VCS Root manually as suggested. It only takes a couple extra steps and the result should be the same.
Thanks for the help, Denis.
The screenshot attached shows I am getting an error related to the certificate attached to the TFS Java application. Since we are not using TFS, I have not configured the certificate for use here. The main Team City Java application does have its certificate properly set.
When looking at the teamcity-tfs.log, I see several errors that occur as a result of this action. But I would think I should see something from an SVN log (I couldn't find this log) and not TFS.
I will run the suggestion of creating from scratch by the development team complaining about this.