[
https://issues.jenkins-ci.org/browse/JENKINS-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159838#comment-159838
]
Jean-Pol Landrain commented on JENKINS-1930:
--------------------------------------------
I have done a test with one of the latest version of Jenkins to date (1.451).
The issue is not present.
> Create Tag (Tag this build) Not working
> ---------------------------------------
>
> Key: JENKINS-1930
> URL: https://issues.jenkins-ci.org/browse/JENKINS-1930
> Project: Jenkins
> Issue Type: Bug
> Components: svn-tag
> Affects Versions: current
> Environment: Platform: All, OS: HP-UX
> Reporter: wymgaz
>
> Hudson version 1.227. Stand alone setup running on Winstone.
> When attempting a tag after selecting 'Tag this build', the tag fails with an
> error:
> Tagging http://subversion/svn/XXXXX/web/project/trunk (rev.19085) to
> http://subversion/svn/XXXXX/web/project/tags/project-30
> Failed to tag
> org.tmatesoft.svn.core.SVNAuthenticationException: svn: Commit failed (details
> follow):
> svn: CHECKOUT of '/svn/XXXXX/!svn/ver/19211/web/project/tags': 403 Forbidden
> (http://subversion)
> at
> org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:84)
> at
> org.tmatesoft.svn.core.wc.SVNCopyClient.doCopy(SVNCopyClient.java:354)
> at
> hudson.scm.SubversionTagAction$TagWorkerThread.perform(SubversionTagAction.java:167)
> at hudson.model.TaskThread.run(TaskThread.java:77)
> Completed
> The error suggests the user setup within the hudson.scm.SubversionSCM.xml does
> not have the authority to checkout the subversion tags directory revision.
> Further investigation found the user being used for the tag is the user that
> started Hudson in the first instance, and NOT the user declared in the
> hudson.scm.SubversionSCM.xml file. Thus, if the user account that started
> Hudson
> does not have enough permissions for SVN, then the tagging fails with the
> above
> error.
> Regards
> Matt Gaunt
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
