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

NODE_NAME can be wrong for parallel build jobs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • core
    • None
    • Perforce depo view checkouts

      Reference JENKINS-60213 : problem is with EXECUTOR_NUMBER being updated for the P4_CLIENT. Jira report has much better details than I can provide.

       

      My situation is that the P4_CLIENT I build uses the variables "jenkins-${JOB_NAME}-${NODE_NAME}"

      The NODE_NAME is wrong a few times a night with 6 parallel builds on 6 different nodes. About 40-50 builds are queued a night, and the wrong P4_CLIENT is causing the wrong P4_CHANGELIST to be reported.

       

            Unassigned Unassigned
            tomreed81 Tom Reed
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: