Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Duplicate
-
Component/s: subversion-plugin
-
Labels:None
-
Environment:Platform: All, OS: WIndows Server 2012
-
Similar Issues:
Description
This is a clone of the original bug, when When attempting a tag after selecting 'Tag this build', the tag fails. This is also related to 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, with a working copy of version 1.7.
The SVN server is "SmartSVN" hosted on a Windows 2012 server. It has the non-configurable convention of requiring serverpath/svn/ before your repo name, and on the log I failed to capture, I saw it complain about /svn/myreponame on the copy.
There is only one user specified in the Jenkins credentials for SVN, and they have tagging privileges.
And I tried the workaround from a similar bug, where you:
1. Connect to the target machine
2. Run `svn cleanup` & `svn up` on each workspace, specifying the credentials
But that had no impact on the result.
There are no credentials stored in my hudson.scm.SubversionSCM.xml file:
<?xml version='1.0' encoding='UTF-8'?>
<hudson.scm.SubversionSCM_-DescriptorImpl plugin="subversion@2.4.1">
<generation>49</generation>
<mayHaveLegacyPerJobCredentials>false</mayHaveLegacyPerJobCredentials>
<workspaceFormat>100</workspaceFormat>
<validateRemoteUpToVar>false</validateRemoteUpToVar>
<storeAuthToDisk>false</storeAuthToDisk>
</hudson.scm.SubversionSCM_-DescriptorImpl>
Attachments
Issue Links
- duplicates
-
-
- Resolved
-
- is related to
-
-
- Resolved
-
Activity
Damon Overboe
created issue -
Damon Overboe
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | current [ 10162 ] | |
| Description |
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 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 |
| Environment | Platform: All, OS: HP-UX | Platform: All, OS: WIndows Server 2012 |
| Resolution | Incomplete [ 4 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
Damon Overboe
made changes -
| 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 is a clone of the original bug, when When attempting a tag after selecting 'Tag this build', the tag fails. This is also related to 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, with a working copy of version 1.7. The SVN server is "SmartSVN" hosted on a Windows 2012 server. It has the non-configurable convention of requiring serverpath/svn/ before your repo name, and on the log I failed to capture, I saw it complain about /svn/myreponame on the copy. There is only one user specified in the Jenkins credentials for SVN, and they have tagging privileges. And I tried the workaround from a similar bug, where you: 1. Connect to the target machine 2. Run `svn cleanup` & `svn up` on each workspace, specifying the credentials But that had no impact on the result. There are no credentials stored in my hudson.scm.SubversionSCM.xml file: <?xml version='1.0' encoding='UTF-8'?> <hudson.scm.SubversionSCM_-DescriptorImpl plugin="subversion@2.4.1"> <generation>49</generation> <mayHaveLegacyPerJobCredentials>false</mayHaveLegacyPerJobCredentials> <workspaceFormat>100</workspaceFormat> <validateRemoteUpToVar>false</validateRemoteUpToVar> <storeAuthToDisk>false</storeAuthToDisk> </hudson.scm.SubversionSCM_-DescriptorImpl> |
| Resolution | Incomplete [ 4 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
| Status | Reopened [ 4 ] | Open [ 1 ] |
| Component/s | subversion [ 15485 ] | |
| Component/s | svn-tag [ 15518 ] | |
| Fix Version/s | current [ 10162 ] | |
| Affects Version/s | current [ 10162 ] |
| Summary | CLONE - Create Tag (Tag this build) Not working | Create Tag (Tag this build) Not working |
| Link |
This issue is related to |
| Assignee | Manuel Jesús Recena Soto [ recena ] |
| Link |
This issue duplicates |
| Resolution | Duplicate [ 3 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Workflow | JNJira [ 157299 ] | JNJira + In-Review [ 195673 ] |