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

Make "effective client name" unique for the buildNode, not for the slave host

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Component/s: perforce-plugin
    • Labels:
      None
    • Environment:
      any where more than 1 slave is running on a remote computer
    • Similar Issues:

      Description

      The "effective client name" of a remote slave is currently:
      p4Client

      {value of "Workspace (client)" in the GUI}

      + hostname

      P4 will behave badly if there is more than one slave running on that remote host that can execute a given job.

      Proposed fix is to insert the following line after 848 of PerforceSCM.java
      p4Client += "-" + buildNode.getNodeName().hashCode();

      This will guarantee a unique but repeatable client name for each slave running on a remote computer regardless of the number of slaves.

        Attachments

          Activity

            People

            • Assignee:
              mikeryan4 mikeryan4
              Reporter:
              mikeryan4 mikeryan4
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: