Incorrect Perforce executable path used

66 views
Skip to first unread message

Ash

unread,
Jun 8, 2012, 11:36:21 AM6/8/12
to Jenkins Users
I recently had to move my Jenkins Master to a new server. One the new
server, the path to Perforce changed. Under the Perforce section of
the settings, I made sure to update the path to the correct value. The
old path was /usr/bin/p4 and the new path is /usr/local/bin/p4. In
both cases, those directories are a part of the system's $PATH.

The trouble is, sometimes a job will now try and use the old path, and
I can't figure out why. Other jobs that use the same Perforce settings
have run and not failed since moving to the new p4 path. Here is one
example of the failure. There wasn't any changes to the Job
configurations or the Node configurations between yesterday and today.

Yesterday's Build
-=-=-=-=-=-=-
Started by timer
Building on master in workspace /home/jenkins/jenkins_home/jobs/Code
Churn/workspace
Using master perforce client: ddp-hudson-cc
[workspace] $ p4 workspace -o ddp-hudson-cc
[workspace] $ p4 login -p
[workspace] $ p4 -P XYZ workspace -o ddp-hudson-cc
Saving modified client ddp-hudson-cc
[workspace] $ p4 -P XYZ -s client -i
Last build changeset: 824431
...
-=-=-=-=-=-=-

Today's Build
-=-=-=-=-=-=-
Started by timer
Building on master in workspace /home/jenkins/jenkins_home/jobs/Code
Churn/workspace
Using master perforce client: ddp-hudson-cc
[workspace] $ p4 workspace -o ddp-hudson-cc
[workspace] $ p4 login -p
[workspace] $ /usr/bin/p4 login -p
Caught exception communicating with perforce. Login attempt failed:
Password invalid.com.tek42.perforce.PerforceException: Login attempt
failed: Password invalid.
at
com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:
615)
at
com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:
556)
at
com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:
372)
at
com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:
292)
at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:
61)
at
hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:
1418)
...
-=-=-=-=-=-=-

When I hit rebuild on the failed build, everything works again.

Has anyone else seen this with the Perforce plugin, or maybe some
other tool/plugin?

Jenkins 1.466
Perforce Plugin 1.3.14
Perforce P4/LINUX26X86_64/2012.1/459601 (2012/05/11)

Rob Petti

unread,
Jun 9, 2012, 10:08:40 PM6/9/12
to jenkins...@googlegroups.com
The /usr/bin/p4 is actually a hard-coded fallback in the event that the first login attempt fails, so there actually isn't anything wrong with the path configuration. It sounds more like there is a transient networking issue between the new master and your perforce server.
Reply all
Reply to author
Forward
0 new messages