|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
It does exist on both. I was using 1.575 and was following the advice to not upgrade unless you see a bug.
Then, I upgraded to 1.576 and it still exists.
I've been able to work around it for now by installing the SVN Tag plugin; my best guess is it's an issue with not liking the url that's forced on us by VisualSVN http:/path-to-server/svn/yourreponame because I saw some behavior with it that appeared to think that http:/path-to-server/svn/ was the actual repo, whereas that's actually nothing; a web browser will list all of the available repos under that, but clients (command line, TortoiseSVN, SmartSVN) will throw an error.
I'm trying to figure out how to prove that out; I think what I can probably do is test using the tagger against the archives, which are NOT served by VisualSVN, and compare that behavior against the live ones which are served by it.