The maven pipeline plugin in version 2.0 tries to parse an empty event spy logfile and logs error messages because of that (that is fine).

Calling withMaven() should not even try to parse any log files from the event spy if the event spy has been disabled via one of the two options available for that.

In my case I disabled the event spy via setting the environment variable JENKINS_MAVEN_AGENT_DISABLED to "true". In this case no valid log file is created and the MavenSpyLogProcessor can't process it so it should not even try it.