Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-13092

First failed job not sending email to responsible user when Bamboo is integrated with Crowd

    XMLWordPrintable

Details

    Description

      Premises:

      • Bamboo 4.4 integrated with Crowd 2.5.3
      • All users have valid emails, and are mapped to repository committers
      • Bamboo is sending email notifications

      Bamboo configuration:

      • Repository commiter: fkraemer
      • Bamboo user details (imported from Crowd):
        • Username: fkraemer
        • Email: fkraemer@atlassian.com
        • Source Repository Alias: fkraemer
      • Plan Notifications:
        • Event: Failed Jobs And First Successful
        • Recipient Type: Responsible (users who are responsible for the current failure)

      Steps I've followed and results:

      1. I Created a new plan, containing only the Source Code Checkout task, and ran it for the first time.
      2. Build #1 was successful, and no notifications were sent, as expected.
      3. I added a task that forces the job to fail
      4. I committed code into the repository, using committer fkraemer
      5. Build #2 failed, but no email was sent to fkraemer@atlassian.com (first failed job - it should have sent an email)
      6. I committed code into the repository again, without changing plan configuration, using committer fkraemer
      7. Build #3 failed, but this time an email was sent to fkraemer@atlassian.com (second failed job)
      8. I removed the failing task from the job
      9. I committed code into the repository, using committer fkraemer
      10. Build #4 was successful, and an email was sent to fkraemer@atlassian.com (first successful, email sent as expected)
      11. I committed code into the repository again, without changing plan configuration, using committer fkraemer
      12. Build #5 was successful, and no email was sent to fkraemer@atlassian.com (as expected)

      Before trying this with Crowd integrated, using a local Bamboo user, having the same configuration, and following the same steps, the responsible user received an email for the first failed job, so this is indeed related to Crowd.

      A workaround is add another notification for "First failed job for plan" to "Committers".

      Please see the screenshot attached showing the behavior mentioned above.

      Attachments

        1. NotificationFailed.png
          57 kB
          Felipe Kraemer

        Issue Links

          Activity

            People

              achystoprudov Alexey Chystoprudov
              fkraemer Felipe Kraemer
              Votes:
              12 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: