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

NODE_NAME not defined for master node

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: core
    • Labels:
      None
    • Environment:
      Windows Server 2003 master and slaves
    • Similar Issues:

      Description

      I was trying to setup my Clearcase views for my nodes based on the ${NODE_NAME} variable, so that each slave would have a unique view name. ${NODE_NAME} is empty on the master, so I cannot use it to create view on the master and have to hard code the view path for each slave, making it so I can't move builds between nodes easily. I have specific requirements to set a custom workspace based on the NODE_NAME.

        Attachments

          Issue Links

            Activity

            Hide
            slide_o_mix Alex Earl added a comment -

            I am seeing this issue again as well. I'll see what I can do to dig up the reason.

            Show
            slide_o_mix Alex Earl added a comment - I am seeing this issue again as well. I'll see what I can do to dig up the reason.
            Hide
            slide_o_mix Alex Earl added a comment -

            Seems like it was probably something in 9b74a88 that caused the issue

            Show
            slide_o_mix Alex Earl added a comment - Seems like it was probably something in 9b74a88 that caused the issue
            Hide
            bruce Dirk Kuypers added a comment -

            Ok, I am back from almost no internet holidays and as I don't understand how to interpret Alex' 9b74a88 (and as I do not know if my personal response email reached him) I will write a small comment here: I think the problem was introduced with 1.527, at least since then I am stuck with 1.526. I opened JENKINS-19222 describing my problems. From the changelog of 1.527 I guess the cause could be JENKINS-19042.

            Show
            bruce Dirk Kuypers added a comment - Ok, I am back from almost no internet holidays and as I don't understand how to interpret Alex' 9b74a88 (and as I do not know if my personal response email reached him) I will write a small comment here: I think the problem was introduced with 1.527, at least since then I am stuck with 1.526. I opened JENKINS-19222 describing my problems. From the changelog of 1.527 I guess the cause could be JENKINS-19042 .
            Hide
            slide_o_mix Alex Earl added a comment -

            @Dirk, the value I posted is the commit ID in Git that I think possibly caused the issue.

            Show
            slide_o_mix Alex Earl added a comment - @Dirk, the value I posted is the commit ID in Git that I think possibly caused the issue.
            Hide
            danielbeck Daniel Beck added a comment -

            Resolving this as fixed again. Whatever goes on with 1.52x+ is a different issue with the same symptoms – it doesn't happen on a pristine instance – and seems better tracked as JENKINS-19222.

            Show
            danielbeck Daniel Beck added a comment - Resolving this as fixed again. Whatever goes on with 1.52x+ is a different issue with the same symptoms – it doesn't happen on a pristine instance – and seems better tracked as JENKINS-19222 .

              People

              • Assignee:
                kohsuke Kohsuke Kawaguchi
                Reporter:
                slide_o_mix Alex Earl
              • Votes:
                1 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: