Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-5391

Please provide email notifications from Jenkins

    Details

    • Type: Story
    • Status: Won't Fix
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: Continuous Integration
    • Labels:
      None

      Description

      I would like email notification of the completion of Jenkins jobs that I submit (but no others). It would especially helpful if the email included a link to the console log and a summary of success or failure.

      As it stands, it is painful to figure out when a job succeeds or fails. I have to either watch endless irrelevant messages go by on the Jekins HipChat room or, when the job stars, immediately launch a browse window to watch the console log. Neither is very satisfactory, especially if I need to go somewhere else while the job runs.

      The current system would be acceptable if the jobs ran quickly, but most of mine take an hour.

      A fine alternative (in case it is easier) is to have a copy of the HipChat notification of jobs I submit sent directly to me on HipChat. That will trigger a notification if I'm connected to HipChat or an email if not, so it would be fine.

        Attachments

          Issue Links

            Activity

            Hide
            jhoblitt Joshua Hoblitt added a comment -

            After a quick survey of the the options, I think this would require:

            • setup of a mail relay for the jenkins master – most likely AWS SES
            • puppetize the configuration of the jenkins global mail relay configuration
            • identity an existing or create a new jenkins plugin that extends the core mailer plugin to allow notifications only to the build requester. This plugin looks promising: https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin
            • puppetize configuration of the notification behavior. This would likey require modification of each job's configuration.
            Show
            jhoblitt Joshua Hoblitt added a comment - After a quick survey of the the options, I think this would require: setup of a mail relay for the jenkins master – most likely AWS SES puppetize the configuration of the jenkins global mail relay configuration identity an existing or create a new jenkins plugin that extends the core mailer plugin to allow notifications only to the build requester. This plugin looks promising: https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin puppetize configuration of the notification behavior. This would likey require modification of each job's configuration.
            Hide
            Parejkoj John Parejko added a comment - - edited

            This would be very useful. It is definitely hard to know when my job finished (or even if it started, given the fact that I'm usually not logged in the first time I go to the jenkins website).

            An alternate solution would be a tweetbot that we could monitor in twitter. Which would honestly be pretty cool anyway.

            Show
            Parejkoj John Parejko added a comment - - edited This would be very useful. It is definitely hard to know when my job finished (or even if it started, given the fact that I'm usually not logged in the first time I go to the jenkins website). An alternate solution would be a tweetbot that we could monitor in twitter. Which would honestly be pretty cool anyway.
            Hide
            frossie Frossie Economou added a comment -

            I have an alternative proposal based on Josh's recent work - that we use the Github API to trigger a notification either by the CI-on-merge mechanism or by an @mention comment. Then Github can take care of the emailing.

            Show
            frossie Frossie Economou added a comment - I have an alternative proposal based on Josh's recent work - that we use the Github API to trigger a notification either by the CI-on-merge mechanism or by an @mention comment. Then Github can take care of the emailing.
            Hide
            Parejkoj John Parejko added a comment - - edited

            That could work. Would that mean that each ticket github branch would have a tag/link added every time a Jenkins build completed? That's not a terrible idea anyway.

            Show
            Parejkoj John Parejko added a comment - - edited That could work. Would that mean that each ticket github branch would have a tag/link added every time a Jenkins build completed? That's not a terrible idea anyway.
            Hide
            frossie Frossie Economou added a comment -

            Oh god no, we don't want that much tag noise. I was thinking putting a comment on the PR or an issue or something like that

            Show
            frossie Frossie Economou added a comment - Oh god no, we don't want that much tag noise. I was thinking putting a comment on the PR or an issue or something like that
            Hide
            rowen Russell Owen added a comment -

            J Matt Peterson [X] pointed out that the following page exists, which is a huge help. I would still like to get explicit notifications, this page is very useful:

            https://ci.lsst.codes/user/username/builds

            where username is your github username

            Show
            rowen Russell Owen added a comment - J Matt Peterson [X] pointed out that the following page exists, which is a huge help. I would still like to get explicit notifications, this page is very useful: https://ci.lsst.codes/user/username/builds where username is your github username
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            I'm closing this request as "wont fix" as there are now reasonable slack notifications.

            Show
            jhoblitt Joshua Hoblitt added a comment - I'm closing this request as "wont fix" as there are now reasonable slack notifications.

              People

              • Assignee:
                jhoblitt Joshua Hoblitt
                Reporter:
                rowen Russell Owen
                Watchers:
                Frossie Economou, John Parejko, John Swinbank, Joshua Hoblitt, Russell Owen
              • Votes:
                1 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: