Branch: refs/heads/master
Home: https://github.com/jenkinsci/perforce-plugin
Commit: 6d62f20ba9cc15929d638c9e729788817c10c59c
https://github.com/jenkinsci/perforce-plugin/commit/6d62f20ba9cc15929d638c9e729788817c10c59c
Author: Rob Petti <rpe...@autonomy.com>
Date: 2012-08-29 (Wed, 29 Aug 2012)
Changed paths:
M src/main/java/com/tek42/perforce/parse/AbstractPerforceTemplate.java
Log Message:
-----------
fixing issue with relogin during command execution
If a ticket expires or authentication otherwise fails during a command, a new
login attempt will be triggered. originally, this would result in a second '-P
<ticket>' argument to be added to the arguments list when using tickets. this
has been fixed.
Commit: bc1608098cbc4a32ee9524912ed8efd4db437d84
https://github.com/jenkinsci/perforce-plugin/commit/bc1608098cbc4a32ee9524912ed8efd4db437d84
Author: Rob Petti <rpe...@autonomy.com>
Date: 2012-08-29 (Wed, 29 Aug 2012)
Changed paths:
M src/main/java/com/tek42/perforce/parse/AbstractPerforceTemplate.java
Log Message:
-----------
use p4 login -a in order to get a ticket that works on all machines
I can really only think of one situation where not doing this might have been a
problem. If you are running a matrix build with a node label expression, the
different slaves may fight for control of a working ticket, causing relogins
during the middle of command attempts. This will prevent that by getting a
ticket that will work on all of them.
Compare:
https://github.com/jenkinsci/perforce-plugin/compare/f6038dc21337...bc1608098cbc
