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

Unable to sync to perforce on a MAC

    Details

    • Similar Issues:

      Description

      Hi,

      Since updating to the latest version of Jenkins (1.535) and the perforce plugin (1.3.26) I get the following error:

      Using remote perforce client: BuildMachine_PAULS-MAC-MINI
      [workspace] $ /Applications/p4 workspace -o BuildMachine_PAULS-MAC-MINI

          • Perforce client workspace 'BuildMachine_PAULS-MAC-MINI' doesn't exist.
          • Please create it, or allow Jenkins to manage clients on it's own.
          • If the client name mentioned above is not what you expected,
          • check your 'Client name format for slaves' advanced config option.
            ERROR: Error accessing perforce workspace.

      My project is a matrix project building on both a Mac and a PC. The PC build works fine, the above error is on the Mac. The matrix contains 80 possible configurations, so due to the license limitations on Perforce I can't create a separate workspace for each config. Instead, I have one workspace for PC and one for Mac. This has worked fine so far.

      The workspace named in the output above does exist, and when the command line was entered manually on the build machine, it worked as expected. The Mac slave is connected to the Windows master using the java Jenkins slave agent.

      Please let me know if you need any additional information.
      Kind regards,
      Charles

        Attachments

          Activity

          Hide
          rpetti Rob Petti added a comment -

          Do you have global timeouts set?

          Show
          rpetti Rob Petti added a comment - Do you have global timeouts set?
          Hide
          charles_blessing Charles Blessing added a comment -

          Hi Rob,

          Where might I find that option? You'll have to forgive me, I've only been using Jenkins for a few months and there are still plenty of options I don't fully understand.

          Kind regards,
          Charles

          Show
          charles_blessing Charles Blessing added a comment - Hi Rob, Where might I find that option? You'll have to forgive me, I've only been using Jenkins for a few months and there are still plenty of options I don't fully understand. Kind regards, Charles
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          You can find timeouts on Jenkins global configuration page (${JENKINS_URL}/configure).

          BTW, have you enabled a "Let Jenkins Create Workspace" checkbox?

          Show
          oleg_nenashev Oleg Nenashev added a comment - You can find timeouts on Jenkins global configuration page (${JENKINS_URL}/configure). BTW, have you enabled a "Let Jenkins Create Workspace" checkbox?
          Hide
          rpetti Rob Petti added a comment -

          I suspect the tek42 api is doing something weird here. It's reporting a workspace as new even though it already exists. Can you please check to make sure the workspace spec on the perforce server has an 'Access:' field that is populated with a date & time?

          Show
          rpetti Rob Petti added a comment - I suspect the tek42 api is doing something weird here. It's reporting a workspace as new even though it already exists. Can you please check to make sure the workspace spec on the perforce server has an 'Access:' field that is populated with a date & time?
          Hide
          charles_blessing Charles Blessing added a comment -

          I'm afraid this appears to have been a false alarm. By unhappy coincidence, all of our IP addresses changed on the same day as I updated. This meant that the server had a new address and the hard-coded IP address was pointing to the wrong computer. The actual error was that the server could not be contacted, but this manifested in a misleading error message.

          When I entered the command on the command line, it used the P4 environment variable which pointed to the server by name, and therefore worked fine.

          Everything is working fine now - although it would be nice to get the error message to be more reflective of the actual problem.

          Show
          charles_blessing Charles Blessing added a comment - I'm afraid this appears to have been a false alarm. By unhappy coincidence, all of our IP addresses changed on the same day as I updated. This meant that the server had a new address and the hard-coded IP address was pointing to the wrong computer. The actual error was that the server could not be contacted, but this manifested in a misleading error message. When I entered the command on the command line, it used the P4 environment variable which pointed to the server by name, and therefore worked fine. Everything is working fine now - although it would be nice to get the error message to be more reflective of the actual problem.
          Hide
          dboyce_bc David Boyce added a comment -

          IMO, this issue should now be resolved as 'Not a Defect' and a fresh issue raised for the error message request.

          Show
          dboyce_bc David Boyce added a comment - IMO, this issue should now be resolved as 'Not a Defect' and a fresh issue raised for the error message request.
          Hide
          rpetti Rob Petti added a comment -

          Feel free to close any other issues you feel should be closed.

          Show
          rpetti Rob Petti added a comment - Feel free to close any other issues you feel should be closed.

            People

            • Assignee:
              Unassigned
              Reporter:
              charles_blessing Charles Blessing
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: