pjdarton commented on Improvement JENKINS-10209

FYI, there was "minimise login" behavior added by JENKINS-8935, which was incorporated in 0.6.15 a long time ago, well before 0.6.27, but this issue isn't the same as that issue.
i.e. the plugin checked (using accurev info) whether or not the user is logged in, and then only logged in if the user isn't logged in already.

However, that algorithm doesn't address this issue (which is why this issue was raised separately).

This issue is all about the way the accurev server can spontaneously log you out in between accurev client commands - doing a pre-emptive "if accurev info says you're not logged in, then log in" at the start isn't enough - one needs to trap the "you're not logged in" errors from every accurev command that is done.

e.g. if the sequence is as follows:

accurev info
  if not logged in, log in
accurev show ... streams
accurev mksnap ...
accurev pop ...

then the code needs to check that the "accurev show", "accurev mksnap" and "accurev pop" commands didn't complain that the user wasn't logged in (and then login and re-issue the command if that's the case), as the login that was checked for right at the start can spontaneously expire at any point.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to