I just used an Atlassian article to configure my team's integration between BitBucket Cloud and Bamboo Server. I would like to understand the API better, but I can't locate the documentation. Specifically, I want to know:
I expected to find it here: https://docs.atlassian.com/atlassian-bamboo/REST/6.2.3/
The endpoint is not available in Bamboo's REST API documentation, I am afraid. Now, going back to your inquire:
I checked with the Bamboo team and it doesn't look like there is any public documentation for the Remote Trigger API as it's not public and isn't meant to be used in API calls at this time as all the publicly documented API calls can be found in the document you linked to.
I would encourage you to go to JAC and create a Suggestion ticket to get this added to the public API and documentation created for it.
So, using BitBucket cloud and Bamboo Server 6.2.2 how do I accomplish the following?
1. PLAN-A - Want to check that the feature branch merges cleanly and do some basic checks.
2. PLAN-B - Merge the change into the target branch(develop) of the pull request and do some more extensive checks before pushing merge back to BitBucket and thus closing the pull request. .
This seems like it should be a pretty straight forward process. BUT....
I configured a webhook for PLAN-A which is sent on pull request creation and updates.
In PLAN-A I set the trigger to be remote. The job is triggered but nothing will be built as the linked repository defaults to develop. So change detection will say there is nothing to do unless I can somehow get a hold of the feature branch.
So I configured PLAN-A to create branches on pull request creation and configured it to use a Branch Updater strategy.
The trigger is sent, PLAN-A checks for changes on the default branch(develop) for the linked repository and does nothing. But a branch is created for PLAN-A. This does detect changes. This seems to work.
For PLAN-B I create basically the same webhook but only send it when a pull request is approved to PLAN-B.
The same thing will happen with change detection, i.e, it will check if there are changes on the default branch for the linked repository (develop). Let's say there are none. Now the pull request will not be merged into develop :-(
So I then I wanted configure branches for PLAN-B. So I select create branch when pull request is created. OK this basically the same as Plan-A and should work. When the plan is triggered is doesn't do anything if there are no new changes on the develop branch. But it should see that there is a pull request created? Or what?
Also If I select create branch when pull request is created i cannot use the Gatekeeper branching strategy! It is simply not available!
So I am really trying to figure out how to handle this...
Any suggestions would be appreciated.
We’re excited to invite you to this action-packed webinar where we will demonstrate how to integrate Opsgenie’s powerful alerting and on-call management tools with your entire Atlassian stack. Mar...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs