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

$NODE_NAME empty for master, exists in $NODE_LABELS

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • None

      Made a simple job on the master with one shell execution to echo both $NODE_NAME and $NODE_LABELS. $NODE_NAME is empty but "master" is echo'd for $NODE_LABELS.

          [JENKINS-14150] $NODE_NAME empty for master, exists in $NODE_LABELS

          Seems like the same problem identified back in JENKINS-9671.

          David Ehrenberger added a comment - Seems like the same problem identified back in JENKINS-9671 .

          For what its worth, echoing the $NODE_LABELS on a slave has the form "SlaveNameIsFirst label_1 label_2" whereas on the master it is the opposite: "label_1 label_2 master"

          David Ehrenberger added a comment - For what its worth, echoing the $NODE_LABELS on a slave has the form "SlaveNameIsFirst label_1 label_2" whereas on the master it is the opposite: "label_1 label_2 master"

          James Monroe added a comment -

          I'm having the same problem using ${NODE_NAME} as the perforce workspace name. it works for slaves, but when the job gets assigned to the master, it fails to poll:
          Looking for changes...
          Using node: Jenkins
          Using master perforce client: ${NODE_NAME}
          [Jenkins] $ p4 workspace -o ${NODE_NAME}

              • Perforce client workspace '${NODE_NAME}' doesn't exist.

          James Monroe added a comment - I'm having the same problem using ${NODE_NAME} as the perforce workspace name. it works for slaves, but when the job gets assigned to the master, it fails to poll: Looking for changes... Using node: Jenkins Using master perforce client: ${NODE_NAME} [Jenkins] $ p4 workspace -o ${NODE_NAME} Perforce client workspace '${NODE_NAME}' doesn't exist.

            Unassigned Unassigned
            daehren David Ehrenberger
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: