Re: (Hudson) Issue #167 - SVN Update not working

> So if your build commits a change or if you manually do so, that needs
> to provide credential on its own, and that happens outside Hudson. IOW,
> as far as Hudson is concerned, all it needs is the ability to check out
> a workspace.
>
> There might be other use cases where one needs to specify the user name,
> and if so I'd like to hear that, but this one doesn't apply, I think.

Examples of use cases would include ANY use case involving
non-anonymous access to a source-control repository.  I should be able
to specify, at any time I need to, which username is used when Hudson
accesses a repository, and I shouldn't have to wait until that
username doesn't work anymore before I am allowed to do that. That's a
basic feature I would expect from any system that connects to a
source-control repository in a non-anonymous way.