|
||||||||
|
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/groups/opt_out.
At time of posting the issue, it was 1.7. Currently 1.8.
Yes, it seems to be overwritten. If one does an "svn up" on the command line, svn behaves the excpected way (,like configured during checkout). If it's done with the jenkins job configuration, it behaves like set in the drop-down, ignoring the set values.
For sure, I was working around a not optimally set up SVN repository. But I am sure, this will happen to a lot of other users as well. Especially, if you need to set up continuous delivery for legacy projects, with a lot of svn:externals and not optimal repository structure. I am talking of several GB of source and configuration, which was fetched in my case and times of weeks for first attempts in reorganising the repository, to get better separation.