-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 2.440.2
authorize-project:1.7.1
blueocean:1.27.11
build-name-setter:2.4.2
build-timeout:1.32
build-user-vars-plugin:1.9
copyartifact:722.v0662a_9b_e22a_c
ec2:1648.vf3d852e00486
embeddable-build-status:467.v4a_954796e45d
envinject:2.908.v66a_774b_31d93
file-operations:214.v2e7dc7f25757
jobConfigHistory:1229.v3039470161a_d
markdown-formatter:167.v8a_428ca_49f89
matrix-auth:3.2.2
p4:1.15.1
parameter-separator:166.vd0120849b_386
parameterized-scheduler:262.v00f3d90585cc
permissive-script-security:0.7
pipeline-stage-view:2.34
pipeline-utility-steps:2.16.2
rebuild:330.v645b_7df10e2a_
resource-disposer:0.23
slack:684.v833089650554
ssh-steps:2.0.68.va_d21a_12a_6476
throttle-concurrents:2.14
timestamper:1.26
warnings-ng:11.2.2
workflow-aggregator:596.v8c21c963d92dJenkins 2.440.2 authorize-project:1.7.1 blueocean:1.27.11 build-name-setter:2.4.2 build-timeout:1.32 build-user-vars-plugin:1.9 copyartifact:722.v0662a_9b_e22a_c ec2:1648.vf3d852e00486 embeddable-build-status:467.v4a_954796e45d envinject:2.908.v66a_774b_31d93 file-operations:214.v2e7dc7f25757 jobConfigHistory:1229.v3039470161a_d markdown-formatter:167.v8a_428ca_49f89 matrix-auth:3.2.2 p4:1.15.1 parameter-separator:166.vd0120849b_386 parameterized-scheduler:262.v00f3d90585cc permissive-script-security:0.7 pipeline-stage-view:2.34 pipeline-utility-steps:2.16.2 rebuild:330.v645b_7df10e2a_ resource-disposer:0.23 slack:684.v833089650554 ssh-steps:2.0.68.va_d21a_12a_6476 throttle-concurrents:2.14 timestamper:1.26 warnings-ng:11.2.2 workflow-aggregator:596.v8c21c963d92d
I believe I am running into the same issue as reported here, but wanted to add some information which may lead to a resolution: https://issues.jenkins.io/browse/JENKINS-52060
In that issue it was found that the server was rejecting a call to "p4 info" when called unauthenticated which as commented on the other issue P4JAVA always does before authentication.
I believe I am attempting to connect to the same semi common server in my industry, if not it has near identical behaviors. I have found it does respond to p4 info unauthenticated if an appropriate user is passed into the p4 info call. It appears to be doing a user validation/error before the standard authentication requirement checks.
So if the credentials are:
P4PORT=ssl:server.network.com:1666
P4USER=John
"p4 -p $P4PORT info" will be rejected
"p4 -p $P4PORT -u $P4USER info" will be accepted as long as the specified user is a valid user on that server, even when not authenticated.
I get this is a non-standard extension on that server so I don't necessarily expect a fix from this side of things. I have reached out to them as well about not validating the user for the "info" command.
If, however, it does not hurt to change the P4JAVA call to "p4 info" right before authentication to include the user then that will likely fix my issue here.