nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

email notifications

Sarath_9utvha

Hi,

can anyone please tell me how to configure the email notifications for every build success/failure. Need to send multiple recipients who is not having the slack subscription.

Few examples already available, but need a step by step implementation to add in the existing repo.

Thanks in advance.

Accepted answers

Oleksandr Kyrdan

Hi @Sarath ,

thank you for your question!

It's a good case to use email-notify pipe.

Please, follow next steps to setup it:

Step 1: Configure your Bitbucket repository for the project

Add your credentials and configuration settings in Bitbucket as variables (see: how to configure Pipelines variables).

Settings > Pipelines > Repository variables:

PASSWORD: The password to authenticate with

Step 2: Setup your CI/CD configuration

Edit and add these steps to bitbucket-pipelines.yml :

image: atlassian/default-image:2

test: &test
  step:
    name: Test
    script:
      - echo "Everything is awesome!"

build: &build
  step:
    name: Build
    script:
      - echo "Starting build..."
      #- <your build logic>
    after-script:
      - ALERT_TYPE="success"
      - if [[ $BITBUCKET_EXIT_CODE -ne 0 ]]; then ALERT_TYPE="error" ; fi
      - pipe: atlassian/email-notify:0.3.12
        variables:
          USERNAME: 'myemail@example.com'
          PASSWORD: $PASSWORD
          FROM: 'myemail@example.com'
          TO: 'example1@example.com, example2@example.com'
          HOST: 'smtp.gmail.com'
          SUBJECT: '${ALERT_TYPE}:Bitbucket Pipe Notification for ${BITBUCKET_BRANCH}'

pipelines:
  default:
    - <<: *test
    - <<: *build
  branches:
    master:
      - <<: *test
      - <<: *build

Step3: Check your Pipelines status and messages in your email account )

Note: We recommend using the pipe with your own email server or third-party providers that support massive email notifications (Sendgrid, AWS SES, ...). Some free accounts from vendors such as Gmail or Outlook have special policies about security and rate limiting that could affect configuring and using the pipe. Make sure you read about it and understand their policies before using them.

All comments

Oleksandr Kyrdan

Hi @Sarath ,

thank you for your question!

It's a good case to use email-notify pipe.

Please, follow next steps to setup it:

Step 1: Configure your Bitbucket repository for the project

Add your credentials and configuration settings in Bitbucket as variables (see: how to configure Pipelines variables).

Settings > Pipelines > Repository variables:

PASSWORD: The password to authenticate with

Step 2: Setup your CI/CD configuration

Edit and add these steps to bitbucket-pipelines.yml :

image: atlassian/default-image:2

test: &test
  step:
    name: Test
    script:
      - echo "Everything is awesome!"

build: &build
  step:
    name: Build
    script:
      - echo "Starting build..."
      #- <your build logic>
    after-script:
      - ALERT_TYPE="success"
      - if [[ $BITBUCKET_EXIT_CODE -ne 0 ]]; then ALERT_TYPE="error" ; fi
      - pipe: atlassian/email-notify:0.3.12
        variables:
          USERNAME: 'myemail@example.com'
          PASSWORD: $PASSWORD
          FROM: 'myemail@example.com'
          TO: 'example1@example.com, example2@example.com'
          HOST: 'smtp.gmail.com'
          SUBJECT: '${ALERT_TYPE}:Bitbucket Pipe Notification for ${BITBUCKET_BRANCH}'

pipelines:
  default:
    - <<: *test
    - <<: *build
  branches:
    master:
      - <<: *test
      - <<: *build

Step3: Check your Pipelines status and messages in your email account )

Note: We recommend using the pipe with your own email server or third-party providers that support massive email notifications (Sendgrid, AWS SES, ...). Some free accounts from vendors such as Gmail or Outlook have special policies about security and rate limiting that could affect configuring and using the pipe. Make sure you read about it and understand their policies before using them.

Sarath_9utvha

Hi Oleksandr Kyrdan,

Thanks for reply, I have used gmail smtp server details along with the code you mentioned above. I got the below error.

<span>✖ Failed to send email. Check your configuration settings.</span>

I have enabled the required settings in my gmail security settings.

Oleksandr Kyrdan

@Sarath ,

make sure that you've turned on Lesssecure access for your account (periodically Google can turn it off) https://myaccount.google.com/lesssecureapps .

Also, check if no messages in your account about blocked access.

Sarath_9utvha

@Oleksandr Kyrdan ,

I have enabled the Lesssecure access earlier itself. But it is blocking me as you mentioned. So I did use two step verification and created a app password. Its working and I got the email notifications. thanks for the help.

surajkamble

Hi @Oleksandr Kyrdan , @Abryan Manalansang , @Sarath

I have enabled the Lesssecure access . But still it is blocking me.

if u have steps please send me

thanks in advance

Sarath_9utvha

Hi@surajkamble,

After enabling the Lesssecure access , on the same security page, you need to turn on 2-step verification and then create a App password which will be provided by google. You have to use this generated app password in your repo. Then you will be able to send the emails.

surajkamble

Thank you @Sarath

John Ghidiu_swd1zq

When using Sendgrid, it is important to remember that the username is `apikey` and the password is the API key. The Sendgrid tutorial uses base64 encoded values for username and password, but the Atlassian pipeline specifically uses PLAIN authentication, so it is an error to encode the username and password variables.

Abhishek P_ck8xgb

@Oleksandr Kyrdan Any suggestions / steps for using AWS SES SMTP for email-notify pipe ?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

notification

atl-gruland

bitbucket-pipelines