feat(bitbucket): supports cloud and server APIs
Summary
This PR introduces a first working version of Bitbucket Server REST API 1.0 support, in addition to the existing Bitbucket Cloud integration.
It allows OpenHands to work with self-hosted Bitbucket instances that expose the older 1.0 REST endpoints, expanding compatibility beyond just cloud users.
Motivation
Most organizations running Bitbucket use the on-premise edition (Bitbucket Server / Data Center) instead of the cloud service. Supporting the Bitbucket Server REST API 1.0 ensures OpenHands can integrate with these enterprise setups.
Notes
- This is an initial implementation; it will be updated and refined once #11051 is merged.
- Current focus is on getting a minimal working version so that contributors using Bitbucket Server can start testing.
Thanks
Excited to contribute this — first version working! Big thanks to the community for the support 🙏
For the archive: Bitbucket data-center-end-of-life
But AFAICT no one knows what will be agentic coding in 3 years.
I am also fine to simply close this feature request if it does not align with the community needs.
How I can help to get feedback on this feature ?
I can understand it's enterprise oriented, but is not the open-source spirit of openhands ?
Without this I can't simply use bitbucket.
Thanks
Kindly request to review this
Hi! Just wanted to note that I'm getting around to reviewing this PR. Just so we're on the same page, there's a few action items in order to make progress on this PR
- there's some stale changes that I can help clean out (we've made some larger architectural changes in the last month to the codebase)
- we're look into the PR #11505 to help unblock SSL context issues
- we'd like to validate the final changes and may request help from a community member for a QA. Alternatively when the time comes I'd be happy to hop on a call where we can walk through a quick demo
LMK if this sounds good!
This looks like a quality contribution and within a reasonable scope. I believe we can unblock it now.
As @malhotra5 mentioned, one of hesitations has been that we do not have BitBucket Server setup ourselves to test this ongoing. We've decided to handle integrations like that by documenting them as "experimental" for now.
Therefore I plan to resolve the merge conflicts and integrate this. #11505 has also resolved the ssh context blocker.