|
||||||||
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 |
[JIRA] (JENKINS-12666) Subversion fails first revision check
su...@group1solutions.com.au (JIRA) Wed, 26 Dec 2012 21:41:55 -0800
- [JIRA] (JENKINS-12666) Subversion fail... su...@group1solutions.com.au (JIRA)
- [JIRA] (JENKINS-12666) Subversion... su...@group1solutions.com.au (JIRA)
- [JIRA] (JENKINS-12666) Subversion... su...@group1solutions.com.au (JIRA)
I'm also running across this problem. v 1.495 WAR file.
Using Jenkins to deploy a specific build by adding a repo@${revision} parameter to the SVN URL, using HEAD is fine, but using any specific revision only works when there is anon read access to the repo, which is not desirable for a private repo.