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.
I have a plan with 6 repositories linked to trigger it. All of them are set to 30minute (1800s) Quiet Periods (which means I should be able to commit to all 6 repos within a thirty minute timeframe, and the commits will all get included in next build).
When a repo gets pushed. It triggers the Quiet waiting period successfully, but the period is substantially longer than 30min. At the moment of writing, the quiet period has been waiting for 45 minutes. Will update with ultimate time it takes when it finally kicks off the build. EDIT: Finally kicked off after about an hour
Anyone know anything about this? Are my quiet periods stacking? Is this a bug?
Thanks
EDIT: I am on Bamboo version 6.2.9 build 60215 - 11 Jan 18