After updating Jenkins to above version and the Multijob plugin from 1.30 to 1.32, when triggering a subjob which has been disabled, the output changed from

    >> Job status: Skipping [XXX]. This subjob has been disabled.

to

 Starting build job XXX.
java.lang.NullPointerException

However, it doesn't result in a failing job, thus the low severity.

Please restore previous behaviour since this message is just confusing while the former one clearly told what was going on.