Working with Unreal Engine 4.8.3, we wanted to try out the integrated Source Control when we bumped into an unexpected problem.
We have two ways of accessing the same repository: either via
There are some minor differences in permissions and perforrmance, but the two can be used pretty much interchangably, i.e. while most of us the svn variant, the few colleagues who need to access the repository via https can commit their changes to the same repository without any problems.
For our Unreal project, we created a new repository, which we checked out using the svn path. Using TortoiseSVN, version control behaved as expected. However, we had problems logging in to the integrated Source Control.
Entering the svn path in the Source Control Login’s Repository field always failed with “Unable to connect to a repository at URL” and “Authentication error from server” even with the correct user name and password.
We then tried entering the https alias instead, which also failed. Surprisingly, the error message is exactly the same, i.e. it looks like the Source Control is still trying to access the svn repository path.
At first we figured that the engine might have cached the previous Repository entry, but when we asked a colleague who hadn’t used the Source Control before to try this, the result was the same. This led me to believe that the engine was pulling the repository path from the project’s svn checkout path. To test this, I did another check out from the https address and then tried the Source Control login again, which immediately worked.
- Source Control only accepts “https” repository paths
- Source Control appears to use the project’s checkout path instead of the entered Repository, or at least check against it
We found a workaround, so this is by no means urgent, but it’s at the very least confusing.