|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
The workaround is not necessarily trivial. As the OP says, "Our build-tools use internally the host subversion client. Because of the incompatibility between 1.6 and 1.7, those tools can't read the 1.6 format without upgrade."
I had this same problem at my previous company. We had ~50 different build machine projects that all needed to get upgraded, just because Jenkins couldn't support multiple slave svn versions.