You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are using com.atlassian.bamboo.specs.api.builders.plan.Plan to configure our Bamboo via Specs.
Our devs are creating branches to develop on before raising a Pull Request. Our builds are run at least twice: after the branch was pushed (and on subsequent changes) and after the PR was merged.
We'd like to notify Slack room when master is "red" but we don't care that much if a build for any of unmerged changes failed (beyond possibly notifying commiters).
We tried using PlanBranchManagement.notificationForCommitters but the docs say it is no-op for spec branches.
Something like this should do the trick:
Plan plan = new Plan(); // all the common code;
if (RssRuntimeContext.isDefaultRssBranch()) {
plan.notifications(...);//any notifications you want on master branch
} else {
plan.notifications(...); //any notifications you want on specs branches
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.