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.
Admin >> Security settings>> [x] Allow anonymous users to trigger remote repository change detection and Bamboo Specs detection
The above steps should be enough to configure the Bamboo instance for remote triggers from GitHub.
Daniel SantosAtlassian Team
I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events