The whole CLI is affected as well.
I'm a bit curious because I'm aware of two different scenarios with completely different result.
I. If I use a JENKINS_HOME from the past (let's say rolling for a year), I can't hit this issue.
II. If I use a completely clean JENKINS_HOME instance (the best is a new directory, start Jenkins from the war (JENKINS_HOME=newdir java -jar jenkins.war) and follow the Jenkins install wizard), this issue manifests itself.
If I forced the argument type to java.lang.String, method encode(String, String) has found but NPE occurred because the first String input parameter was null.
The question is why is the result of expression: |