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

PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin

      The PROPFILE token is not evaluating in the Editable E-mail Notification for the e-mail-ext plugin.

      For example, when I put this in the Default Content of the e-mail:

      ${PROPFILE,file="props.cfg",property="TESTING_VAR"}

      The value of "TESTING_VAR" is not displayed in the e-mail. Instead, this is displayed:

      ${PROPFILE,file="props.cfg",property="TESTING_VAR"}

      This PROPFILE token works when I put it in the "Set Build Name" field for the build-name-setter plugin.

      So the build-name-setter plugin is able to consume the PROPFILE token, but the e-mail-ext plugin does not seem to be consuming it properly.

      I am running Jenkins 1.480.2 with email-ext - 2.24.1.

          [JENKINS-16779] PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin

          Kavita Tiwari created issue -
          Kavita Tiwari made changes -
          Labels New: email-ext plugin, token-macro
          Alex Earl made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Alex Earl made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          Jesse Glick made changes -
          Resolution Original: Not A Defect [ 7 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]
          Jesse Glick made changes -
          Labels Original: email-ext plugin, token-macro New: email-ext token-macro
          Jesse Glick made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Reopened [ 4 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 147607 ] New: JNJira + In-Review [ 206401 ]

            slide_o_mix Alex Earl
            trincodog Kavita Tiwari
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: