Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,555,395
Community Members
 
Community Events
184
Community Groups

How to attach report to email notification after failing manual or scheduled pipeline run?

Edited

We are using pipelines to run E2E tests. When it fails, bitbucket sends email notification. We would like to receive a zipped file attached to this email. E2E tools generate reports, we would like to get these reports to see what went wrong. How to achieve this?

2 answers

@Oleksandr Kyrdan  hi! Could you help me please?

I have done everything as you write above, but somehow when Pipeline try to find an attachment - it shows an error. 

noSuchFile.jpg   

Here is my ymlFile, can you please tell me - what I have write wrong so attachment doesn't loads.

ymlFile.jpg  Thank you! And Happy New Year! And Merry Christmas!)

UPDATE

Have added full path to the file and it looks like it works. However the email is not send anyway sendingEmail.jpg

0 votes
Oleksandr Kyrdan
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 03, 2020

Hi @Marek Zielonkowski ,

Thank you for your question!

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

You can use $BITBUCKET_EXIT_CODE variable in the after-script section.
$BITBUCKET_EXIT_CODE - the exit code of a step, if step success value setup to 0.

script:
- <your test logic>
- pytest test/test.py --junitxml=test-reports/report.xml
- zip -r test-reports.zip test-reports
after-script:
- ALERT_TYPE="success"
- if [[ $BITBUCKET_EXIT_CODE -ne 0 ]]; then ALERT_TYPE="error" ; fi
- pipe: atlassian/email-notify:0.3.11
variables:
USERNAME: 'myemail@example.com'
PASSWORD: $PASSWORD
FROM: 'myemail@example.com'
TO: 'example@example.com'
HOST: 'smtp.gmail.com'
SUBJECT: '${ALERT_TYPE}:Bitbucket Pipe Notification for ${BITBUCKET_BRANCH}'
ATTACHMENTS: 'test-reports.zip'


That will fail with:


✖ Validation errors:
SUBJECT:- must be of string type

SUBJECT: "'${ALERT_TYPE}:Notification-TG Files Adapted Properly for ${BITBUCKET_BRANCH}'"

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events