Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-43951

Allow use of double quoted strings for pipeline variables

    • 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

          Michael Neale created issue -
          Michael Neale made changes -
          Epic Link New: JENKINS-36291 [ 172300 ]
          James Dumay made changes -
          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
          James Dumay made changes -
          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
          Michael Neale made changes -
          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)
          Michael Neale made changes -
          Assignee Original: James Dumay [ jamesdumay ]
          Michael Neale made changes -
          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*
          * 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)
          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)

          Out of scope: 

          * A UI to select available pipeline variables
          James Dumay made changes -
          Rank New: Ranked lower
          James Dumay made changes -
          Rank New: Ranked lower
          James Dumay made changes -
          Sprint Original: Blue Ocean 1.3 [ 296 ] New: Blue Ocean 1.2-beta5 [ 376 ]
          James Dumay made changes -
          Rank New: Ranked lower

            Unassigned Unassigned
            michaelneale Michael Neale
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: