Committers do not receive Bamboo email notifications, though notifications are configured for the plan.

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問


プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Fisheye および Crucible は除く

要約

Some of the committers or particular recipients do not receive the notifications configured for the plan since all conditions are met for the notification event. whereas other recipients are able to receive notifications for the same event.

環境

This is seen in Bamboo version 7.2.4 connected with the SVN repository as a linked repository.

診断

  • Check that all conditions are met for the notification event configured for the plan in order to send notifications by the Bamboo to users. A detailed explanation of events can be found at Notification events under the "Notification events" section.
  • As it is mentioned in the summary of this page that other users are able to receive the notification mail, it is confirmed that it is not an issue with the mail server.
  • Once all the above are checked and confirmed, it's time to debug more into the notifications by enabling the following classpaths under Bamboo administration > Log settings.

    com.atlassian.bamboo.notificationすべて
    com.atlassian.bamboo.mailDEBUG
    com.atlassian.bamboo.authorDEBUG
    com.atlassian.bamboo.commitDEBUG

    More info can be found at Troubleshooting Notifications under the "Debugging Notifications" section.

  • Once the above is enabled, reproduce the issue and check the <Bamboo-home>/logs/atlassian-bamboo.log file. You can see something like this below in the logs:

    2020-04-08 17:05:22,469 DEBUG [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-13] [ChainCompletedNotificationListener] Completed Chain Notification Listener checking for notifications to send for PROJ-PLANKEY-12
    2020-04-08 17:05:22,497 DEBUG [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-13] [ChainCompletedNotificationListener] Completed chain notification (class class com.atlassian.bamboo.notification.chain.ChainFailedAndFirstFixedNotificationType ) rule found for recipient: , type: com.atlassian.bamboo.plugin.system.notifications:recipient.committer...
    
    2020-08-25 16:37:20,904 DEBUG [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-15] [CommitterRecipient] Author Lastname, Firstname <firstname@corp.com> does not have a linked user. Skipping
  • As per the above log snippet, the linked user is missing for the author, so Bamboo is skipping sending notifications to the committer.
  • The below SQL query can be used to check if linked_username is associated with an author or not:

    select * from author where author_name like '%<author_name>%';

    (Where <author_name> is your login name for the source-code repository.

    • From the above output, please verify if the column linked_username is null for the author or not.

    • If it is null, please follow the steps provided under the solution section of this page.

原因

  • In this case, the issue is due to the author's name not being associated with any Bamboo user profile in Bamboo. When the author name is associated with the Bamboo user profile, then only Bamboo will be able to send notifications related to builds.

ソリューション

  • Associating the Bamboo user profile with the author's name can solve this issue.

  • In order to do this, select Bamboo user profile >Edit Profile > select the author name from the Repository aliases list. If your name does not appear in the list, select Add aliasPlease refer to the document Associating your author name with your user profile for more info.
  • For the SVN repository, if an author made at least one commit to the repository, then go to Bamboo user profile->Edit Profile and search for the author's name in "Repository alias" and add it.
最終更新日 2022 年 5 月 10 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.