Hi,

in case there is only one AccuRev server around, it would be sufficient to have
a cronjob in the background that sets a permanent AccuRev login token ("login
-n") and then Hudson itself does not have to do logins anymore.

Currently, all of our Hudson jobs for safety do also login to AccuRev (there are
jobs that do not use the Hudson AccuRev stream configuration feature), which
means we have many many login operations every day, sometimes we get failures
because job logins interfer with Hudson logins, sometimes Hudson takes a long
time (or hangs) when Authenticating with AccuRev.

We could get rid of that if Hudson only tried to login to a server if there is a
user name specified in the AccuRev server configuration.

Thanks!
Thomas