Browse Source

SONAR-14851 updated docs and upgrade notes to inform user about permissions needed

tags/9.0.0.45539
Lukasz Jarocki 3 years ago
parent
commit
901b5674ba

+ 8
- 0
server/sonar-docs/src/pages/analysis/github-integration.md View File

@@ -47,6 +47,14 @@ Specify the following settings in your app:
| **GitHub Enterprise:** Repository metadata <br> **GitHub.com:** Metadata <br> (this setting is automatically set by GitHub)| Read-only |
| Pull Requests | Read & write |
| Commit statuses | Read-only |

- For private repositories, grant access to the following **Repository permissions**:
| Permission | Access |
|---------------------|--------------|
| Contents | Read-only |

- If setting up **GitHub Authentication**, in addition to the aforementioned Repository permissions, grant access for the following **User permissions**:

| Permission | Access |

+ 3
- 0
server/sonar-docs/src/pages/setup/upgrade-notes.md View File

@@ -13,6 +13,9 @@ The JavaScript custom rule API, which was previously deprecated, has been remove
**Deprecated Plugin Java API dropped**
Parts of the Java API for plugins that were deprecated before SonarQube 7.0 have been dropped. You should compile plugins against SonarQube 9.0 to ensure they're compatible and to check if they're using a deprecated API that has been dropped.

**Reporting Quality Gate status on GitHub branches requires an additional permission**
When working in private GitHub repositories, you need to grant read-only access to the **Contents** permission on the GitHub application that you're using for SonarQube integration. See the [GitHub integration documentation](/analysis/github-integration/) for more information.

[Full release notes](https://jira.sonarsource.com/secure/ReleaseNote.jspa?projectId=10930&version=15682)

## Release 8.9 LTS Upgrade Notes

Loading…
Cancel
Save