Bamboo monitors new branches pushed to Bitbucket and accordingly creates new plan branches.
If the first build of the plan branch failed, then no responsibility is auto-assigned, so no one is notified. (Even if you manually assign the responsibility, Bamboo does not send an email to the responsible person until the next build failure. This is a separate bug reported in https://jira.atlassian.com/browse/BAM-17387)
All the subsequent build failures in the plan branch do not have responsibility auto-assigned either. So no one will get notified and actively fix them.
The auto-assign seems to only work again when someone has fixed the build failure, and then a new commit makes the next build fail.
Is there any way to configure bamboo so it can assign the responsibility to the one who committed last in the new plan branch, if the first build fails?
If the first build of the plan branch failed, then no responsibility is auto-assigned, so no one is notified. (Even if you manually assign the responsibility, Bamboo does not send an email to the responsible person until the next build failure. This is a separate bug reported in https://jira.atlassian.com/browse/BAM-17387)
The first build failure does not auto assign because there isn't any related Commit in the Commit tab for first build. Feature Request https://jira.atlassian.com/browse/BAM-12984
All the subsequent build failures in the plan branch do not have responsibility auto-assigned either. So no one will get notified and actively fix them.
Subsequent build failures should have auto assign the creator of the commit. Is there any Commits shown in the Commit tab of the build?
Is the related Bamboo user configured with the correct alias? Make sure that the email shown in Author of the commit in the Commit tab is added as alias for the related user at Administration > Security > Users > <username> > Repository aliases. The related user can add the alias manually at User Profile > Edit profile too.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.