Bitbucket
Port's Bitbucket integration allows you to model Bitbucket cloud resources in your software catalog and ingest data into them.
This documentation covers Port's integration with Bitbucket Cloud. For information about integrating with Bitbucket Server (Self-Hosted), please refer to the Bitbucket Server integration documentation.
Overviewโ
This integration allows you to:
- Map and organize your desired Bitbucket cloud resources and their metadata in Port (see supported resources below).
- Watch for Bitbucket object changes (create/update/delete) in real-time, and automatically apply the changes to your software catalog.
- Map and ingest monorepo repositories.
Supported resourcesโ
The resources that can be ingested from Bitbucket into Port are listed below.
It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
Setupโ
To install Port's Bitbucket cloud integration, see the installation page.
Configurationโ
Port integrations use a YAML mapping block to ingest data from the third-party api into Port.
The mapping makes use of the JQ JSON processor to select, modify, concatenate, transform and perform other operations on existing fields and values from the integration API.
Capabilitiesโ
Ingesting Git objectsโ
By using Port's Bitbucket integration, you can automatically ingest Bitbucket resources into Port based on real-time events.
The integration allows you to ingest a variety of objects resources provided by the Bitbucket API, including repositories, pull requests and files. It also allows you to perform "extract, transform, load (ETL)" on data from the Bitbucket API into the desired software catalog data model.
Permissionsโ
Port's Bitbucket integration requires the following scopes to be enabled on either a workspace token or app password:
workspace
:read
;project
:read
;repository
:read
;pullrequest
:read
;webhooks
.
You will be prompted to add these permissions while creating a new workspace token or app password.
Examplesโ
Refer to the examples page for practical configurations and their corresponding blueprint definitions.
Relevant Guidesโ
For relevant guides and examples, see the guides section.
Advancedโ
Refer to the advanced page for advanced use cases and examples.