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 . 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.
Originally reported by 
jglick, imported from: “Took…on master” shown for a build which ran on a slave which was since deleted
- assignee: jglick
- status: Resolved
- priority: Minor
- component(s): core
- label(s): cloud, slave
- resolution: Fixed
- resolved: 2012-09-04T21:28:31+00:00
- votes: 0
- watchers: 3
- imported: 2025-11-24
Raw content of original issue
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.
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 . 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.
Originally reported by
jglick, imported from: “Took…on master” shown for a build which ran on a slave which was since deleted
Raw content of original issue
1.424