Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,455,405
Community Members
 
Community Events
175
Community Groups

Triggering Bamboo builds with GitHub webhook

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.

 

2 comments

is the webhook url format still valid for Bamboo 7.0.x?

I found this recent article: https://www.midori-global.com/blog/2021/05/03/how-to-trigger-a-bamboo-build-on-commit

and it mentions the format:

_<YOUR_BAMBOO_SERVER_BASE_URL>/rest/api/latest/queue/<YOUR_BAMBOO_PROJECT_KEY>-<BAMBOO_PLAN_KEY>

 

Is there a doc page that has this officially documented?

found the answer for myself.  this is the format on v7.0.4:

https://<bamboo host url>/rest/api/latest/repository/scan?repositoryId=*repoId*

repoId comes creating a spec repo by going to Specs > Set up Specs repository

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events