-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
-
Blue Ocean - Candidates
Problem
For some steps, such as notifications, it is pretty common to want to be able to get to pipeline variables (as opposed to environment variables).
In pipeline text this generally means you use double quotes, and string interpolation in the parameters, howrever the editor uses single quotes and avoids groovy string expansion.
It would be nice to be able to allow dynamic double quoted strings as an option somehow.
Steps to reproduce
- Use a notification step - try to get the pipeline name into the message string
- Use an environment variable, try to use "credentials('abc')" to fetch the cred value (it will only be literally what you type in)
Out of scope:
- A UI to select available pipeline variables
[JENKINS-43951] Allow use of double quoted strings for pipeline variables
Epic Link | New: JENKINS-36291 [ 172300 ] |
Description |
Original:
For some steps, such as notifications, it is pretty common to want to be able to get to pipeline variables (as opposed to environment variables). In pipeline text this generally means you use double quotes, and string interpolation in the parameters, howrever the editor uses single quotes and avoids groovy string expansion. It would be nice to be able to allow dynamic double quoted strings as an option somehow. |
New:
*Problem* For some steps, such as notifications, it is pretty common to want to be able to get to pipeline variables (as opposed to environment variables). In pipeline text this generally means you use double quotes, and string interpolation in the parameters, howrever the editor uses single quotes and avoids groovy string expansion. It would be nice to be able to allow dynamic double quoted strings as an option somehow. *Steps to reproduce* TBD |
Sprint | New: Blue Ocean 1.2 [ 296 ] | |
Description |
Original:
*Problem* For some steps, such as notifications, it is pretty common to want to be able to get to pipeline variables (as opposed to environment variables). In pipeline text this generally means you use double quotes, and string interpolation in the parameters, howrever the editor uses single quotes and avoids groovy string expansion. It would be nice to be able to allow dynamic double quoted strings as an option somehow. *Steps to reproduce* TBD |
New:
*Problem* For some steps, such as notifications, it is pretty common to want to be able to get to pipeline variables (as opposed to environment variables). In pipeline text this generally means you use double quotes, and string interpolation in the parameters, howrever the editor uses single quotes and avoids groovy string expansion. It would be nice to be able to allow dynamic double quoted strings as an option somehow. *Steps to reproduce* TBD |
Description |
Original:
*Problem* For some steps, such as notifications, it is pretty common to want to be able to get to pipeline variables (as opposed to environment variables). In pipeline text this generally means you use double quotes, and string interpolation in the parameters, howrever the editor uses single quotes and avoids groovy string expansion. It would be nice to be able to allow dynamic double quoted strings as an option somehow. *Steps to reproduce* TBD |
New:
*Problem* For some steps, such as notifications, it is pretty common to want to be able to get to pipeline variables (as opposed to environment variables). In pipeline text this generally means you use double quotes, and string interpolation in the parameters, howrever the editor uses single quotes and avoids groovy string expansion. It would be nice to be able to allow dynamic double quoted strings as an option somehow. *Steps to reproduce* * Use a notification step - try to get the pipeline name into the message string * Use an environment variable, try to use "credentials('abc')" to fetch the cred value (it will only be literally what you type in) |
hey jamesdumay kzantow this actually came up for real. I am not sure if we ever had a solution for this (the model supports it, but how to we let the user choose or know it should be a double quoted string?)