We're using Bamboo to build a number of our web sites using Jekyll. The content for the sites is stored in git repositories stored on GitHub so that the community can contribute to the documentation.
At the moment, the process is that when a pull request is approved, the commit is merged into the GitHub repository, which then triggers a build in Bamboo.
If that build fails (for example if the user submitted something that included a broken link), no progress can be made until someone goes and fixes the problem. It completely halts progress.
What I'd like to have is something similar to what I've seen elsewhere with code submissions where the pull request itself triggers a code validation process (in this scenario, an attempt to build the site) and then report back to GitHub the status of the build process so that the repo maintainer knows whether or not the proceed with the merge.
We're already using the GitHub Status add-on for Bamboo and it is reporting back to GitHub the status of the current build process for a given commit but that is only part of the picture.
I don't know how to do the "trigger a build in Bamboo when someone submits a pull request but before the merge is approved" bit ... is it even possible with GitHub and Bamboo?
I could use Travis instead but that seems to be duplicating the stack then ...
I've found this article which looks like it will help a lot:
I need to do some testing to see how much of our existing workflow needs to change.
This doesn't seem to be a complete answer, after all.
Unfortunately, this approach only seems to work when the new branches are created on the repository that is used when building in Bamboo.
However, if the pull request comes from a fork of the repository, the new branch is on that fork and not on the repository referenced by Bamboo ... which means that GitHub never triggers a Bamboo build!
Any thoughts or suggestions on that?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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