diff options
| author | michaelbirnstiehl <michael.birnstiehl@sonarsource.com> | 2021-08-26 10:54:56 -0500 |
|---|---|---|
| committer | sonartech <sonartech@sonarsource.com> | 2021-08-30 20:08:19 +0000 |
| commit | 1e78c066e5eed1752abfbcc91b977703d5dd0c51 (patch) | |
| tree | c47f5f3dd2b9b42b0c29429c7873e1bbf81ba794 /server/sonar-docs/src/pages/analysis/azuredevops-integration.md | |
| parent | eb5fd708f79d83bbfc2683dea406c875c4d2541e (diff) | |
| download | sonarqube-1e78c066e5eed1752abfbcc91b977703d5dd0c51.tar.gz sonarqube-1e78c066e5eed1752abfbcc91b977703d5dd0c51.zip | |
SONAR-15326 Document the encryption of DevOps platform secrets
Diffstat (limited to 'server/sonar-docs/src/pages/analysis/azuredevops-integration.md')
| -rw-r--r-- | server/sonar-docs/src/pages/analysis/azuredevops-integration.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/server/sonar-docs/src/pages/analysis/azuredevops-integration.md b/server/sonar-docs/src/pages/analysis/azuredevops-integration.md index 540e074e670..62b1528d00c 100644 --- a/server/sonar-docs/src/pages/analysis/azuredevops-integration.md +++ b/server/sonar-docs/src/pages/analysis/azuredevops-integration.md @@ -29,7 +29,9 @@ To import your Azure DevOps repositories into SonarQube, you need to first set y - **Configuration Name** (Enterprise and Data Center Edition only) – The name used to identify your Azure DevOps configuration at the project level. Use something succinct and easily recognizable. - **Azure DevOps collection/organization URL** – If you are using Azure DevOps Server, provide your full Azure DevOps collection URL. For example, `https://ado.your-company.com/DefaultCollection`. If you are using Azure DevOps Services, provide your full Azure DevOps organization URL. For example, `https://dev.azure.com/your_organization`. -- **Personal Access Token** – An Azure DevOps user account is used to decorate Pull Requests. We recommend using a dedicated Azure DevOps account with Administrator permissions. You need a [personal access token](https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=tfs-2017&tabs=preview-page) from this account with the scope authorized for **Code > Read & Write** for the repositories that will be analyzed. This personal access token is used for pull request decoration, and you'll be asked for another personal access token for importing projects in the following section. +- **Personal Access Token** – An Azure DevOps user account is used to decorate Pull Requests. We recommend using a dedicated Azure DevOps account with Administrator permissions. You need a [personal access token](https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=tfs-2017&tabs=preview-page) from this account with the scope authorized for **Code > Read & Write** for the repositories that will be analyzed. Administrators can encrypt this token at **Administration > Configuration > Encryption**. See the **Settings Encryption** section of the [Security](/instance-administration/security/) page for more information. + + This personal access token is used to report your Quality Gate status to your pull requests. You'll be asked for another personal access token for importing projects in the following section. ### Adding a personal access token for importing repositories After setting your global settings, you can add a project from Azure DevOps by clicking the **Add project** button in the upper-right corner of the **Projects** homepage and selecting **Azure DevOps**. |