I can see that another of our Jenkins may be recovering, by creating the file. However, could Jenkins then not throw an exception? It could handle the situation more gracefully
WARNING: Failed to parse the build number in the permalink cache:c:\jenkins\jobs\hello_world\builds\lastSuccessfulBuild java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at jenkins.model.PeepholePermalink.resolve(PeepholePermalink.java:92) at hudson.model.Job.getLastSuccessfulBuild(Job.java:888) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectIm pl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
WARNING: Failed to parse the build number in the permalink cache:c:\jenkins\jobs\hello_world\builds\lastStableBuild java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at jenkins.model.PeepholePermalink.resolve(PeepholePermalink.java:92) at jenkins.model.PeepholePermalink$RunListenerImpl.onCompleted(PeepholePermalink.java:233) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199) at hudson.model.Run.execute(Run.java:1786) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374)
|