Hi all,

Any progress on this?

We would really appreciate this!
Our environment is suffering a lot from this issue!

  1. We have build servers running many different subversion client versions (1.5 - 1.7)
  2. Many of our Job's build steps invoke command-line svn for several tasks
  3. We have Jobs that explicitly require subversion >=1.7, while we MUST keep the global subversion to 1.6 (because of previous point)
  4. Our current workaround uses svn upgrade when an svn command fails, but:
    • This only works for some of the issues
    • requires a lot of maintenance, taking very much of our precious time!

So, I would like to increase priority on this issue.

Thanks in advance!

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.

Reply via email to