When an AccuRev server is renamed in the global system settings, configurations for existing jobs retain the old server name, and throw a NullPointerException when run:

Building in workspace /var/lib/jenkins/workspace/1.9.X.X_NIGHTLY_client
FATAL: null
java.lang.NullPointerException
at hudson.plugins.accurev.FindAccurevClientExe.invoke(FindAccurevClientExe.java:69)
at hudson.plugins.accurev.FindAccurevClientExe.invoke(FindAccurevClientExe.java:13)
at hudson.FilePath.act(FilePath.java:991)
at hudson.FilePath.act(FilePath.java:969)
at hudson.plugins.accurev.AccurevSCM.checkout(AccurevSCM.java:503)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1275)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Skipped archiving because build is not successful
[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] done
Finished: FAILURE

This continues until the server name is reverted, or the job configuration is manually updated with the new server name.

Major because:

• Can break a large number of existing jobs.
• Stack trace is quite misleading - it took me a long time to nail down the root cause of the exception.
• Zero information from the plugin is logged to jenkins.log

This case should be handled, or give a relevant error message when a job's AccuRev configuration is invalid.