-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
-
None
Due to https://jira.atlassian.com/browse/BAM-12228, the Stash integration functionality available in Bamboo Server is disabled in Bamboo cloud. This means that some Bamboo-Stash integration features, such as notifications of build statuses, commit information in Bamboo, and repository triggering are unavailable.
- is caused by
-
- Closed
-
- Closed
-
BDEV-8860 Failed to load
-
BDEV-8859 Failed to load
- relates to
-
- Closed
-
- Closed
-
- Gathering Interest
[BAM-15891] You can't integrate Bamboo Cloud with Stash Server
Mikael X Johansson
added a comment - It's pretty hard to migrate from all Server solution onto the cloud when you don't even try to fix integrations between the two products...
We have an issue that we're not getting build status back to the bitbucket server after completed builds, it this impossible from bamboo cloud?
Mikael X Johansson
added a comment - It's pretty hard to migrate from all Server solution onto the cloud when you don't even try to fix integrations between the two products...
We have an issue that we're not getting build status back to the bitbucket server after completed builds, it this impossible from bamboo cloud? 
Rijnhard Hessel
added a comment - I find this pretty ridiculous actually.
Your own products should integrate well.
At the moment you have to pick all cloud or all server, try and mix the 2 and you have hell on your hands.
I really wouldn't mind if the pricing for the server was as flexible as the cloud, but it's not.
Rijnhard Hessel
added a comment - I find this pretty ridiculous actually.
Your own products should integrate well.
At the moment you have to pick all cloud or all server, try and mix the 2 and you have hell on your hands.
I really wouldn't mind if the pricing for the server was as flexible as the cloud, but it's not. We have had long deliberations internally about this issue. At this point in time it is unlikely that we will implement this. It is unfortunate but we have many other more pressing issues we need to focus on. To set the expectations properly I will close this as 'won't fix'.
Krystian closed BAM-15894 as Not a Bug, because that old Stash notification is deprecated. If that's correct, then we should close out BAM-15892, too, and so there is no workaround possible for this bug (BAM-15891); someone will have to fix BAM-15464 or BAM-12228.
The best would be to fix BAM-15464, but the second best would be to fix BAM-15894 "Support Stash notifications via OAuth, not just Basic Auth"
IMO, the best would be to fix BAM-15464, providing a way to use HTTPS for Stash repositories.
If this gets fixed by fixing BAM-12228, we'll be stuck with using SSH in Bamboo, which the Stash documentation says we should avoid. https://confluence.atlassian.com/display/STASH/Enabling+SSH+access+to+Git+repositories+in+Stash "To get the maximum performance from Stash, we advise configuring automatic build tools to use the http or https protocol, if possible."
If BAM-15892 is fixed, we'll be able to use Basic Auth AppLinks, but then we'll be stuck using Basic Auth, which is "not recommended" according to https://confluence.atlassian.com/display/KB/Application+Links+Troubleshooting+Guide
Hi,
Thanks everyone for your feedback. Given the Bamboo Cloud EOL going forward we will not be implementing new features in Bamboo Cloud.
Regards,
Krystian Brazulewicz
Atlassian Bamboo Development