According to the Cforge homepage we can get the following such advantages.
Import / Commit
Again, you can use the standard mechanism of CODESYS SVN to commit your changes on your projects. But here cforge has several advantages:
You can import or check in several projects and libraries at once
cforge will also commit every project in binary form, containing the SVN connection settings to your repository
cforge will commit a Markdown file, containing an export of the source codeMyProject/
MyLib/(these files are generated)
MyProject.project
MyProject.md
MyLib.library
MyLib.md
So investigate integrating the cforge tool into our workflow.
Trying to checkout the repository gives the following error:
Version Info:
CODESYS IDE 3.5.16.10
CODESYS SVN 4.2.6.0
Tortoise SVN 1.14
cforge tool 1.0.0.29
This repository [r303]
Sounds like it is getting a false svn URL?
Seems repository specific, as SM3RaspiStepper works. At least it extracts the repositories, even if it throws a few KeyNotFoundException.
The cforge checkout fails because Cforge/Scripts/pysvn.py:svn_list() calls this command line:
If I try the same in command prompt, I get the E175009 error only for these two svn addresses:
but listing the components of trunk is no problem (trunk contains only one folder, mqttsparkplugb):
My first guess is a length issue, ie the command can't handle paths bigger than 256, but I don't know yet which end this is.
I guess checking the server logs might help, but I can see with wireshark exactly what response I get from the server.
Wireshark analysis shows:
After recieving the request, the server waits 30 seconds then sends a FIN ACK. ie. it gives no response.
So it could be the path length is now too great, or it could be the SVN server has a limit on the XML response size. I think only the SVN logs can say why no response is given for the svn list command.
OK, I am convinced it is some sort of timeout issue.
sometimes the same command reports the error, and sometimes it responds correctly.
eg.
Probably a good catch!
Tool is not yet suitable for large SVN repositories, and if we just wait, CODESYS Git will be available.