jenkinsci / jenkinsci/parameterized-trigger-plugin
[JENKINS-57974] If you do need to escape '$', use '$'.
- Dominant language
- Java
- Stars
- 77
- Forks
- 174
- Avg merge
- 22h 27m
- Merged PRs (30d)
- 1
Description
- install the Jenkins Parameterized Trigger plugin (2.35.2)
- create a freestyle job
- click Add build step
- click Trigger/call builds on [sic] other projects
- click Add Parameters
- click Restrict matrix execution to a subset
- click

- read the bottom of the help:
However, Jenkins variable expansion leaves undefined variables as-is, so most of the time your Groovy string line expression syntax will survive the expansion, get passed to Groovy as-is, and work as expected. If you do need to escape '$', use '$'.
Expected results: the two things should presumably be different.
The relevant code is:
If you do need to escape '$', use '$$'.
I'm not going to fix this right away. Filing it because I found it while reading the help for everything and I'm punting as I'm not quite sure about the fix.
---
Originally reported by jsoref, imported from: If you do need to escape '$', use '$'.
Raw content of original issue
- install the Jenkins Parameterized Trigger plugin (2.35.2)
- create a freestyle job
- click Add build step
- click Trigger/call builds on [sic] other projects
- click Add Parameters
- click Restrict matrix execution to a subset
- click
- read the bottom of the help:
However, Jenkins variable expansion leaves undefined variables as-is, so most of the time your Groovy string line expression syntax will survive the expansion, get passed to Groovy as-is, and work as expected. If you do need to escape '$', use '$'.
Expected results: the two things should presumably be different.
The relevant code is:
If you do need to escape '$', use '$$'.I'm not going to fix this right away. Filing it because I found it while reading the help for everything and I'm punting as I'm not quite sure about the fix.
Contributor guide
Assessment
This issue has not been assessed yet.