[ 
https://issues.jenkins-ci.org/browse/JENKINS-12934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Lillevold updated JENKINS-12934:
--------------------------------------

       Priority: Critical  (was: Blocker)
    Description: 
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


  was:
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 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)
The job module have the following repo: 
https://svn.myserver.com/svn/repo/folder1/folder2/trunk
The svn-tag plugin is configured with:
https://svn.myserver.com/svn/repo/folder1/folder2/tags/${env['BUILD_VERSION']}

Remote Module Location: 
https://svn.myserver.com/svn/repo/folder1/folder2/trunk@2254.
Tag Base URL: https://svn.myserver.com/svn/repo/folder1/folder2/tags/0.0.3.2254.
There was no old tag at 
https://svn.myserver.com/svn/repo/folder1/folder2/tags/0.0.3.2254.
Subversion copy failed. svn: File not found: revision 2254, path 
'/folder1/folder2/trunk/folder1/folder2/trunk'
svn: '/svn/repo/!svn/bc/2254/folder1/folder2/trunk' path not found: 404 Not 
Found (https://svn.myserver.com)
Build step 'Perform Subversion tagging on successful build' marked build as 
failure



Fixed the actual folder beneath repo level, and added that my folder includes a 
'.' in case this has any significance. I have tried with other folders with 
names that do not contain '.' with same results though.
                
> 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

        

Reply via email to