From 4d0b5d564b2b6b507d8233d0e5d831d9a18ee2d1 Mon Sep 17 00:00:00 2001 From: Mathieu Suen Date: Thu, 31 Mar 2022 10:20:53 +0200 Subject: [PATCH] SONAR-16150 Fixing broken link in documentation --- server/sonar-docs/src/pages/extend/adding-scm.md | 2 +- .../sonar-docs/src/pages/instance-administration/security.md | 2 +- server/sonar-docs/src/pages/setup/install-cluster.md | 2 +- server/sonar-docs/src/pages/setup/upgrading.md | 4 ++-- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/server/sonar-docs/src/pages/extend/adding-scm.md b/server/sonar-docs/src/pages/extend/adding-scm.md index 970d7ebae8b..0c23a1a3d06 100644 --- a/server/sonar-docs/src/pages/extend/adding-scm.md +++ b/server/sonar-docs/src/pages/extend/adding-scm.md @@ -9,4 +9,4 @@ SonarQube Scanner uses information from the project's SCM, if available, to: * Display the most recent commit on each line the code viewer. ![Commit info is available from the margin of the code viewer](/images/commit-info-in-code-viewer.png) -The only required SCM command is "blame", which gets the last committer of each line for a given file. This command is executed by a SonarQube plugin through the extension point org.sonar.api.batch.scm.ScmProvider. See the multiple existing plugins, for instance [Git](https://docs.sonarqube.org/display/SONAR/Git+Integration), for more details. +The only required SCM command is "blame", which gets the last committer of each line for a given file. This command is executed by a SonarQube plugin through the extension point org.sonar.api.batch.scm.ScmProvider. See the multiple existing plugins, for instance [Git](https://docs.sonarqube.org/8.9/analysis/scm-integration/), for more details. diff --git a/server/sonar-docs/src/pages/instance-administration/security.md b/server/sonar-docs/src/pages/instance-administration/security.md index a0820bfdd27..80214589116 100644 --- a/server/sonar-docs/src/pages/instance-administration/security.md +++ b/server/sonar-docs/src/pages/instance-administration/security.md @@ -118,7 +118,7 @@ The way authorization is implemented in SonarQube is pretty standard. It is poss To administer groups and users, choose **Administration > Security**, and use the sub-menu items. ### User -Multiple integrations that allow the delegation of authentication are available (see the [Plugin Library](https://redirect.sonarsource.com/doc/plugin-library.html) and [Other Plugins](https://docs.sonarqube.org/display/PLUG/Other+Plugins), but you can manually create and edit users at **[Settings > Security > Users](/#sonarqube-admin#/admin/users)**. For manually-created users, login and password can be set at creation. Manually-created users can edit their passwords. +Multiple integrations that allow the delegation of authentication are available (see the [Plugin Library](https://docs.sonarqube.org/8.9/instance-administration/plugin-version-matrix/) but you can manually create and edit users at **[Settings > Security > Users](/#sonarqube-admin#/admin/users)**. For manually-created users, login and password can be set at creation. Manually-created users can edit their passwords. During both user creation and edit, you can set an account's screen name, email address. User login and email address will be implicitly recognized by the Issue Assignment feature as SCM accounts if applicable, but you can set additional SCM accounts explicitly. diff --git a/server/sonar-docs/src/pages/setup/install-cluster.md b/server/sonar-docs/src/pages/setup/install-cluster.md index 232d0edc426..2e3fd9505d1 100644 --- a/server/sonar-docs/src/pages/setup/install-cluster.md +++ b/server/sonar-docs/src/pages/setup/install-cluster.md @@ -187,7 +187,7 @@ The following is an example of the default SonarQube cluster installation proces 1. On a single application node of the cluster, download and install SonarQube Data Center Edition, following the usual [Installing the Server](/setup/install-server/) documentation. 2. Add cluster-related parameters to `$SONARQUBE_HOME/conf/sonar.properties`. -3. This is also a good opportunity to install plugins. Download and place a copy of each plugin JAR in `$SONARQUBE_HOME/extensions/plugins`. Be sure to check compatibility with your SonarQube version using the [Plugin Version Matrix](https://docs.sonarqube.org/display/PLUG/Plugin+Version+Matrix). +3. This is also a good opportunity to install plugins. Download and place a copy of each plugin JAR in `$SONARQUBE_HOME/extensions/plugins`. Be sure to check compatibility with your SonarQube version using the [Plugin Version Matrix](https://docs.sonarqube.org/8.9/instance-administration/plugin-version-matrix/). 4. Zip the directory `$SONARQUBE_HOME`. This archive is a customized SonarQube Data Center Edition package that can be copied to other nodes. **Test configuration on a single node:** diff --git a/server/sonar-docs/src/pages/setup/upgrading.md b/server/sonar-docs/src/pages/setup/upgrading.md index 9f3d4b465d1..7e52d81cd70 100644 --- a/server/sonar-docs/src/pages/setup/upgrading.md +++ b/server/sonar-docs/src/pages/setup/upgrading.md @@ -42,7 +42,7 @@ During your upgrade, tables may be duplicated to speed up the migration process, ### Upgrading from the ZIP file 1. Download and unzip the SonarQube distribution of your edition in a fresh directory, let's say `$NEW_SONAR_HOME` -2. Manually install additional plugins that are compatible with your version of SonarQube. Use the [Compatibility Matrix](https://docs.sonarqube.org/display/PLUG/Plugin+Version+Matrix) to ensure that the versions you install are compatible with your server version. Simply copying plugins from the old server to the new is not recommended; incompatible or duplicate plugins could cause startup errors. Analysis of all languages provided by your edition is available by default without plugins. +2. Manually install additional plugins that are compatible with your version of SonarQube. Use the [Compatibility Matrix](https://docs.sonarqube.org/8.9/instance-administration/plugin-version-matrix/) to ensure that the versions you install are compatible with your server version. Simply copying plugins from the old server to the new is not recommended; incompatible or duplicate plugins could cause startup errors. Analysis of all languages provided by your edition is available by default without plugins. 3. Update the contents of `sonar.properties` and `wrapper.conf` files (in `$NEW_SONAR_HOME/conf`) with the settings of the related files in the `$OLD_SONAR_HOME/conf` directory (web server URL, database, ldap settings, etc.). Do not copy-paste the old files. If you are using the Oracle DB, copy its JDBC driver into `$NEW_SONAR_HOME/extensions/jdbc-driver/oracle` 4. Stop your old SonarQube Server @@ -53,7 +53,7 @@ If you are using the Oracle DB, copy its JDBC driver into `$NEW_SONAR_HOME/exten ### Upgrading from the Docker image [[info]] -| If you're upgrading with an Oracle database or you're using additional plugins, you can reuse your extensions volume from the previous version to avoid moving plugins or drivers. Use the [Compatibility Matrix](https://docs.sonarqube.org/display/PLUG/Plugin+Version+Matrix) to ensure that your plugins are compatible with your version. Analysis of all languages provided by your edition is available by default without plugins. +| If you're upgrading with an Oracle database or you're using additional plugins, you can reuse your extensions volume from the previous version to avoid moving plugins or drivers. Use the [Compatibility Matrix](https://docs.sonarqube.org/8.9/instance-administration/plugin-version-matrix/) to ensure that your plugins are compatible with your version. Analysis of all languages provided by your edition is available by default without plugins. To upgrade SonarQube using the Docker image: -- 2.39.5