[
https://issues.jenkins-ci.org/browse/JENKINS-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
evernat resolved JENKINS-1956.
------------------------------
Resolution: Not A Defect
I personnaly think that the default behavior should not be to overwrite an
existing svn tag and that it is right to give an error. Because overwriting a
svn tag does not seem a good practice.
Given the low vote count after more than 3 years, this issue is closed as not a
defect. You can reopen it if you feel different.
Anyway the svn-tag plugin seems to be an alternative for your use case.
> Tagging build to an existing tag causes SVN error
> -------------------------------------------------
>
> Key: JENKINS-1956
> URL: https://issues.jenkins-ci.org/browse/JENKINS-1956
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Affects Versions: current
> Environment: Platform: All, OS: All
> Reporter: smason
>
> When trying to tag a build to an existing tag I get this error:
> Tagging http://PROJECT/trunk (rev.7) to http://PROJECT/tags/uat
> Failed to tag
> org.tmatesoft.svn.core.SVNException: svn: Path 'tags/uat' already exists
> at
> org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:55)
> at
> org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:40)
> at
> org.tmatesoft.svn.core.wc.SVNCopyClient.doCopy(SVNCopyClient.java:312)
> at
> hudson.scm.SubversionTagAction$TagWorkerThread.perform(SubversionTagAction.java:167)
> at hudson.model.TaskThread.run(TaskThread.java:77)
> Completed
> I would expect behaviour similar to the svn-tag plugin instead, where if the
> tag
> already exists it is over-written (perhaps with a warning/confirmation first).
--
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
