When using the multi-job plugin to instruct a child job to run on a specified node, the child job cannot be rebuilt using the rebuild plugin.
When the job is rebuilt, the value of the NodeChoice field is populated on the screen however this is not read in by the NodeLabel plugin. The job then hangs in the queue with the status "(pending—Waiting for next available executor)".
If the child job is built directly without a parent job, the rebuild successfully reads the Node label and then runs on the given node.
Looking at the difference in the HTML, the input field for the node choice has a differing name on scendario 1 against scenario two:
Scenario 1 (failed):
Scenario 2 (successful):