Triggering Bamboo builds with GitHub webhook

[#1]

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

1. First of all, the Bamboo instance should be reachable through the internet. Otherwise, GitHub will not be able to find It to trigger a build.
2. As mentioned before you might have a polling trigger configured. The first action is to remove it. Go to Plan configuration >> Triggers and remove the polling trigger if you have one.
3. Bamboo needs to have a remote trigger configured in the plan you want GitHub to trigger.
4. Add the list of addresses that can trigger builds in Bamboo. You should include both your proxy address and the IPs from webhook of GitHub (you can find a reference to them in this page: About GitHub's IP addresses - GitHub Help)
5. Make sure the anonymous user can trigger builds:

   Admin >> Security settings>> [x] Allow anonymous users to trigger remote repository change detection and Bamboo Specs detection

6. GitHub needs to be configured to call the following Bamboo REST API:
   

   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.