The Bitbucket Cloud Integration have to be configured on your CDS by a CDS Administrator.
This integration allows you to link a Git Repository hosted by your Bitbucket Cloud to a CDS Application.
This integration enables some features:
{CDS_UI_URL}/cdsapi/repositories_manager/oauth2/callback
(if you are in development mode you have to omit /cdsapi and replace {CDS_UI_URL} with your API URL)Account Read
, Workspace membership Read
, Repositories Read
, Pull requests Read
, Webhooks Read and Write
Key
and Secret
. It correspond to clientId
and clientSecret
in the CDS config.toml file.On https://bitbucket.org/account/settings/app-passwords/ create a new app password with the following scopes:
Email
and Read
Read
Read
Read
and Write
Read
and Write
Read and write
Create a yml file:
version: v1.0
name: bitbucket-cloud
type: bitbucketcloud
description: "My Bitbucket Cloud"
auth:
user: my-user-on-bitbucket-cloud
token: the-long-token-here
options:
disableStatus: false # Set to true if you don't want CDS to push statuses on the VCS server - optional
disableStatusDetails: false # Set to true if you don't want CDS to push CDS URL in statuses on the VCS server - optional
disablePolling: false # Does polling is supported by VCS Server - optional
disableWebHooks: false # Does webhooks are supported by VCS Server - optional
cdsctl project vcs import YOUR_CDS_PROJECT_KEY vcs-bitbucketcloud.yml
For now, CDS supports push events. CDS uses this push event to remove existing runs for deleted branches (24h after branch deletion).