Bitbucket Data Center support

jekyll/_cci2/add-ssh-key.adoc

@@ -14,7 +14,7 @@ contentTags:
 
 Add additional SSH keys to your project for access to deploy other services or to write to, or checkout code from other repositories.
 
-If you want to set up an SSH key in order to checkout code from additional repositories in GitHub (xref:github-integration#[GitHub OAuth app only]) or Bitbucket within a job, refer to the xref:github-integration#enable-your-project-to-check-out-additional-private-repositories[GitHub] or xref:bitbucket-integration#enable-your-project-to-check-out-additional-private-repositories[Bitbucket] integration pages.  If you need additional SSH keys to access other services and your org is set up to the use xref:github-integration#[GitHub OAuth app] or Bitbucket, follow the steps below.
+If you want to set up an SSH key in order to checkout code from additional repositories in GitHub (xref:github-integration#[GitHub OAuth app only]) or Bitbucket Cloud within a job, refer to the xref:github-integration#enable-your-project-to-check-out-additional-private-repositories[GitHub OAuth app] or xref:bitbucket-integration#enable-your-project-to-check-out-additional-private-repositories[Bitbucket Cloud] integration pages.  If you need additional SSH keys to access other services and your org is set up to the use xref:github-integration#[GitHub OAuth app] or Bitbucket Cloud, follow the steps below.
 
 You may need to add the public key to `~/.ssh/authorized_keys` in order to add SSH keys.
 
@@ -34,14 +34,14 @@ CircleCI cannot decrypt SSH keys, therefore every new key must have an empty pas
 
 . In a terminal, generate the key with `ssh-keygen -t ed25519 -C "your_email@example.com"`. See link:https://www.ssh.com/ssh/keygen/[Secure Shell documentation] for additional details.
 . In the CircleCI application, go to your project's settings by clicking the *Project Settings* button (top-right on the *Pipelines* page of the project).
-. On the *Project Settings* page, click on *SSH Keys*.
+. On the *Project Settings* page, select *SSH Keys*.
 . Scroll down to the *Additional SSH Keys* section.
 +
 If you have a GitLab integration, you will find that an additional SSH key already exists. This was created automatically by CircleCI during the project creation process. This key is used to checkout your code so it should not be removed.
-. Click the *Add SSH Key* button.
+. Select *Add SSH Key*.
 . In the *Hostname* field, enter the key's associated host (for example, `git.heroku.com`). If you do not specify a hostname, the key will be used for all hosts.
 . In the *Private Key* field, paste the SSH key you are adding.
-. Click the *Add SSH Key* button.
+. Select *Add SSH Key*.
 
 [#add-ssh-keys-to-a-job]
 == 2. Add SSH keys to a job
@@ -79,7 +79,8 @@ If you need to add multiple SSH keys with blank hostnames to your project, you w
 [#see-also]
 == See also
 
-* xref:github-integration#[GitHub OAuth Integration]
-* xref:github-apps-integration#[GitHub Apps Integration]
-* xref:bitbucket-integration#[Bitbucket Integration]
-* xref:gitlab-integration#[GitLab CI Integration]
+* xref:github-integration#[GitHub OAuth app integration]
+* xref:github-apps-integration#[GitHub App integration]
+* xref:bitbucket-integration#[Bitbucket integration]
+* xref:bitbucket-data-center-integration#[Bitbucket Data Center integration]
+* xref:gitlab-integration#[GitLab integration]

jekyll/_cci2/api-developers-guide.adoc

@@ -92,7 +92,7 @@ curl --header "Circle-Token: $CIRCLE_TOKEN" \
 == Getting started with the API
 
 [#github-and-bitbucket-projects]
-=== GitHub OAuth and Bitbucket projects
+=== GitHub OAuth and Bitbucket Cloud projects
 
 [NOTE]
 ====
@@ -120,10 +120,10 @@ The `project_slug` is also included in the response payload when looking up a pi
 
 image::{{ site.baseurl }}/assets/img/docs/api-structure.png[API structure]
 
-For GitHub and Bitbucket projects, `project_slug` is currently usable as a human-readable identifier for a given project. For <<gitlab-saas-support-projects,GitHub App and GitLab projects>>, the slug format has been changed.
+For GitHub and Bitbucket Cloud projects, `project_slug` is currently usable as a human-readable identifier for a given project. For <<gitlab-saas-support-projects,GitHub App, GitLab and Bitbucket Data Center projects>>, the slug format has been changed.
 
 [#gitlab-saas-support-projects]
-=== GitHub App and GitLab projects
+=== GitHub App, GitLab and Bitbucket Data Center projects
 
 [NOTE]
 ====
@@ -191,8 +191,8 @@ Many of the API calls make use of the `+{project-slug}+` triplet, described <<ge
 [#prerequisites]
 === Prerequisites
 
-* A GitHub, Bitbucket, or GitLab account with a repository to set up with CircleCI. *GitHub App and GitLab users:* Note the <<gitlab-saas-support-projects,change in the definition>> for the project slug references in the examples and use cases on the rest of this document.
-* Completion of the CircleCI link:{{ site.baseurl }}/getting-started[onboarding].
+* A GitHub, Bitbucket, or GitLab account with a repository to set up with CircleCI. *GitHub App, GitLab and Bitbucket Data Center users:* Note the <<gitlab-saas-support-projects,change in the definition>> for the project slug references in the examples and use cases on the rest of this document.
+* Completion of the CircleCI xref:getting-started#[onboarding].
 
 [#steps]
 === Steps

jekyll/_cci2/api-intro.adoc

@@ -37,11 +37,11 @@ NOTE: Currently, xref:managing-api-tokens#creating-a-personal-api-token[Personal
 
 [NOTE]
 ====
-*GitHub App and GitLab users:* Note that the definition of *project slug* provided in this section, as well as its usage throughout this document applies to GitHub and Bitbucket projects only. GitLab projects currently use a new slug format:
+*GitHub App and GitLab users:* Note that the definition of *project slug* provided in this section, as well as its usage throughout this document applies to GitHub and Bitbucket Cloud projects only. GitLab, GitHub App and Bitbucket Data Center projects currently use a new slug format:
 
 `circleci/:slug-remainder`
 
-The project slug for GitLab projects can be found by navigating to your project in the CircleCI web app and taking the string from the browser address bar. The slug must be treated as an opaque string and passed in its entirety in API requests. Read the link:{{site.baseurl}}/api-developers-guide/#getting-started-with-the-api/[API Developer's Guide] for more details.
+The project slug for GitLab, GitHub App and Bitbucket Data Center projects can be found by navigating to your project in the CircleCI web app and taking the string from the browser address bar. The slug must be treated as an opaque string and passed in its entirety in API requests. Read the link:{{site.baseurl}}/api-developers-guide/#getting-started-with-the-api/[API Developer's Guide] for more details.
 ====
 
 CircleCI API v2 uses a string representation called the `project_slug`, which is a "triplet" of your version control system (VCS), the name of your organization, and the name of the repository. `project_slug` takes the following form:
@@ -51,12 +51,12 @@ CircleCI API v2 uses a string representation called the `project_slug`, which is
 :vcs_type/:org_name/:repo_name
 ----
 
-The `project_slug` is included in the response payload when pulling information about a project as well as when looking up a pipeline or workflow by ID. The `project_slug` can then be used to get information about the project. For GitHub OAuth app and Bitbucket projects, it is currently usable as a human-readable identifier for a given project.
+The `project_slug` is included in the response payload when pulling information about a project as well as when looking up a pipeline or workflow by ID. The `project_slug` can then be used to get information about the project. For GitHub OAuth app and Bitbucket Cloud projects, it is currently usable as a human-readable identifier for a given project.
 
 [#authentication]
 == Authentication
 
-The CircleCI API v2 enables users to be authenticated by sending your xref:managing-api-tokens#creating-a-personal-api-token[Personal API token] as a HTTP header in the request, with the name `Circle-Token` and the token as the value. You can find examples in the xref:api-developers-guide#[API Developer's Guide].
+The CircleCI API v2 enables users to be authenticated by sending your xref:managing-api-tokens#creating-a-personal-api-token[Personal API token] as an HTTP header in the request, with the name `Circle-Token` and the token as the value. You can find examples in the xref:api-developers-guide#[API Developer's Guide].
 
 [discrete#triggering-a-pipeline-with-parameters-example]
 ==== Triggering a pipeline with parameters example