You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure Pipelines can automatically build and validate every pull request and commit to your BitBucket Cloud repository. This article describes how to configure the integration between BitBucket Cloud and Azure Pipelines.
15
+
Azure Pipelines can automatically build and validate every pull request and commit to your Bitbucket Cloud repository. This article describes how to configure the integration between Bitbucket Cloud and Azure Pipelines.
16
16
17
-
BitBucket and Azure Pipelines are two independent services that integrate well together. Your BitBucket Cloud users do not automatically get access to Azure Pipelines. You must add them explicitly to Azure Pipelines.
17
+
Bitbucket and Azure Pipelines are two independent services that integrate well together. Your Bitbucket Cloud users do not automatically get access to Azure Pipelines. You must add them explicitly to Azure Pipelines.
18
18
19
-
## Access to BitBucket repositories
19
+
## Access to Bitbucket repositories
20
20
21
21
# [YAML](#tab/yaml/)
22
22
23
-
You create a new pipeline by first selecting a BitBucket Cloud repository and then a YAML file in that repository. The repository in which the YAML file is present is called `self` repository. By default, this is the repository that your pipeline builds.
23
+
You create a new pipeline by first selecting a Bitbucket Cloud repository and then a YAML file in that repository. The repository in which the YAML file is present is called `self` repository. By default, this is the repository that your pipeline builds.
24
24
25
25
You can later configure your pipeline to check out a different repository or multiple repositories. To learn how to do this, see [multi-repo checkout](multi-repo-checkout.md).
26
26
27
27
# [Classic](#tab/classic/)
28
28
29
-
You create a new pipeline by first selecting **BitBucket Cloud** for repository type, and then one of the repositories you have access to.
29
+
You create a new pipeline by first selecting **Bitbucket Cloud** for repository type, and then one of the repositories you have access to.
30
30
31
31
---
32
32
33
33
Azure Pipelines must be granted access to your repositories to trigger their builds, and fetch their code during builds.
34
34
35
-
There are 2 authentication types for granting Azure Pipelines access to your BitBucket Cloud repositories while creating a pipeline.
35
+
There are 2 authentication types for granting Azure Pipelines access to your Bitbucket Cloud repositories while creating a pipeline.
| 1. [OAuth](#oauth-authentication)| Your personal BitBucket identity |
40
-
| 2. [Username and password](#password-authentication)| Your personal BitBucket identity |
39
+
| 1. [OAuth](#oauth-authentication)| Your personal Bitbucket identity |
40
+
| 2. [Username and password](#password-authentication)| Your personal Bitbucket identity |
41
41
42
42
### OAuth authentication
43
43
44
-
OAuth is the simplest authentication type to get started with for repositories in your BitBucket account. BitBucket status updates will be performed on behalf of your personal BitBucket identity. For pipelines to keep working, your repository access must remain active.
44
+
OAuth is the simplest authentication type to get started with for repositories in your Bitbucket account. Bitbucket status updates will be performed on behalf of your personal Bitbucket identity. For pipelines to keep working, your repository access must remain active.
45
45
46
-
To use OAuth, login to BitBucket when promoted during pipeline creation. Then, click **Authorize** to authorize with OAuth. An OAuth connection will be saved in your Azure DevOps project for later use, as well as used in the pipeline being created.
46
+
To use OAuth, login to Bitbucket when promoted during pipeline creation. Then, click **Authorize** to authorize with OAuth. An OAuth connection will be saved in your Azure DevOps project for later use, as well as used in the pipeline being created.
47
47
48
48
### Password authentication
49
49
50
-
Builds and BitBucket status updates will be performed on behalf of your personal identity. For builds to keep working, your repository access must remain active.
50
+
Builds and Bitbucket status updates will be performed on behalf of your personal identity. For builds to keep working, your repository access must remain active.
51
51
52
52
To create a password connection, visit [Service connections](../library/service-endpoints.md) in your Azure DevOps project settings.
53
-
Create a new BitBucket service connection and provide the user name and password to connect to your BitBucket Cloud repository.
53
+
Create a new Bitbucket service connection and provide the user name and password to connect to your Bitbucket Cloud repository.
54
54
55
55
## CI triggers
56
56
@@ -61,7 +61,7 @@ Continuous integration (CI) triggers cause a pipeline to run whenever you push a
@@ -115,7 +115,7 @@ You can specify the full name of the branch (for example, `master`) or a wildcar
115
115
> [!NOTE]
116
116
> If you use [templates](../process/templates.md) to author YAML files, then you can only specify triggers in the main YAML file for the pipeline. You cannot specify triggers in the template files.
117
117
118
-
BitBucket creates a new _ref_ when a pull request is created. The ref points to a _merge commit_, which is the merged code between the source and target branches of the pull request. The PR validation pipeline builds the commit this ref points to. This means that the YAML file that is used to run the pipeline is also a merge between the source and the target branch. As a result, the changes you make to the YAML file in source branch of the pull request can override the behavior defined by the YAML file in target branch.
118
+
Bitbucket creates a new _ref_ when a pull request is created. The ref points to a _merge commit_, which is the merged code between the source and target branches of the pull request. The PR validation pipeline builds the commit this ref points to. This means that the YAML file that is used to run the pipeline is also a merge between the source and the target branch. As a result, the changes you make to the YAML file in source branch of the pull request can override the behavior defined by the YAML file in target branch.
119
119
120
120
If no `pr` triggers appear in your YAML file, pull request validations are automatically enabled for all
121
121
branches, as if you wrote the following `pr` trigger. This configuration triggers a build when any
@@ -204,7 +204,7 @@ For included branches, a build will be triggered on each push to a pull request
204
204
205
205
## FAQ
206
206
207
-
Problems related to BitBucket integration fall into the following categories:
207
+
Problems related to Bitbucket integration fall into the following categories:
208
208
209
209
* **[Failing triggers](#failing-triggers):** My pipeline is not being triggered when I push an update to the repo.
210
210
* **[Wrong version](#wrong-version):** My pipeline runs, but it is using an unexpected version of the source/YAML.
@@ -213,7 +213,7 @@ Problems related to BitBucket integration fall into the following categories:
213
213
214
214
[!INCLUDE [qa](includes/qa2.md)]
215
215
216
-
* Webhooks are used to communicate updates from BitBucket to Azure Pipelines. In BitBucket, navigate to the settings for your repository, then to Webhooks. Verify that the webhooks exist.
216
+
* Webhooks are used to communicate updates from Bitbucket to Azure Pipelines. In Bitbucket, navigate to the settings for your repository, then to Webhooks. Verify that the webhooks exist.
Copy file name to clipboardExpand all lines: docs/pipelines/repos/github-enterprise.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -112,7 +112,7 @@ Problems related to GitHub Enterprise integration fall into the following catego
112
112
113
113
### Failing checkout
114
114
115
-
Do you use Microsoft-hosted agents? If so, these agents may not be able to reach your BitBucket server. See [Not reachable from Microsoft-hosted agents](#not-reachable-from-microsoft-hosted-agents) for more information.
115
+
Do you use Microsoft-hosted agents? If so, these agents may not be able to reach your Bitbucket server. See [Not reachable from Microsoft-hosted agents](#not-reachable-from-microsoft-hosted-agents) for more information.
Copy file name to clipboardExpand all lines: docs/pipelines/repos/multi-repo-checkout.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -141,7 +141,7 @@ You can trigger a pipeline when an update is pushed to the `self` repository or
141
141
- You keep your YAML file in a separate repository from the application code. You want to trigger the pipeline every time an update is pushed to the application repository.
142
142
143
143
> [!NOTE]
144
-
> Repository resource triggers only work for Azure Repos Git repositories at present. They do not work for GitHub or BitBucket repository resources.
144
+
> Repository resource triggers only work for Azure Repos Git repositories at present. They do not work for GitHub or Bitbucket repository resources.
145
145
146
146
If you do not specify a `trigger` section in a repository resource, then the pipeline won't be triggered by changes to that repository. If you specify a `trigger` section, then the behavior for triggering is similar to how CI triggers work for the self repository.
0 commit comments