-
Bug
-
Resolution: Unresolved
-
Minor
-
None
On a busy Jenkins system it can take up to 30 minutes before your job gets executed, then take several minutes to get to the step you've just added where you accidentally misspelled a parameter name to a Groovy command (sh in my case). The declarative-linter idea is great but something that can pick up any errors that are guaranteed to break your build when it finally executed would make a huge difference.
Can you give me an example? It should be doing this for steps - not for shared library functions, but it should be verifying parameter names for step classes invoked from the Jenkinsfile.