[
https://issues.jenkins-ci.org/browse/JENKINS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
pjdarton resolved JENKINS-3197.
-------------------------------
Resolution: Fixed
The changes done as part of JENKINS-9629 effectively resolves this issue, in
that it prevents logins from interfering any more than necessary.
> RFE: Use AccuRev server without doing logins
> --------------------------------------------
>
> Key: JENKINS-3197
> URL: https://issues.jenkins-ci.org/browse/JENKINS-3197
> Project: Jenkins
> Issue Type: Improvement
> Components: accurev
> Affects Versions: current
> Environment: Platform: All, OS: All
> Reporter: vessel
> Assignee: Scott Tatum
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
