This article reviews how to configure a Bitbucket Server External Service, which allows you to sync Stoplight both users and specifications with data stored in Bitbucket.
Heads up!
This article discusses Bitbucket Server, Atlassian's on-premise Git service. For Bitbucket Cloud (Atlassian's hosted service), please refer to the documentation here.
Before continuing, be sure to:
- Have a valid Bitbucket Server login
- Have the URL to your Bitbucket Server instance
- Be logged in to Stoplight as an Administrator
From the Stoplight Landing Screen
From the Admin Settings
From the External Services Screen
Registering the Bitbucket Service
Unsure of what to use for your API URL?
The Bitbucket Server API URL defaults to the path "/rest/api/1.0". For example, if your Bitbucket server is usually accessed through https://bitbucket.example.com, this would make the API URL:
https://bitbucket.example.com/rest/api/1.0
Also note that some Bitbucket Servers might be configured to use a base path, for example "/git". If your server uses a base path, be sure to include that before the "/rest/api/1.0". For example:
https://bitbucket.example.com/git/rest/api/1.0
Get in touch if you have any issues finding the right configuration options.
Next Steps
Now that you've configured Gitlab, continue on to Connecting Your Accounts or Getting Started with Studio to start creating APIs.