We are suffering the same bug as in 277, with the same stacktrace reported by Boon Elschenbroich in https://issues.jenkins.io/browse/JENKINS-67862 

The bug is risen when we call a parameterized managed script and one of the parameters is referring a variable without braces.

note: we have other parameterized managed scripts referring variables without braces but only this particular one is rising the exception, AFAWK at the time of this comment.

Workaround:

Add braces to the variable

Thanks for the info.

In my case string 1 is a parameter value which should be substituted (token_response) and string 2 is a text string - which also contains $, but should not be substituted.

token_response=Bearer ${$.get_authorisation.response.body.token}

If $token_response equals "Bearer ${$.get_authorisation.response.body.token}" execute command A, if $token_response equals something else execute command B.

Perhaps i need some escape characters in the string2 text box (\ before the $??).

brendanf I just ran a test with the latest with "Bearer ${$.get_authorisation.response.body.token}" as the string and it passed, (I checked that the value output was the same as input in this case). Are you sure you are on version 280?

ral_openbravo I am also not able to reproduce your issue in a test, can you please give more information?

Right, I used the non-quote version. Can you share any stack traces or anything? 

A Colleague has recreated this issue on a local jenkins install.

The following Stack trace is observed.

{{Mar 03, 2022 4:42:08 P.M. WARNING org.jenkins_ci.plugins.run_condition.BuildStepRunner logEvaluateException
Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Error processing tokens], action = [Fail the build]
org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Invalid identifier in macro
at org.jenkinsci.plugins.tokenmacro.Parser.parseIdentifier(Parser.java:210)
at org.jenkinsci.plugins.tokenmacro.Parser.parseDelimitedToken(Parser.java:148)
at org.jenkinsci.plugins.tokenmacro.Parser.parseToken(Parser.java:111)
at org.jenkinsci.plugins.tokenmacro.Parser.parse(Parser.java:87)
Caused: org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Error processing tokens
at org.jenkinsci.plugins.tokenmacro.Parser.parse(Parser.java:97)
at org.jenkinsci.plugins.tokenmacro.Parser.process(Parser.java:75)
at org.jenkinsci.plugins.tokenmacro.Parser.process(Parser.java:68)
at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:199)
at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:237)
at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:211)
at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:203)
at org.jenkins_ci.plugins.run_condition.core.StringsMatchCondition.runPerform(StringsMatchCondition.java:62)
at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.evaluate(BuildStepRunner.java:109)
at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:149)
at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:107)
at org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuilder.perform(ConditionalBuilder.java:134)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:806)
at hudson.model.Build$BuildExecution.build(Build.java:198)
at hudson.model.Build$BuildExecution.doRun(Build.java:163)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:514)
at hudson.model.Run.execute(Run.java:1888)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:99)
at hudson.model.Executor.run(Executor.java:432)}}

Console output as follows

Run condition [Strings match] enabling prebuild for step [BuilderChain]
Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Error processing tokens], action = [Fail the build]
Build step 'Conditional steps (multiple)' changed build result to FAILURE
Build step 'Conditional steps (multiple)' marked build as failure

Alex, could you estimate when this issue could be fixed?

No, I haven't been able to reproduce it, so I can't really say when it will be fixed.

We encountered the same issue with upgrade to v280.v97a_82642793c. In the end we found out that the issue was caused by an "unset environment variable" used as a token. We worked around the issue by setting the enviroment variable to a default value and thus ensuring that there are never empty/unset tokens.

Some detailed steps from my colleague on how he reproduced the issue.

Exact steps to reproduce:

Jenkins version 2.319.3
Token Macro plugin v280.v97a_82642793c

1. Create new Freestyle project job
2. Check the "This project is parameterized" checkbox
3. Add one "Choice Parameter"

• Name: token_response
• Choices:
  Bearer ${$.get_authorisation.response.body.token}
  Bearer ${$.get_authorisation.response.body.access_token}

4. Under "Build", Add Build step -> Conditional steps (multiple)
5. In Conditional steps (multiple) entry

• under "Run?", select "String match" in dropdown

                String 1: ${token_response}

                String 2: Bearer ${$.get_authorisation.response.body.access_token}

• Add a step to run under "Steps to run if condition is met"
  (I've added "Execute Shell" containing "echo hi")

 6. Save config and then Build with Parameters

Thanks, I will try this out!

285 was released yesterday that I believe should fix this. It worked in my testing.