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>