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

Concurrent builds do not work when they execute on the same node simultaneously.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: perforce-plugin
    • Labels:
      None
    • Environment:
      Perforce Plugin 1.2.7
    • Similar Issues:

      Description

      When using concurrent builds on the same node, the perforce plugin attempts to use the same client workspace for both, resulting in syncing problems.

      The plugin should be able to detect when syncing to an alternate workspace (ie. workspace@2) and adjust the name of the client accordingly to ensure it's unique.

        Attachments

          Activity

          Hide
          gramakrishnan Gangadharan Ramakrishnan added a comment -

          Any updates on this..
          We have the similar issue when running concurrent builds using perforce..

          Show
          gramakrishnan Gangadharan Ramakrishnan added a comment - Any updates on this.. We have the similar issue when running concurrent builds using perforce..
          Hide
          rpetti Rob Petti added a comment -

          Sorry, I haven't had the chance to look at it. You should be able to work around it by turning on the always force sync option.

          Show
          rpetti Rob Petti added a comment - Sorry, I haven't had the chance to look at it. You should be able to work around it by turning on the always force sync option.
          Hide
          sonofkhmer Paolo Torelli added a comment -

          Bug is still present on Perforce Plugin 1.3.17

          The correct value is used when the process starts:
          [...]
          Building remotely on jk-1070 in workspace C:\jenkins_root\workspace\build_code_new@3
          Using remote perforce client: jk-1070_build_code_new-1480515880_3
          [build_code_new@3] $ p4 workspace -o jk-1070_build_code_new-1480515880_3
          [...]

          but the environment variable is not correctly set
          C:\jenkins_root\workspace\build_code_new@3>set P4CLIENT
          P4CLIENT=jk-1070_build_code_new-1480515880

          Show
          sonofkhmer Paolo Torelli added a comment - Bug is still present on Perforce Plugin 1.3.17 The correct value is used when the process starts: [...] Building remotely on jk-1070 in workspace C:\jenkins_root\workspace\build_code_new@3 Using remote perforce client: jk-1070_build_code_new-1480515880_3 [build_code_new@3] $ p4 workspace -o jk-1070_build_code_new-1480515880_3 [...] but the environment variable is not correctly set C:\jenkins_root\workspace\build_code_new@3>set P4CLIENT P4CLIENT=jk-1070_build_code_new-1480515880
          Hide
          rpetti Rob Petti added a comment -

          It doesn't look like that would adversely affect syncing. It should be fixed now anyways.

          Show
          rpetti Rob Petti added a comment - It doesn't look like that would adversely affect syncing. It should be fixed now anyways.
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Rob Petti
          Path:
          src/main/java/hudson/plugins/perforce/PerforceSCM.java
          http://jenkins-ci.org/commit/perforce-plugin/ecbba4b82234288733fe295b8ea702a531bb8619
          Log:
          [FIXED JENKINS-10125] fixing P4CLIENT build env variable for concurrent builds

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Rob Petti Path: src/main/java/hudson/plugins/perforce/PerforceSCM.java http://jenkins-ci.org/commit/perforce-plugin/ecbba4b82234288733fe295b8ea702a531bb8619 Log: [FIXED JENKINS-10125] fixing P4CLIENT build env variable for concurrent builds

            People

            • Assignee:
              rpetti Rob Petti
              Reporter:
              rpetti Rob Petti
            • Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: