Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-57202

p4 workspace -o "No output for" after upgrade mac slave to 10.13

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Not A Defect
    • Component/s: p4-plugin
    • Labels:
      None
    • Environment:
      windows master / MacOS slave - latest Jenkins version
    • Similar Issues:

      Description

      My windows/mac jobs ran fine. For building some Botan lib on macOS slave, i had to upgrade Xcode, then macOS from macOS 10.10 to 10.13.
      Afterwards, i noticed that the jenkins job build fails with the error 'no output for p4'.
      In pre-build i execute p4 commands ok (correct output), but all of a sudden Jenkins then performs p4 workspace -o <workspace> 
      and this fails with error 
      Caught exception communicating with perforce. No output for: p4 workspace -o ...

      That command runs fine when run from terminal command window on mac slave; apparently not within Jenkins job.

       

      >>>>
      12:09:40 Using remote perforce client: <workspace name>
      12:09:40 [<computername>] $ p4 workspace -o <workspace name>
      12:09:40 Caught exception communicating with perforce. No output for: p4 workspace -o <workspace name> com.tek42.perforce.PerforceException: No output for: p4 workspace -o <workspace name>
      12:09:40 at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:409)
      12:09:40 at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:302)
      12:09:40 at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61)
      .....
      <<<<<

       

       

        Attachments

          Activity

          Hide
          p4karl Karl Wirth added a comment -

          Hi bav ver,

          Thanks for reporting this. One of our developers used to run 10.13 and now is on 10.14 so we know that build slaves used to work on 10.13. 

          Can you please try making sure that the build slave has been included in the disk access privacy policy. If that doesn't help can you try disabling the Firewall to check if that is the problem.

           

          Thanks in advance.

          Show
          p4karl Karl Wirth added a comment - Hi bav ver , Thanks for reporting this. One of our developers used to run 10.13 and now is on 10.14 so we know that build slaves used to work on 10.13.  Can you please try making sure that the build slave has been included in the disk access privacy policy. If that doesn't help can you try disabling the Firewall to check if that is the problem.   Thanks in advance.
          Hide
          bav bav ver added a comment - - edited

          Hi Karl Wirth 
          Bottom line, i had to switch from 'perforce' to 'perforce software' using the p4 plugin.
          There i had to create Perforce credential. This Kind was not available first, but had to be configured first in Manage Jenkins - Configure Credentials; then i was able to create a Perforce user password credential and apply to the mac build job.
          Now the build is progressing on both windows and mac.

          Show
          bav bav ver added a comment - - edited Hi Karl Wirth   Bottom line, i had to switch from 'perforce' to 'perforce software' using the p4 plugin. There i had to create Perforce credential. This Kind was not available first, but had to be configured first in Manage Jenkins - Configure Credentials; then i was able to create a Perforce user password credential and apply to the mac build job. Now the build is progressing on both windows and mac.
          Hide
          p4karl Karl Wirth added a comment -

          Hi bav ver. Is it OK if I contact you directly so we can discuss further offline?

          Show
          p4karl Karl Wirth added a comment - Hi bav ver . Is it OK if I contact you directly so we can discuss further offline?
          Hide
          bav bav ver added a comment -

          So problem is solved now

          Show
          bav bav ver added a comment - So problem is solved now
          Hide
          p4karl Karl Wirth added a comment -

          Hi bav ver. Thanks for the confirmation and great that you resolved it. The 'perforce' plugin was the old one developed by one of the Jenkins community:

          https://wiki.jenkins.io/display/JENKINS/Perforce+Plugin

          and the new one was developed by staff at Perforce:

          https://wiki.jenkins.io/display/JENKINS/P4+Plugin

          It may be that there was something in the old plugins or it's dependency that broke with the 10.13 upgrade.

          Thanks again,

          Karl

           

          Show
          p4karl Karl Wirth added a comment - Hi bav ver . Thanks for the confirmation and great that you resolved it. The 'perforce' plugin was the old one developed by one of the Jenkins community: https://wiki.jenkins.io/display/JENKINS/Perforce+Plugin and the new one was developed by staff at Perforce: https://wiki.jenkins.io/display/JENKINS/P4+Plugin It may be that there was something in the old plugins or it's dependency that broke with the 10.13 upgrade. Thanks again, Karl  
          Hide
          p4karl Karl Wirth added a comment -

          Not a defect in new plugin but may be a problem in the legacy plugin.

          Show
          p4karl Karl Wirth added a comment - Not a defect in new plugin but may be a problem in the legacy plugin.

            People

            • Assignee:
              Unassigned
              Reporter:
              bav bav ver
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: