Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: svn-tag-plugin
-
Labels:None
-
Similar Issues:
Description
SVN tagging fails randomly with the below error. And it passes without any changes by just re-running the build.
Started by user z000dg8c Building on master Updating https://bhscme.access.nokiasiemensnetworks.com/isource/svnroot/scm_uplane/trunk/mttest/testcases/trunk/smoketests At revision 93 no change for https://bhscme.access.nokiasiemensnetworks.com/isource/svnroot/scm_uplane/trunk/mttest/testcases/trunk/smoketests since the previous build [workspace] $ /bin/sh -xe /tmp/hudson5736673732388142370.sh Remote Module Location: https://bhscme.access.nokiasiemensnetworks.com/isource/svnroot/scm_uplane/trunk/mttest/testcases/trunk/smoketests@85. Tag Base URL: https://bhscme.access.nokiasiemensnetworks.com/isource/svnroot/scm_uplane/tags/Test-Copy. Sleeping for 10 seconds after deleting the existing tag Delete old tag https://bhscme.access.nokiasiemensnetworks.com/isource/svnroot/scm_uplane/tags/Test-Copy. Subversion copy failed. svn: Commit failed (details follow): svn: CHECKOUT /isource/svnroot/scm_uplane/!svn/bln/93 failed Build step 'Perform Subversion tagging on successful build' marked build as failure Finished: SUCCESS
One hint is that access through !svn/bln is not possible in our servers. But at the same time it is confusing how the plugin works sometimes.
Attachments
Activity
The exclamation mark is not added by me. I guess it is done by the SVNRepository class used by the SVN Tagging code.
As per documentation, to access SVN for specific revisions, it is needed to provide url in that format.
Another observation is that, the random failures happen only when deletion of the existing tag is performed. When this deletion happens, the repository revision goes up by one revision and then the tagging fails.
Is it needed that an SVN update is done within the working copy before attempting a copyClient.doCopy operation within the tagging plugin?
Update. The root cause seems to be the delays from the SVN server in Enterprise environment with multiple servers (master-slave). As a workaround, I introduced a slight delay in code after the deletion operation as well as after the creation operation (this is needed when other jobs are called after completion of this job). I also made it as a configurable value for the tagging plugin. If you think it is useful, you can add this to the main release.
Code changes are attached to this issue as diffs.zip
Hi,
Can you get the log file from svn server? I suspect the existence of exclamation mark in the path may confuse the server. Can you get rid of it and see if it works successfully?
I can't do any fix as the information is limited and the error seems to be intermittent.
HTH,