feat(bitbucket): Add API-driven pipeline backend for Bitbucket integration setup#112396
Merged
evanpurkhiser merged 1 commit intomasterfrom Apr 8, 2026
Conversation
c3091db to
eba6218
Compare
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit eba6218. Configure here.
Contributor
Backend Test FailuresFailures on
|
…ation setup Implement `get_pipeline_api_steps()` on `BitbucketIntegrationProvider` with a single authorize step that verifies the Atlassian Connect JWT from Bitbucket's addon authorization flow. The frontend posts the JWT received from the popup callback, and the backend validates it against the original callback path using `get_integration_from_jwt`. Updates `build_integration()` to handle both legacy and API state paths. Ref [VDY-41](https://linear.app/getsentry/issue/VDY-41/bitbucket-api-driven-integration-setup)
eba6218 to
f1cd277
Compare
leeandher
approved these changes
Apr 8, 2026
cmanallen
approved these changes
Apr 8, 2026
wedamija
approved these changes
Apr 8, 2026
george-sentry
pushed a commit
that referenced
this pull request
Apr 9, 2026
…ation setup (#112396) Implement `get_pipeline_api_steps()` on `BitbucketIntegrationProvider` with a single authorize step that verifies the Atlassian Connect JWT from Bitbucket's addon authorization flow. The frontend posts the JWT received from the popup callback, and the backend validates it against the original callback path using `get_integration_from_jwt`. Updates `build_integration()` to handle both legacy and API state paths. Ref [VDY-41](https://linear.app/getsentry/issue/VDY-41/bitbucket-api-driven-integration-setup)
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Implement
get_pipeline_api_steps()onBitbucketIntegrationProviderwitha single authorize step that verifies the Atlassian Connect JWT from
Bitbucket's addon authorization flow. The frontend posts the JWT received
from the popup callback, and the backend validates it against the original
callback path using
get_integration_from_jwt. Updatesbuild_integration()to handle both legacy and API state paths.
Ref VDY-41