I'm trying to make a custom release job with Hudson, starting from a Maven 2 job. By adding some pre and post release build steps I'm mostly there.
One of the requirements for the release job is that we want to either release from the trunk, using HEAD (default), or from a tag (if something is b0rked in the trunk). So this requires some human input for choosing the destination.
This is possible by using command line parameters. Thankfully, the SVN plugin recognizes the parameters and checks out from the required destination:
repository/${SVN_PATH}/${SVN_TAG} => repository/tags/last-successful/myproject-tag232

However, the Subversion tagging plugin does not know/recognize the variables when trying to copy. I'm not talking about destination variables (the tag name), for example: ${env['BUILD_ID']}. I'm talking about the source variables.

Example:
svn copy http;//source/${myvariable} http;//source/${env['BUILD_ID']}

There's also an issue with the format, the format used by the plugins is ${env['myvariable']}, which isn't recognized by the SVN plugin, which uses ${myvariable} directly.

The obvious workaround is to not use the plugin and just launch svn copy... Not nice