Plugin that deploys itself automatically on slaves should only deploy if the slave has some specific labels.
The use case here is that not all our slaves might be related to the plugin it wants to be installed on.
The labels could start with "jenkins-plugin-" so we know it's for a jenkins plugin and it could add the plugin name after that prefix so we know which plugin it is.
This can be applied to hadoop as well as ChromeDriver unless it uses the configuration of selenium grid v2 "exclude pattern" configuration which is not the case in the trunk.
Unless this feature can be controlled somewhere that I've not seen, this is pretty bad to install some stuff on machines that don't need it or will fail to work because the distant machine is not compatible with the plugin