when the warnings-ng plugin is loaded probably some codes like that are executed
and then that is rising a very verbose set of deprecation and security warnings plus a bunch of stack traces. luckily the module still runs - but it might cease working in some near to mid-term future.

maybe those build node console command sequence will trigger the same messages and effects.

def config = io.jenkins.plugins.analysis.warnings.groovy.ParserConfiguration.getInstance()
print config