In one of the pull requests a ticket is referenced with a bad build. However, this does not have the same build key. There are also no references to this ticket in the commits.Why are other build results displayed in the pull request.
It's confusing users as the build appears to be failed.
Configuration: Bitbucket 4.8.x / Bamboo 5.12.1 / JIRA 7.0.2
On the Bitbucket side, we don't do anything smart with those results. We basically accept build statuses (including build names as an arbitrary string) via REST that are mapped to a commit hash. We then show the build statuses that are linked to the commit at the head of the source branch of the pull request.
Judging from the format you have there, I suspect that someone named their branch IP-1709-**** and branched off the head commit of this PR, and pushed it up for Bamboo to grab. Bamboo then built the branch plan and sent Bitbucket Server results for this commit, which failed. Since Bamboo was building the branch plan for a branch named IP-1709-***, when it sent us the name of the build, it included that branch name in the arbitrary string.
So ultimately there is some build that failed against the HEAD commit of your branch, and that might be something to worry about. Perhaps the build is flakey, or that branch plan is running different tests, but those both definitely should be cause for alarm. A third possibility is that the branch plan was simply misconfigured and that shouldn't be a cause for alarm.
Does that make sense?
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot