For any plugin that forces a 64 bit version (as opposed to 32bit or none), it would be nice to link it to a 64bit limit group. Or something that disallows the situation of enforcing 64bit but assigning to 32bit machines. Why does the farm have to be so dumb? I keep fixing the same “weeds” over and over again. I can’t tell the idiotic error messages from the important ones.
b 
The “build” option is still at the plugin level, so at the moment a slave doesn’t even know a job is targeting 64 bit until it already has the job loaded. The ideal solution is to make it a job setting, which would allow it to affect job scheduling. We would also like to expose other useful settings as well, like a minimum RAM requirement. These improvements are currently targeted for 4.1, but that may change depending on how much these changes affect the job’s structure in the repository.
Cheers,