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
Community Support Engineer
186 accepted answers
2 comments