Setting Up Notifications for Parent Branch Committer on Child Branch Failure in Bamboo

[shyam kumar]

Our team is using Bamboo for our CI/CD pipelines, and we have a common setup involving parent-child plan dependencies.

Our Setup:

• We have a "parent" plan which builds a core component.

• This parent plan is configured to trigger multiple "child" plans upon its successful completion.

• Each child plan has its own separate repository.

The Problem: A frequent scenario we encounter is that a commit to the parent plan's repository might introduce a change that causes one or more of the downstream child plans to fail.

We need a reliable way to notify the original committer(s) of the parent plan when one of these dependent child plans fails, as the parent's change is the root cause.

Is there a native Bamboo feature or a simpler configuration we might be overlooking that allows us to directly notify the parent plan's committers when a dependent child plan fails?

[Shashank Kumar]

Hello Shyam,

Welcome to Atlassian community.

On the child plan if you set the below notification, won't it work ?

As I understand the child plan fails because of commit done by some user which triggered the main plan but same changes caused failure of the child plan.

Still child plan should be able to notify the original committers as those commits are causing failures. 

Regards,

Shashank Kumar

[shyam kumar]

Hello Shashank,

Thank you again for your response and for your valuable suggestion. We appreciate you looking into this!

To clarify our concern a bit further, we want to make sure we're on the same page regarding how Bamboo's "Committers" notification works in a very specific scenario we face.

Our Situation: We have a "main" project (our Parent Plan) that automatically starts other "sub-projects" (our Child Plans) when it successfully finishes. Each Child Plan has its own separate code.

The Specific Case We're Asking About: Sometimes, a change made only to the Parent Plan's code causes one of our Child Plans to break and fail. In this specific failure, there are no new code changes in the Child Plan's own repository.

We have set up the Child Plan to send an email notification when its build fails, specifically to the "Committers - Users who have committed to the build."

Our main question is: In the scenario described above (Child Plan fails due to a Parent Plan code change, with no new commits to the Child Plan's own code), will Bamboo's "Committers" notification correctly email the person who committed the change to the Parent Plan's code?

We're currently running a test exactly for this scenario in our environment to verify the behavior. We're very keen to see if Bamboo handles this specific cross-repository committer attribution natively.

Thanks,

Shyam