-
Bug
-
Resolution: Unresolved
-
Minor
-
None
I'm unraveling a problem with shared library global variables barfing when you call them with named parameters rather than a list of unnamed parameters (which I'll open a JIRA about once I nail it down better) but annoyingly, such errors are just silently swallowed in a Declarative Pipeline. This, unsurprisingly, is a bug.
- is duplicated by
-
JENKINS-44059 Jenkins executes custom declarative pipeline step even though call signature is wrong without error
-
- Resolved
-