![]() |
|
|
|
|
Change By:
|
Damon Overboe
(21/Aug/14 5:30 PM)
|
|
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
This is also related
to
the UI or even the event logs (even with the hudson Subversion SCM log set to 'fine' or higher)
https://issues
.
jenkins-ci.org/browse/JENKINS-21797, but I have eliminated that.
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.
Generally, it fails silently, not pumping any information to the UI or even the event logs (even with the hudson.scm.SubversionSCM log set to 'fine' or higher).
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
, with a working copy of
version 1.
227
7
.
Stand alone setup running on Winstone.
When attempting
The SVN server is "SmartSVN" hosted on
a
tag after selecting 'Tag this build',
Windows 2012 server. It has
the
tag fails with an error:
Tagging http:
non-configurable convention of requiring serverpath
/
/subversion/
svn/
XXXXX/web/project/trunk (rev.19085)
before your repo name, and on the log I failed
to
http:
capture, I saw it complain about
/
/subversion/
svn/
XXXXX/web/project/tags/project-30
myreponame on the copy.
Failed to tag
org
There is only one user specified in the Jenkins credentials for SVN, and they have tagging privileges
.
tmatesoft.svn.core.SVNAuthenticationException: svn: Commit failed (details
follow):
svn
And I tried the workaround from a similar bug, where you
:
CHECKOUT of '/svn/XXXXX/!svn/ver/19211/web/project/tags': 403 Forbidden
(http://subversion)
at
org
1
.
tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:84)
Connect to the target machine
at org
2
.
tmatesoft.
Run `
svn
.core.wc.SVNCopyClient.doCopy(SVNCopyClient.java:354)
cleanup` & `svn up` on each workspace, specifying the credentials
at
hudson
But that had no impact on the result
.
scm.SubversionTagAction$TagWorkerThread.perform(SubversionTagAction.java:167)
at hudson.model.TaskThread.run(TaskThread.java:77)
Completed
The error suggests the user setup within the
There are no credentials stored in my
hudson.scm.SubversionSCM.xml
does
file:
not have the authority to checkout the subversion tags directory revision
<?xml version='1
.
0' encoding='UTF-8'?>
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
SubversionSCM_-DescriptorImpl plugin="subversion@2
.
xml file
4
.
Thus, if the user account that started Hudson
1">
does not have enough permissions for SVN, then the tagging fails with the above
<generation>49</generation>
error.
<mayHaveLegacyPerJobCredentials>false</mayHaveLegacyPerJobCredentials>
<workspaceFormat>100</workspaceFormat>
Regards
<validateRemoteUpToVar>false</validateRemoteUpToVar>
<storeAuthToDisk>false</storeAuthToDisk>
Matt Gaunt
</hudson.scm.SubversionSCM_-DescriptorImpl>
|
|
|
|
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.
