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

“Took…on master” shown for a build which ran on a slave which was since deleted

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • 1.424

      If you run a build on a slave, then delete the slave node and revisit the build page, it will claim to have been built on master even though build.xml says otherwise in <builtOn>. The reason is that node.jelly takes a Node rather than a String.

      A corner case for dumb slaves, but quite common when using a cloud plugin, and rather confusing.

          [JENKINS-15042] “Took…on master” shown for a build which ran on a slave which was since deleted

          Jesse Glick created issue -
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 145761 ] New: JNJira + In-Review [ 191618 ]

            jglick Jesse Glick
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: