問題

When integrating Bitbucket Server with Bamboo, the build status is not being reported correctly. Bitbucket Server reports a failed build where it should not. There is no exception reported in Bitbucket Server log files.

診断

環境

• Bamboo and Bitbucket Server successfully integrated using application links.

原因

The Bitbucket Server access logs indicate that the build status is being updated from two Bamboo servers. Similar entries are reported in the atlassian-bitbucket-access.log file:

172.16.1.2,172.16.3.4 | https | i@YVL5WPx506x203837x0 | - | 2017-01-17 08:26:08,367 | "POST /rest/build-status/latest/commits/cd609f735e6d512a95b6de9786e4e1148f2e8964 HTTP/1.0" | "" "Apache-HttpClient/4.3.6 (java 1.5)" | - | - | - | - | - | - | 
172.16.1.2,172.16.3.4 | https | o@YVL5WPx506x203837x0 | - | 2017-01-17 08:26:08,390 | "POST /rest/build-status/latest/commits/cd609f735e6d512a95b6de9786e4e1148f2e8964 HTTP/1.0" | "" "Apache-HttpClient/4.3.6 (java 1.5)" | 204 | 218 | 0 | - | 23 | - |

172.16.1.2 and 172.16.3.4 are the two IP addresses for the two Bamboo servers. Try and identify which one of these is your production Bamboo server?
This situation could arise if there is another Bamboo process (probably a test server) running in the same machine as Bamboo production server. This test Bamboo server probably will have the same plan key that will build from the same branch as production. If this test Bamboo is created with the backup data from Bamboo production, it will also have the application link to the same Bitbucket Server instance so it will also send the build status to the Bitbucket Server instance.

ソリューション

Run the following command in the machine hosting Bamboo to check how many Bamboo processes are running in the machine:

ps | grep java

• Kill the test Bamboo server process