Definitely need a resume disable capability. I'd love a global option, but a per job option is also not a crime. There are times when you know your workspace and what your job is doing will not be viable for resumption even if Jenkins can, in theory resume your build. The resumes will just fail or worse lead to red-herring issues. Yes, people should create stateless build steps with always clean thinking but that's just not reality at scale. Having a disable resume option would be handy.
Second, if you are working in a situation where your workspace, or build nodes are ephemeral, resume literally breaks jenkins. The resume feature locks to the precise name of the comptue/build slave. Which in a ephemeral state (think mesos/kubernetes/docker plugins, or jclouds and dynamically named slaves), when jenkins is restarted that build slave no longer exists. The job sits in the queue waiting for the slave to come online, but it never does. Because it's resume is using the slave name, not the "label" tied to the actual job, the act of being in the queue never triggers a the dynamic provisioner (jclouds) to create a new slave. And the job hangs indefinitely.
We see evidence that these resume states can also cause thread locking on the build queue itself which then prevents any jobs from queuing at all. We have to go through quite the arduous process to manually clean the jenkins file system to prevent builds from requeing.
If you won't provide s disable resume feature, t hen at least tell us the logic for how Jenkins decides which jobs need to be resumed so we can properly clean up markers jenkins looks for on the file system to tell it to requeue.
It seems to be a combination of jenkins home xml files as well as some file state inside the Jobs folder, (jobs/JobName/builds/#/workflow/....). But I don't know exactly what.
Another option could be to wrap "node" blocks with "Resume from here" rather than resume from inside a node block. I suppose we could try putting the "node" call inside a function marked with @NonCPS but that seems extreme and may have unexpected results and I doubt I could get all my users to follow that convention anyway.