This is a re-ask of this question as it appears to have been both misunderstood and to have fallen off the radar.
The question boils down to getting bamboo to work nicely with a fast-forward merge strategy. In such a strategy, not every merge to the master branch results in a merge commit. Some simply re-point the master branch to the relevant commit, which might already have a build associated with it. Since builds can take a long time in some cases, it would be great if bamboo could automatically update the master branch plan to point to the results of the build from the development branch plan instead of re-running a build. Given that the commit hash would be the same in a case of a fast-forward merge, this would be completely safe to do (unless the build makes use of timestamps in a weird way, but that's a separate issue)
If bamboo isn't capable of this, how might one submit a ticket for it and try to get attention to said ticket?
I can't comment on the ticket, but it would be nice in general if bamboo could trigger builds based on the tree hash instead of the commit hash. You can get the tree by `git show --pretty=format:%T HEAD`. This way someone could modify their commit message or change authorship without having to re-run tests.
Can see all commit metadata with git cat-file commit HEAD
On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events