I've got a Bamboo plan configured to build from a GitHub repository. Bamboo polls GitHub and detects commits that trigger a build. Bamboo correctly lists the GitHub commit under the Commits tab. Correctly detects the JIRA ticket id in the commit message and links it to our JIRA. However, it does not link the commit id back to GitHub. In other plans using a Stash repository, Bamboo does link the commits back to Stash.
Is this a problem with the way the GitHub repo is defined in Bamboo? Bamboo gains access to the repo through a GitHub account and a SSH key. However, the particular GitHub account does not own the repository. The account does have access rights to the repository. The repository is a private repository with access restricted to our organization.
Updated on 26-Apr-2017
By examining the HTML Bamboo produces arround the GitHub commit, I see this:
<span class="revision-id" title="Unable to create URL - please check your web repository configuration"> 7a0f2e22b0ba314d4f6675a8d6b58f7f218461b5 </span>
It would be very helpful if that title was visible on the page instead of being buried in the HTML.
Updated 26-Apr-2017
Have tried several ways of defining the WEB Repository for the GitHub Linked Repository. Tried defining using Stash (Legacy) and Fisheye. Neither will generate the correct URL for linking back to GitHub. So basically Bamboo 5.14.5 does not provide a way to link a commit back to GitHub like it does for Stash or Fisheye.