-
Bug
-
Resolution: Fixed
-
Low
-
6.1.4
-
Severity 3 - Minor
-
Summary
Application link set with OAuth impersonation breaks Bamboo build status in Bitbucket
Environment
- Bamboo 6.1.4
- Bamboo 6.1.6
- Bitbucket 5.3.3
- Crowd 2.12.0
Steps to Reproduce
- Set app link between Bamboo and Bitbucket on OAuth Impersonation
- Pull users from Crowd
- Setup a plan using the Bitbucket server repository
- Commit to Bitbucket repository
Expected Results
- Bitbucket should show the build status notification from Bamboo
Actual Results
[BitbucketServerBuildStatusUpdater] Sending build notification to Stash (build key: XXXXX, repository: XXXXXX)
[RestCallHelper] Failed to send stash build notification via http://bitbucket533:7990 - it has to have OAuth authentication configured.
[BitbucketServerBuildStatusUpdater] Failed to store build status against Stash instance Bitbucket, reason: com.atlassian.bamboo.jira.rest.JiraRestResponse@11101c08[statusCode=2147483647,statusMessage=<null>,errors=Errors[errorMessages=[Failed to send stash build notification via http://bitbucket533:7990 - it has to have OAuth authentication configured.],errors={}],body=<null>,entity=<null>]
[BitbucketServerBuildStatusUpdater] No build status updates have been sent to Stash (build key: XXXXX, repository: XXXXXXX test). Is your application link configured properly?
Workaround
No workaround available if OAuth Impersonation is required. Otherwise don't setup Application Links with OAuth Impersonation.
Notes
Issue is resolved in Bamboo 6.2