feat(bitbucket-server): Add API-driven pipeline backend for Bitbucket Server integration setup#116295
Merged
Conversation
github-actions
Bot
added
the
Scope: Backend
![sentry-warden[bot]](https://avatars.githubusercontent.com/in/2755838?s=60&v=4){kind=small}
evanpurkhiser
force-pushed
the
evanpurkhiser/feat-bitbucket-server-add-api-driven-pipeline-backend-for-bitbucket-server-integration-setup
branch
2 times, most recently
from
2d49f16 to
b88bb62
Compare
… Server integration setup Implement `get_pipeline_api_steps()` on `BitbucketServerIntegrationProvider` with two steps: installation config (validates URL, RSA private key, and consumer key length, then fetches an OAuth 1.0a request token from the Bitbucket Server instance), and an OAuth callback step that builds the authorize URL from the request token and exchanges the callback's `oauth_token` (used by Bitbucket Server as the verifier) for an access token. Legacy `InstallationConfigView`, `OAuthLoginView`, and `OAuthCallbackView` remain in place so in-flight installs can complete via the existing flow; they will be removed in a follow-up once the API flow has been validated in production.
evanpurkhiser
force-pushed
the
evanpurkhiser/feat-bitbucket-server-add-api-driven-pipeline-backend-for-bitbucket-server-integration-setup
branch
from
b88bb62 to
a2aaa5f
Compare
wedamija
approved these changes
May 27, 2026
evanpurkhiser
deleted the
evanpurkhiser/feat-bitbucket-server-add-api-driven-pipeline-backend-for-bitbucket-server-integration-setup
branch
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
2 participants
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()onBitbucketServerIntegrationProviderwith two steps: installation config (validates URL, RSA private key, and consumer key length, then fetches an OAuth 1.0a request token from the Bitbucket Server instance), and an OAuth callback step that builds the authorize URL from the request token and exchanges the callback'soauth_token(used by Bitbucket Server as the verifier) for an access token.Legacy
InstallationConfigView,OAuthLoginView, andOAuthCallbackViewremain in place so in-flight installs can complete via the existing flow; they will be removed in a follow-up (VDY-103) once the API flow has been validated in production.Ref VDY-99