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

Emails using WARNINGS_RESULT show "is not supported in this context" in Pipeline builds

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • analysis-core-plugin
    • None
    • Jenkins 2.32.3
      email-ext-plugin 2.57
      warnings-plugin 4.60

      I try to reference WARNINGS_RESULT in

       

      pipeline {

      .......

      post {

          always  {

              emailext (

                   body: '''${WARNINGS_RESULT}'''

      ........

       

      And I get the following in the email:

      WARNINGS_RESULT is not supported in this context

       

      I successfully ran WarningsPublisher in a previous step and that information is being posted for the builds.

       

          [JENKINS-43355] Emails using WARNINGS_RESULT show "is not supported in this context" in Pipeline builds

          Shannon Kerr created issue -
          Shannon Kerr made changes -
          Link New: This issue relates to JENKINS-41861 [ JENKINS-41861 ]
          David van Laatum made changes -
          Component/s New: token-macro-plugin [ 15832 ]
          David van Laatum made changes -
          Assignee Original: David van Laatum [ davidvanlaatum ] New: Alex Earl [ slide_o_mix ]
          Alex Earl made changes -
          Component/s Original: email-ext-plugin [ 15538 ]
          Component/s Original: pipeline [ 21692 ]
          Component/s Original: token-macro-plugin [ 15832 ]
          Assignee Original: Alex Earl [ slide_o_mix ] New: Ulli Hafner [ drulli ]
          Ulli Hafner made changes -
          Component/s New: analysis-core-plugin [ 15709 ]
          Component/s Original: warnings-plugin [ 15513 ]
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            drulli Ulli Hafner
            kerrhome Shannon Kerr
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: