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.
When configuring a GitHub repository in Bamboo a repository polling trigger will be added by default. Polling triggers are designed to frequently check the remote repository for changes and may not be the best strategy for all build plans. They tend to overload the server with scheduled tasks to check the remote repository and this can reduce the server performance.
The steps below are intended to allow you a different configuration that will remove the cost of frequent remote repository checks.
Configuration steps
Admin >> Security settings>> [x] Allow anonymous users to trigger remote repository change detection and Bamboo Specs detection
https://<BAMBOO_URL>/rest/triggers/latest/remote/changeDetection?planKey=<PLAN-KEY>
The above steps should be enough to configure the Bamboo instance for remote triggers from GitHub.
Daniel Santos
Atlassian TeamCommunity Support Engineer
185 accepted answers
2 comments