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

Token in Email Extension Plugin not working anymore after upgrade to Jenkins 2.289.3

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • token-macro-plugin
    • None
    • Linux (CentOS 7)
      Jenkins 2.289.3
    • 2.14

      Hi,

      We have a Jenkins job that uses the "Email Extension Plugin" in order to send emails with the content of a file as Default Content
      The job uses this functionality with this kind of token:
      ${FILE,path="file.txt"}

      Since upgrading Jenkins from version 2.263.3 to 2.289.3 in the emails Default Content we get ${FILE,path="file.txt"}
      instead it of the content of file.txt.
      After fallback to 2.263.3 the issue recovered again.

      Version of Email Extension Plugin used is 2.83

      Many thanks for your help!

      Brgrds,

      Steffen

       

          [JENKINS-66392] Token in Email Extension Plugin not working anymore after upgrade to Jenkins 2.289.3

          Steffen created issue -
          Namikaze Minato made changes -
          Component/s New: token-macro-plugin [ 15832 ]
          Namikaze Minato made changes -
          Environment Original: Linux (CentOS 7) New: Linux (CentOS 7)
          Jenkins 2.289.3
          Basil Crow made changes -
          Component/s Original: email-ext-plugin [ 15538 ]
          Basil Crow made changes -
          Link New: This issue duplicates JENKINS-64555 [ JENKINS-64555 ]
          Basil Crow made changes -
          Released As New: 2.14
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Unassigned Unassigned
            swohlrab Steffen
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: