[
https://issues.jenkins-ci.org/browse/JENKINS-12934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160496#comment-160496
]
Martin Arends commented on JENKINS-12934:
-----------------------------------------
same issue here with this setup:
repo-url:
https://aaa.bb/svn/project/theme/meis-intra-2/branches/release
svn-tag-config:
../tags/build/${env['BUILD_TAG']}
and I'm getting this:
no change for https://aaa.bb/svn/project/theme/meis-intra-2/branches/release
since the previous build
Remote Module Location:
https://aaa.bb/svn/project/theme/meis-intra-2/branches/release@2228.
Tag Base URL:
https://aaa.bb/svn/project/theme/meis-intra-2/tags/build/jenkins-test.a1.svn-taggging-3.
There was no old tag at ../tags/build/jenkins-test.a1.svn-taggging-3.
Subversion copy failed. svn: File not found: revision 2228, path
'/theme/meis-intra-2/branches/release/theme/meis-intra-2/branches/release'
svn: '/svn/project/!svn/bc/2228/theme/meis-intra-2/branches/release' path not
found: 404 Not Found (https://aaa.bb)
Build step 'Perform Subversion tagging on successful build' marked build as
failure
I'm on win 2003 server, jenkins 1.455 and svn 1.7; as Peter mentioned,
everything worked fine a few weeks ago.
> Subversion Tag plugin tries to copy from invalid source path
> ------------------------------------------------------------
>
> Key: JENKINS-12934
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12934
> Project: Jenkins
> Issue Type: Bug
> Components: plugin, subversion
> Affects Versions: current
> Environment: Windows Server 2008 R2.
> Jenkins installed as Windows Service.
> Reporter: Peter Lillevold
> Priority: Critical
> Labels: jenkins, plugin, subversion, tag
>
> Last week the subversion tagging plugin stopped working, and I have so far
> not been able to pinpoint the source of this error.
> This bug is a showstopper for us since the tags are used in other jobs.
> The job module have Subversion SCM set up with the following repo:
> https://svn.myserver.com/svn/repo/folder1.sub/trunk
> The svn-tag plugin is configured with:
> https://svn.myserver.com/svn/repo/folder1.sub/tags/${env['BUILD_VERSION']}
> The error message from the plugin shows that apparently it tries to copy from
> an invalid source path.
> (note: I have obfuscated url names, but otherwise the number of parts are the
> same)
> Remote Module Location:
> https://svn.myserver.com/svn/repo/folder1.sub/trunk@2254.
> Tag Base URL: https://svn.myserver.com/svn/repo/folder1.sub/tags/0.0.3.2254.
> There was no old tag at
> https://svn.myserver.com/svn/repo/folder1.sub/tags/0.0.3.2254.
> Subversion copy failed. svn: File not found: revision 2254, path
> '/folder1.sub/trunk/folder1.sub/trunk'
> svn: '/svn/repo/!svn/bc/2254/folder1.sub/trunk' path not found: 404 Not Found
> (https://svn.myserver.com)
> Build step 'Perform Subversion tagging on successful build' marked build as
> failure
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
