com.tek42.perforce.PerforceException: No output for: p4 workspace -o SOME_CLIENT

Jenkins JIRA | austje | 7 years ago
  1. 0

    It seems that the perforce plugin finds the p4 executable by using the system PATH variable, rather than referencing the value of "Path to p4 executable" listed on the job configuration page. This is misleading and makes errors difficult to debug. In our situation, we updated the ~/.bashrc file on our nodes and removed the path to the p4 executable from our PATH variable. Upon restarting the nodes, we got the following error for all of our builds that used perforce: Started by user vaustje Building remotely on node4 Using remote perforce client: SOME_CLIENT Caught exception communicating with perforce. No output for: p4 workspace -o SOME_CLIENT com.tek42.perforce.PerforceException: No output for: p4 workspace -o SOME_CLIENT at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:314) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:53) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:671) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:294) at hudson.model.AbstractProject.checkout(AbstractProject.java:1003) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:428) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:376) at hudson.model.Run.run(Run.java:1174) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:303) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:123) Finished: FAILURE At first we thought that there was an error running the p4 command on the remote machine, but it turned out that p4 was not getting executed at all. The value of "Path to p4 executable" was set correctly in our job configuration. However it was not until we updated the PATH variable in our bashrc and restarted the nodes that the issue was fixed.

    Jenkins JIRA | 7 years ago | austje
    com.tek42.perforce.PerforceException: No output for: p4 workspace -o SOME_CLIENT
  2. 0

    It seems that the perforce plugin finds the p4 executable by using the system PATH variable, rather than referencing the value of "Path to p4 executable" listed on the job configuration page. This is misleading and makes errors difficult to debug. In our situation, we updated the ~/.bashrc file on our nodes and removed the path to the p4 executable from our PATH variable. Upon restarting the nodes, we got the following error for all of our builds that used perforce: Started by user vaustje Building remotely on node4 Using remote perforce client: SOME_CLIENT Caught exception communicating with perforce. No output for: p4 workspace -o SOME_CLIENT com.tek42.perforce.PerforceException: No output for: p4 workspace -o SOME_CLIENT at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:314) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:53) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:671) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:294) at hudson.model.AbstractProject.checkout(AbstractProject.java:1003) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:428) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:376) at hudson.model.Run.run(Run.java:1174) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:303) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:123) Finished: FAILURE At first we thought that there was an error running the p4 command on the remote machine, but it turned out that p4 was not getting executed at all. The value of "Path to p4 executable" was set correctly in our job configuration. However it was not until we updated the PATH variable in our bashrc and restarted the nodes that the issue was fixed.

    Jenkins JIRA | 7 years ago | austje
    com.tek42.perforce.PerforceException: No output for: p4 workspace -o SOME_CLIENT
  3. 0

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

    Google Groups | 3 years ago | Jason Murray
    com.tek42.perforce.PerforceException: No output for: workspace -o hudson-deploy-client--1606248362
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Perforce Plugin - Jenkins - Jenkins Wiki

    jenkins-ci.org | 3 months ago
    com.tek42.perforce.PerforceException: No output for: p4 workspace -o HUDSON-BUILD
  6. 0

    Perforce Plugin - hudson - Hudson Wiki

    hudson-ci.org | 3 months ago
    com.tek42.perforce.PerforceException: No output for: C:\Program Files (x86)\Perforce\p4.exe workspace -o YYY

    1 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.tek42.perforce.PerforceException

      No output for: p4 workspace -o SOME_CLIENT

      at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse()
    2. com.tek42.perforce
      Workspaces.getWorkspace
      1. com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:314)
      2. com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:53)
      2 frames
    3. hudson.plugins.perforce
      PerforceSCM.checkout
      1. hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:671)
      2. hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:294)
      2 frames
    4. Hudson
      Run.run
      1. hudson.model.AbstractProject.checkout(AbstractProject.java:1003)
      2. hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:428)
      3. hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:376)
      4. hudson.model.Run.run(Run.java:1174)
      4 frames
    5. Hudson Maven Embedder
      MavenModuleSetBuild.run
      1. hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:303)
      1 frame
    6. Hudson
      Executor.run
      1. hudson.model.ResourceController.execute(ResourceController.java:88)
      2. hudson.model.Executor.run(Executor.java:123)
      2 frames