You can use:

Index: src/main/java/hudson/plugins/svn_tag/SvnTagPlugin.java
===================================================================
— src/main/java/hudson/plugins/svn_tag/SvnTagPlugin.java (revision 21844)
+++ src/main/java/hudson/plugins/svn_tag/SvnTagPlugin.java (working copy)
@@ -70,7 +70,8 @@
String tagBaseURLStr, String tagComment) {
PrintStream logger = buildListener.getLogger();

• if (!Result.SUCCESS.equals(abstractBuild.getResult())) {
  + if (Result.FAILURE.equals(abstractBuild.getResult()) ||
  + Result.ABORTED.equals(abstractBuild.getResult())) {
  logger.println("No Subversion tagging for unsuccessful build. ");

return true;

Hi,

Thank you for the enhancement idea and I'd love to add the feature, but it may not be the hightest priority. I'll lower the priority and it would be nice if you can send me the patch containing GUI modifications as well as the diff above so I can merge to the code.

I would consider the current behaviour to be a bug, the jenkins wiki at https://wiki.jenkins-ci.org/display/JENKINS/Terminology says:

Unstable build: A build is unstable if it was built successfully and one or more publishers report it unstable. For example if the JUnit publisher is configured and a test fails then the build will be marked unstable.

Successful build: A build is successful when the compilation reported no errors.

As I understand this, unstable builds are also always successful builds. So the svn-tagging plugin should by definition tag unstable builds. Since it claims on https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Tagging+Plugin

What does this do?
This plugin automatically performs subversion tagging (technically speaking svn copy) on successful build.

Also, if my last build was unstable and I'm adding 'lastSuccessfulBuild' to my job-url, I get this unstable build with a yellow ball. If I'm using 'lastStableBuild', I get an earlier build with a blue ball.