I am using dependency to trigger build plans.
e.g. Plan A, if successful will trigger plan B which if successful will trigger plan C.
Consider following situation.
Developer X, commits and that triggers Plan A to build successfully.
Plan A then tiggers to build Plan B which also builds successfully.
Plan B then triggers Plan C which fails.
In this case I would expect Bamboo to send "Build failed" email to Developer X. This does not happen.
Notification is set to "Send email to Responsible User" if build fails.
It seems Bamboo can't figure out who the responsible developer was if a dependent plan fails.
Please help me fix this issue.
Thanks for your question. I was able to reproduce the behavior that you described, and I raised a new feature request based on this case. It will be implemented as per our policy. Feel free to add yourself as a watcher, vote or comment to that new feature request. As a workaround you can configure the same notifications for all your dependent plans.
Please let me know if you have any further questions or concerns.
Thank you so much for your response.
This does not work either. Bamboo can't figure out who the committer was that triggered parent plan build unless committer also happened to commit to child plan.
When it comes to dependent plan build, Bamboo sems to have no idea about things like who triggered the build, how long did parent plan take. It would alos make sense to be able to send just one notification when entire stack has been built successfully and how long it took instead of sending notifications on every step in the chain.
I verified that the way that the plan dependency is implemented in Bamboo is that the parent plan triggers the child plan and there is no information being passed from one to the other. This means that the child plan has no information about the parent plan performance: "like who triggered the build, how long did parent plan take".
Currently there is no way to configure Bamboo to send notifications form a child plan to the parent plan's responsible user account. If you need to add more information to the feature request that I have raised, please feel free to leave more comments with your suggestions.
Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs