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

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • 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

       

            Assignee:
            Unassigned
            Reporter:
            Steffen
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: