{% if not item.all-repos-installed? %}
{% ifequal item.config-set.metadata.provider-id :bitbucket %}
Pull Requests integration is enabled, but some of the projects lack the webhooks (have you deleted them?).
Disable and enable the integration.
Bitbucket projects with their webhook status:
{% for repo in item.repos %}
{{repo.owner-login}}/{{repo.repo-slug}} :
{% if repo.ci-status-string %}
{{ repo.ci-status-string }}
{% else %}
{% if repo.ci-installed? %}
INSTALLED
{% else %}
NOT INSTALLED!
{% endif %}
{% endif %}
{% endfor %}
{% endifequal %}
{% endif %}
CodeScene can post a Build Status on your Pull Requests. Build status can be made a requirement
for the Pull Request and can act as a Quality Gate.
CodeScene can post a Code Insights Report. A negative report will not prevent merges.
If Code Insights Report is enabled, CodeScene can add annotations to specific lines of files where code degradations and improvements occurred.
You can specify configuration settings or select an Connection Settings Preset.
Specify the Bitbucket user email address.Specify a Bitbucket API token with scopes (created via Create API token with scopes at id.atlassian.com). Required scopes: read:pullrequest:bitbucket, write:pullrequest:bitbucket, read:webhook:bitbucket, write:webhook:bitbucket, delete:webhook:bitbucket, and read:repository:bitbucket.
Advanced Settings
Specify the Bitbucket API URL. If left blank, a default API URL is constructed from the repository paths.
The external webhooks will call CodeScene using this Host URL. If left blank, the global Host URL is used.