I would like to suggest that this plugin supports more than one tag being placed
against a project. The use case is a simple one, i have a nightly build that
runs an exhaustive set of test suites and a bunch of analysers. I want this
build to be able to use the 'last successful' code base to work on. The CI
builds that run through out the day are a great candidate for creating the
lastSuccessful tag. However those CI builds also need to tag themselves with
their build number as QA and testing grab those from time to time and we need to
be able to replicate them. A simple solution for this would be to allow a build
to tag itself in more than one way. Note we do not keep the CI builds for very
long as they use a lot of space, therefore it is not possible to rely upon
hudson's historical list to find out the SVN revision that was used for a
specific build, this is the reason we are tagging each successful build with its
build number. Just a shame i cant also get the last successful build to also tag
itself as just that, the last successful.