-
Bug
-
Resolution: Won't Fix
-
Minor
-
None
Steps to Reproduce: [from ntulele]
- Enable plugin for a job
- Set the following:
- Timeout strategy: Absolute
- Timeout minutes: 3
- Time-out variable: 19
- Time-out actions:
- Abort the build
- Writing the build description (& enter some text)
- Save/Apply and attempt to execute build
- Note failure with stack trace per below
- delete "19" from the Time-out variable text box
- Save/Apply & re-attempt build --> PASS
Log excerpt:
FATAL: null
java.lang.NullPointerException
at hudson.plugins.build_timeout.BuildTimeOutStrategy.hasMacros(BuildTimeOutStrategy.java:112)
at hudson.plugins.build_timeout.BuildTimeOutStrategy.expandAll(BuildTimeOutStrategy.java:108)
at hudson.plugins.build_timeout.impl.AbsoluteTimeOutStrategy.getTimeOut(AbsoluteTimeOutStrategy.java:44)
at hudson.plugins.build_timeout.BuildTimeoutWrapper$EnvironmentImpl.<init>(BuildTimeoutWrapper.java:166)
at hudson.plugins.build_timeout.BuildTimeoutWrapper.setUp(BuildTimeoutWrapper.java:211)
at hudson.model.Build$BuildExecution.doRun(Build.java:156)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
at hudson.model.Run.execute(Run.java:1738)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
from Maciej:
It happens probably because Action field was not set. I would expect from the plugin a minimal message saying which field should not be null if it is about invalid configuration.
It looks caused for "Timeout minutes" isn't set.
But that's strange:
As far as I know, you can never configure build-timeout in that way...
An empty string should be set even if you leave the field empty.
You can never have that field completely unset.
I'll test the behavior with Jenkins 1.647 and see whethet I can reproduce the problem.
Please let me know if you know the exact steps to reproduce the problem.