Assuming you have a "build" that does this in Hudson, you should probably then configure the build to be parameterized.
You might need to augment this with the use of scripts to actually run the svn / deployment commands outside of the integrated Hudson tasks, as the Hudson tasks will typically take any "known" Hudson credentials (or even credential cache) and use those as parameters in the plugin.
Note that this might have the undesired side-effect of exposing the user's password in the log files, as Hudson won't know that this parameter should be handled "specially" in the logging.