one of our teams has noticed an issue that seems to occur when doing an SVN checkout of a project (with path: https://svn.xxxxx.com/svn/packages/my_project/trunk) that contains multiple externals. This issue's appearance seems to coincide with the date when we did the update to 5.1.0, which improved the support of SVN externals. Here is the issue:
09:23:46,534 DEBUG - Executing command: svn log https://svn.xxxxx.com/svn/teamlib/external/allegro/trunk/ --non-interactive --trust-server-cert --username xxxx --password ****** -v --xml -r 14006:14003
09:23:46,534 DEBUG - Command working directory: C:\Work\buildagent\bin
09:23:46,944 WARN - svn: E160013: '/svn/teamlib/!svn/bc/15823/external/allegro/trunk' path not found
The weird thing is that the SVN path above does not exist! However, our project has an SVN external property that points to something that resembles the above path (https://svn.xxxxx.com/svn/teamlib/external/allegro/tags/4.1.16-xxx.4) which does exist, but there are NO "trunk" folder underneath the "https://svn.xxxxx.com/svn/teamlib/external/allegro" folder. So I don't know how or why QB constructed this SVN path...
However, this error does not occur all the time, only when the "svn log" commands attempts to be ran on some of the svn externals path which are weirdly constructed for some reason. When QB only does 1 svn log command on the main project (svn log https://svn.xxxxx.com/svn/packages/my_project/trunk), then the checkout step is successful.
Can you look into this issue? It is pretty major for us right now.
Thanks in advance!