• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: token-macro-plugin
• Labels:

  None

1. 

   ExampleCondition2.png

   28 kB

   2022-03-03 17:01

2. 

   PluginVersion.png

   20 kB

   2022-03-03 16:54

3. 

   no_bug.png

   12 kB

   2022-03-02 05:06

4. 

   bug.png

   12 kB

   2022-03-02 05:06

5. 

   TokenMacroConditional.png

   55 kB

   2022-03-01 11:00

[JENKINS-67916] Continue to get [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Error processing tokens] after upgrade to 280

Brendan Farrell created issue - 2022-03-01 11:54

Brendan Farrell made changes - 2022-03-01 11:58

Description

Original: related to issues https://issues.jenkins.io/browse/JENKINS-67862 https://issues.jenkins.io/browse/JENKINS-67873   Upgraded the Token Macro jenkins plugin to 280 but still encountering the error reported in these tickets.   ``` Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Error processing tokens], action = [Don't run] 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 ```   Prior to v277 these jobs ran without issue.   It may be related to the specific syntax in my conditional statement - with is a string beginning with a $.   !TokenMacroConditional.png

New: related to issues https://issues.jenkins.io/browse/JENKINS-67862 https://issues.jenkins.io/browse/JENKINS-67873   Upgraded the Token Macro jenkins plugin to {{280.v97a_82642793c}} but still encountering the error reported in these tickets.   {{Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Error processing tokens], action = [Don't run]}} {{ 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}}     Prior to v277 these jobs ran without issue. It may be related to the specific syntax in my conditional statement - with is a string beginning with a $. See the attached screenshot for details.

Brendan Farrell made changes - 2022-03-01 11:59

Description

Original: related to issues https://issues.jenkins.io/browse/JENKINS-67862 https://issues.jenkins.io/browse/JENKINS-67873   Upgraded the Token Macro jenkins plugin to {{280.v97a_82642793c}} but still encountering the error reported in these tickets.   {{Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Error processing tokens], action = [Don't run]}} {{ 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}}     Prior to v277 these jobs ran without issue. It may be related to the specific syntax in my conditional statement - with is a string beginning with a $. See the attached screenshot for details.

New: related to issues https://issues.jenkins.io/browse/JENKINS-67862 https://issues.jenkins.io/browse/JENKINS-67873   Upgraded the Token Macro jenkins plugin to {{280.v97a_82642793c}} but still encountering the error reported in these tickets.   {quote}Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Error processing tokens], action = [Don't run] 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 {quote}     Prior to v277 these jobs ran without issue. It may be related to the specific syntax in my conditional statement - with is a string beginning with a $. See the attached screenshot for details.

Brendan Farrell made changes - 2022-03-01 16:41

Link

New: This issue blocks JENKINS-67862 [ JENKINS-67862 ]

Brendan Farrell made changes - 2022-03-01 16:42

Link

Original: This issue blocks JENKINS-67862 [ JENKINS-67862 ]

Brendan Farrell made changes - 2022-03-01 16:42

Link

New: This issue relates to JENKINS-67862 [ JENKINS-67862 ]

Rafa made changes - 2022-03-02 05:06

Attachment

New: bug.png [ 57369 ]

Rafa made changes - 2022-03-02 05:06

Attachment

New: no_bug.png [ 57370 ]

Collapse comment: Rafa added a comment - 2022-03-02 05:29

Rafa added a comment - 2022-03-02 05:29

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

Expand comment: Rafa added a comment - 2022-03-02 05:29

Rafa added a comment - 2022-03-02 05:29 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

Collapse comment: Brendan Farrell added a comment - 2022-03-02 09:27, Edited by Brendan Farrell - 2022-03-02 09:36

Brendan Farrell added a comment - 2022-03-02 09:27 - edited

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 $??).

Expand comment: Brendan Farrell added a comment - 2022-03-02 09:27, Edited by Brendan Farrell - 2022-03-02 09:36

Brendan Farrell added a comment - 2022-03-02 09:27 - edited 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 $??).

Load more newer events