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

Provide a token so that build failure causes can be included in build failure emails

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      The Build Failure Analyzer plugin provides some very handy information. I'd love to be able to include this information in the email notices that Jenkins sends out when builds fail, so that our developers can sometimes save time by not having to log in to Jenkins to see why a build failed.

      The Jenkins email-ext plugin allows administrators to construct the email body contents using a series of tokens. Could Build Failure Analyzer provide a token that lists the failure analysis reasons, descriptions, and links to the indications?

        Attachments

          Activity

          Hide
          jaswong Jason Wong added a comment -

          Yeah, I got that working as well, the problem I have is when I use the same token in a groovy template. Other tokens work though like ${build.*} etc.

          Show
          jaswong Jason Wong added a comment - Yeah, I got that working as well, the problem I have is when I use the same token in a groovy template. Other tokens work though like ${build.*} etc.
          Hide
          fonsecas72 hugo fonseca added a comment -

          No, I still haven't found the solution for this.
          I tried something like: http://jenkins-ci.361315.n4.nabble.com/Build-Failure-Analyzer-Email-Ext-td4720692.html and when I try the "Email template testing" it works fine but since in the real build the scan is triggered after the email being sent it does not work. :/

          Show
          fonsecas72 hugo fonseca added a comment - No, I still haven't found the solution for this. I tried something like: http://jenkins-ci.361315.n4.nabble.com/Build-Failure-Analyzer-Email-Ext-td4720692.html and when I try the "Email template testing" it works fine but since in the real build the scan is triggered after the email being sent it does not work. :/
          Hide
          shahmishal mishal shah added a comment -

          is it possible to change the order in which BFA runs? I am not able to send out email with BFA info because BFA runs after email plugin is triggered.

          Show
          shahmishal mishal shah added a comment - is it possible to change the order in which BFA runs? I am not able to send out email with BFA info because BFA runs after email plugin is triggered.
          Hide
          shahmishal mishal shah added a comment -

          is it possible to change the order in which BFA runs? I am not able to send out email with BFA info because BFA runs after email plugin is triggered.

          Show
          shahmishal mishal shah added a comment - is it possible to change the order in which BFA runs? I am not able to send out email with BFA info because BFA runs after email plugin is triggered.
          Hide
          mike_bayliss mike bayliss added a comment -

          The token can be used in the default content box, so I presume that BFA is actually started by email-ext plugin in that case.

          I've looked at the code but java/groovy isn't my strong point and I can't work out how to start the BFA from the groovy template. If somebody can provide that information there isn't any need for code changes.

          Show
          mike_bayliss mike bayliss added a comment - The token can be used in the default content box, so I presume that BFA is actually started by email-ext plugin in that case. I've looked at the code but java/groovy isn't my strong point and I can't work out how to start the BFA from the groovy template. If somebody can provide that information there isn't any need for code changes.

            People

            Assignee:
            t_westling Tomas Westling
            Reporter:
            smokris Steve Mokris
            Votes:
            20 Vote for this issue
            Watchers:
            20 Start watching this issue

              Dates

              Created:
              Updated: