|
||||||||
|
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.
Are you sure this isn't supported by perforce? p4port can be an rsh specification. I've found some examples in a changelog that indicate rsh formatted p4ports have been supported for a while.
Maybe this should be fixed by ssh-agent plugin instead? It certainly has been a solved problem for the git plugin:
JENKINS-12492from http://www.perforce.com/perforce/r10.2/user/relnotes.txt
Directly Invoking p4d - #2884 * **
UNIX ONLY. The p4 client program can now directly invoke
the p4d server program by setting P4PORT to "rsh: p4d -ir
root". The "rsh:" instructs the client to run the program
following the :, and the -i flag makes p4d run once with
its stdin/stdout as the communications pipe. By setting
P4PORT to "rsh:rsh host cmd" it is possible to invoke a
server on a remote machine, if "cmd" is either the invocation
of p4d or a wrapper script which does as much.
#280361 (Bugs #26753,#41870,#42313) *
'p4 -p "rsh: p4d -i -r ." passwd < password.txt' now works
properly on Windows. Additionally, marshalled invocations such as
'p4 -G login < password.txt' now work properly on Windows.
#209865 (Bug #35224) *
P4PORT=rsh: can now handle quoting of spaces on UNIX.
Use double quotes. For example, the P4CONFIG file can contain:
P4PORT=rsh: p4d -r "root directory"
and "root directory" is recognized as a single argument
(without the quotes). A " can be specified by using "". Note
that, on Windows, the whole string (after the rsh: ) is passed
to cmd.exe for handling, and must obey cmd.exe's quoting
rules.