Running Jenkins 1.460
To reproduce:
Two different jobs say auniquejob and auniquejob2 are restricted to run based on the same label, say foo.
There is a single node (hudson-slave-b in the attached screenshot) labeled foo with one executor. Build both jobs.
While the first job is running, the second is waiting in the queue for the executor to free up. While it is in this state, its job xml is malformed. The first attached screenshot shows what I get if I hover over the job name in the queue. If I navigate to <jenkins>/job/<jobname>/api/xml, I get an error screen.
When the first job finishes, the second does get scheduled properly onto the same executor that the first one used.
The error does not occur if a second node is available with the same label and that second node is offline. This is our workaround.

Priority would probably be minor for most people but we do a ton of dynamic job manipulation via script and have scripts looking at job xmls all the time. So for us this would be a blocker, except for the workaround.

Guessing core component but screenshot showing list of plugins is also attached - is there an easy way to get a text version of this?