why does Jenkins Subversion Tagging Plugin delete old tags

Question

I have a job that builds the trunk, and uses the plugin "Subversion Tagging" to create a tag after the build is complete.

I'm wondering why it deletes the old tags, and that there's no option to stop this from happening. i.e. one tag is created and the previous one is deleted.

This may be a question regarding svn administration procedures.

Answer 1

To answer your question: because it was designed that way.

I find that plugin quite restrictive as well, and write my own shell scripts to perform my tagging for me.

Answer 2

Those tags are still in Subversion repository history and you can always look through all of them by running svn log against the /tags path or your repository.

Answer 3

I'm using version 1.14 and this only deletes the tag which it is about to create, should it exist. So if you include e.g. ${env['BUILD_TAG']} in your tag, it will look differently on every build and old tags will not get lost that way.