aboutsummaryrefslogtreecommitdiffstats
path: root/server/sonar-docs/src/pages/analysis
diff options
context:
space:
mode:
authormichaelbirnstiehl <michael.birnstiehl@sonarsource.com>2019-12-12 08:32:06 -0600
committerSonarTech <sonartech@sonarsource.com>2019-12-16 20:46:14 +0100
commitb5fd0052d954a477c0b598b51f1e2042ab37d439 (patch)
tree74161d027c273a03703ef8e15f1bf3c2af38fc58 /server/sonar-docs/src/pages/analysis
parent2918662cfdad093cf6608b73b090588da6a8ce66 (diff)
downloadsonarqube-b5fd0052d954a477c0b598b51f1e2042ab37d439.tar.gz
sonarqube-b5fd0052d954a477c0b598b51f1e2042ab37d439.zip
DOCS add GitLab minimum version
Diffstat (limited to 'server/sonar-docs/src/pages/analysis')
-rw-r--r--server/sonar-docs/src/pages/analysis/pr-decoration.md38
1 files changed, 12 insertions, 26 deletions
diff --git a/server/sonar-docs/src/pages/analysis/pr-decoration.md b/server/sonar-docs/src/pages/analysis/pr-decoration.md
index 335ee200f7e..fb66407a977 100644
--- a/server/sonar-docs/src/pages/analysis/pr-decoration.md
+++ b/server/sonar-docs/src/pages/analysis/pr-decoration.md
@@ -42,11 +42,7 @@ Click your ALM provider below to expand the instructions on decorating your Pull
|
| ### Setting your global settings
|
-| To set your global settings in SonarQube:
-|
-| 1. Navigate to **Administration > Configuration > General Settings > Pull Request Decoration**.
-| 2. Select the **GitHub** tab.
-| 3. Click the **Create configuration** button.
+| To set your global settings in SonarQube, navigate to **Administration > Configuration > General Settings > Pull Request Decoration** and select the **GitHub** tab.
|
| From here, set your **Configuration Name**, **GitHub Instance URL**, **GitHub App ID**, and your GitHub App's **Private Key** (that was generated above in the **Creating a GitHub App** section).
|
@@ -61,17 +57,13 @@ Click your ALM provider below to expand the instructions on decorating your Pull
|
| *Minimum BitBucket Server version 5.15*
|
+| A Bitbucket Server user account is used to decorate Pull Requests. We recommend creating a dedicated Bitbucket Server account with Administrator permissions to decorate Pull Requests. You need a [Personal Access Token](https://confluence.atlassian.com/bitbucketserver0515/personal-access-tokens-961275199.html) from this account with **Write** permission for the repositories that will be analyzed.
+|
| To add Pull Request decoration on Bitbucket Server, you need to update your global and project settings.
|
| ### Setting your global settings
|
-| A Bitbucket Server user account is used to decorate Pull Requests. We recommend creating a dedicated Bitbucket Server account with Administrator permissions to decorate Pull Requests. You need a [Personal Access Token](https://confluence.atlassian.com/bitbucketserver0515/personal-access-tokens-961275199.html) from this account with **Write** permission for the repositories that will be analyzed.
-|
-| To set your global settings in SonarQube:
-|
-| 1. Navigate to **Administration > Configuration > General Settings > Pull Request Decoration**.
-| 2. Select the **Bitbucket Server** tab.
-| 3. Click the **Create configuration** button.
+| To set your global settings in SonarQube, navigate to **Administration > Configuration > General Settings > Pull Request Decoration** and select the **Bitbucket Server** tab.
|
| From here, set your **Configuration name**, **Bitbucket Server URL**, and the **Personal Access Token** of the account you're using to decorate your Pull Requests.
|
@@ -84,17 +76,13 @@ Click your ALM provider below to expand the instructions on decorating your Pull
[[collapse]]
| ## Azure DevOps Server
|
+| An Azure DevOps Server user account is used to decorate Pull Requests. We recommend creating a dedicated Azure DevOps Server account with Administrator permissions to decorate Pull Requests. 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.
+|
| To add Pull Request decoration on Azure DevOps Server, you need to update your global and project settings.
|
| ### Setting your global settings
|
-| An Azure DevOps Server user account is used to decorate Pull Requests. We recommend creating a dedicated Azure DevOps Server account with Administrator permissions to decorate Pull Requests. 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.
-|
-| To set your global settings in SonarQube:
-|
-| 1. Navigate to **Administration > Configuration > General Settings > Pull Request Decoration**.
-| 1. Select the **Azure DevOps Server** tab.
-| 1. Click the **Create configuration** button.
+| To set your global settings in SonarQube, navigate to **Administration > Configuration > General Settings > Pull Request Decoration** and select the **Azure DevOps Server** tab.
|
| From here, set your **Configuration name** and the **Personal Access Token** of the account you're using to decorate your Pull Requests.
|
@@ -107,17 +95,15 @@ Click your ALM provider below to expand the instructions on decorating your Pull
[[collapse]]
| ## GitLab
|
-| To add Merge Request decoration to GitLab, you need to update your global and project settings.
+|*Minimum GitLab version 11.7*
|
-| ### Setting your global settings
+| A GitLab user account is used to decorate Merge Requests. We recommend creating a dedicated GitLab account with at least **Reporter** [permissions](https://docs.gitlab.com/ee/user/permissions.html) (the account needs permission to leave comments) to decorate Merge Requests. You need a Personal Access Token from this account with the scope authorized for **api** for the repositories that will be analyzed.
|
-| A GitLab user account is used to decorate Merge Requests. We recommend creating a dedicated GitLab account with at least **Reporter** [permissions](https://docs.gitlab.com/ee/user/permissions.html) to decorate Merge Requests. This user account needs permissions to leave comments. You need a Personal Access Token from this account with the scope authorized for **api** for the repositories that will be analyzed.
+| To add Merge Request decoration to GitLab, you also need to update your global and project settings.
|
-| To set your global settings in SonarQube:
+| ### Setting your global settings
|
-| 1. Navigate to **Administration > Configuration > General Settings > Pull Request Decoration**.
-| 1. Select the **GitLab** tab.
-| 1. Click the **Create configuration** button.
+| To set your global settings in SonarQube, navigate to **Administration > Configuration > General Settings > Pull Request Decoration** and select the **GitLab** tab.
|
| From here, set your **Configuration name** and the **Personal Access Token** of the account you're using to decorate your Merge Requests.
|