Perforce Plugin - Can't get plugin to work on remote client

899 views
Skip to first unread message

Jason Murray

unread,
Jan 29, 2014, 6:53:15 PM1/29/14
to jenkins...@googlegroups.com
I am trying to use the Perforce plugin on a Linux slave and am getting an exception. 

Before I file a bug I wanted to see if there was any configuration issue or compatibility problems that might be the actual cause.

The possible issue with my setup are:

1. The slave is a VM in openstack. Its IP and network communications are being managed by openstack. Perhaps something is not being configured properly which is preventing the plugin from working.

2. We are able to use the latest version of the p4 client, but our server is old.

Client : Rev. P4/LINUX26X86_64/2013.1/685046 (2013/08/07).

Server version: P4D/LINUX26X86/2005.2/93627 (2006/02/14)

Jenkins: Jenkins ver. 1.547

3. The plugin fails with the following log:

Started by user anonymous
[EnvInject] - Loading node environment variables.
Building remotely on lm-nightly-deploy.openstack.lyr.is in workspace /home/hudson/workspace/perforce test
Using remote perforce client: hudson-deploy-client--1606248362
[perforce test] $  workspace -o hudson-deploy-client--1606248362
Caught exception communicating with perforce. No output for:  workspace -o hudson-deploy-client--1606248362 com.tek42.perforce.PerforceException: No output for:  workspace -o hudson-deploy-client--1606248362 
	at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:408)
	at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:301)
	at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61)
	at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1615)
	at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1576)
	at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:892)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1415)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561)
	at hudson.model.Run.execute(Run.java:1678)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)
ERROR: Unable to communicate with perforce. No output for:  workspace -o hudson-deploy-client--1606248362 
Finished: FAILURE

4. There is a jira issue that includes precisely this exception, but it was closed more than a year ago.

Ginga, Dick

unread,
Jan 30, 2014, 8:36:36 AM1/30/14
to jenkins...@googlegroups.com

Look for errors in your View definition in Jenkins. Maybe you don’t have a … at the end. Also try running that command on your slave, in your job workspace root as the user that the slave is logged in as.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Message has been deleted

Jason Murray

unread,
Feb 4, 2014, 2:29:45 PM2/4/14
to jenkins...@googlegroups.com
The view appears right.

Workspace (client): hudson-deploy-client => Unable to check workspace against depot

Let Jenkins Create Workspace:  yes
Let Jenkins Manage Workspace View: yes

View Map: //depot/projects/tools/Hammer/... //hudson-deploy-client/...

I cannot run the command locally because there is no 'workspace' command.

I have configured Jenkins to install perforce support but it does not indicate that this is being done in the log output.

This server has a p4 executable in its path.

Where would the  'workspace' executable come from if it is not loaded by Jenkins remotely?

Ginga, Dick

unread,
Feb 4, 2014, 2:30:40 PM2/4/14
to jenkins...@googlegroups.com

Ignore that error message. I always get it and it is harmless

--

Jason Murray

unread,
Feb 4, 2014, 2:33:25 PM2/4/14
to jenkins...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages