Skip to end of metadata
Go to start of metadata

With this service, you can set up Bitbucket to send an email message to a given email address, for each pushed changegroup. To send multiple emails, provide a comma-separated list of addresses, for example: 

sally@gothic.edu,betty@meanmoms.org

Format of the Email Messages

Email messages are sent from commits-noreply@bitbucket.org.

When a changegroup contains only one changeset, the email subject line will be of the following form:

Subject: commit/<project>: <user>: <commit msg>

When a changegroup contains two or more changesets, the email subject line will be of the following form:

Subject: commit/<project>: <x> new changesets

Setting Up the service

 You must have administrative access on a repository to add this service.

  1. Go to the repository's settings.
  2. Click Services in the left-hand navigation.
    The Services page appears.
  3. Select the Email service from the services dropdown.
  4. Click Add service.
    A new section appears for the Email service.
  5. Enter the following information:

    EmailEnter the email address where Bitbucket should send the email messages.
  6. Press Save.

If you are having trouble with the service, see Troubleshoot Bitbucket services.

12 Comments

  1. Anonymous

    Is there a way to leave repo push e-mail subscriptions in the hands of the individual user instead of the admin?  I admin a Mercurial repo and would prefer to have the repo users take care of whether or not they want to receive push e-mails.

    Thanks.

    1. Anonymous

      A very simple way to do that would be to send the push e-mails to a mailing-list. Users could then subscribe to the mailing-list if they want to.

       

  2. Anonymous

    I send all commits to a commits mailing list. If someone sees an interesting commit and uses the neat commenting features you have on the website, those comments are hidden from the people who follow the mailing list.

    I would like a feature where I can specify which project mailing list commit comments should be sent to.

  3. Anonymous

    Does this work for git commits as well as mercurial? We have not been successful in getting this to work for a git repo.

    1. It should.  If you are having problems getting it to work, please send an email to support@bitbucket.org.

  4. Anonymous

    You need to get emails setup like Fisheye.. They were 1000X better

  5. Anonymous

    Is there a way to configure email notifications to be received only for particular branch commits?

  6. Anonymous

    Thanks for this hook.

    https://bitbucket.org/site/master/issue/8161/email-hook-branch-value-bug if you get a moment please

    Warm regards

  7. I just contacted Atlassian Support to hear how we can get email setup like we had it in FishEye. Those emails made us very productive and gave us good insight to what changed, with URLs to the diff. Seems like we have moved 30 years back in time with Bit Bucket emails, but perhaps we just don't know how to configure properly.

  8.  Is it possible to send mails from the author email push or pullrequest.