![]() |
|
|
|
|
Change By:
|
Damon Overboe
(21/Aug/14 5:21 PM)
|
|
Fix Version/s:
|
current
|
|
Environment:
|
Platform: All, OS:
HP-UX
WIndows Server 2012
|
|
Description:
|
This is a clone of the original bug, when When attempting a tag after selecting 'Tag this build', the tag fails.
Generally, it fails silently, not pumping any information to the UI or even the event logs (even with the hudson Subversion SCM log set to 'fine' or higher).
I was able to get it to pump one failure message, but I was not able to capture it. I am restarting the VM to see if it will pump the message again.
I can recreate it using Jenkins 1.575 or 1.576 on Windows Server 2012, using the latest of the Subversion plugin.
Original meessage:
--------
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.
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.
