From 04a29ef2b9e31605182b18f5123941366b844c7b Mon Sep 17 00:00:00 2001 From: Evgeny Mandrikov Date: Tue, 14 May 2019 15:21:36 +0200 Subject: [PATCH] Fix links in documentation --- server/sonar-docs/src/pages/scan/sonarscanner-for-ant.md | 2 +- .../src/pages/scan/sonarscanner-for-azure-devops.md | 2 +- .../sonar-docs/src/pages/scan/sonarscanner-for-jenkins.md | 8 ++++---- .../sonar-docs/src/pages/scan/sonarscanner-for-msbuild.md | 2 +- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/server/sonar-docs/src/pages/scan/sonarscanner-for-ant.md b/server/sonar-docs/src/pages/scan/sonarscanner-for-ant.md index 3aa58ee34c7..84d4a2de6fa 100644 --- a/server/sonar-docs/src/pages/scan/sonarscanner-for-ant.md +++ b/server/sonar-docs/src/pages/scan/sonarscanner-for-ant.md @@ -11,7 +11,7 @@ url: /scan/sonarscanner-for-ant/ The SonarScanner for Ant provides a `task` to allow integration of SonarQube analysis into an Apache Ant build script. -The SonarScanner for Ant is an Ant Task that is wrapper of [SonarScanner](/scan/sonarqube-scanner/), which works by invoking SonarScanner and passing to it all [properties](/analysis/analysis-parameters/) named following a `sonar.*` convention. This has the downside of not being very Ant-y, but the upside of providing instant availability of any new analysis parameter introduced by a new version of a plugin or of SonarQube itself. Therefore, successful use of the SonarScanner for Ant requires strict adherence to the property names shown below. +The SonarScanner for Ant is an Ant Task that is wrapper of [SonarScanner](/scan/sonarscanner/), which works by invoking SonarScanner and passing to it all [properties](/analysis/analysis-parameters/) named following a `sonar.*` convention. This has the downside of not being very Ant-y, but the upside of providing instant availability of any new analysis parameter introduced by a new version of a plugin or of SonarQube itself. Therefore, successful use of the SonarScanner for Ant requires strict adherence to the property names shown below. ## Use diff --git a/server/sonar-docs/src/pages/scan/sonarscanner-for-azure-devops.md b/server/sonar-docs/src/pages/scan/sonarscanner-for-azure-devops.md index c219c2eefe7..4e6127ac2e2 100644 --- a/server/sonar-docs/src/pages/scan/sonarscanner-for-azure-devops.md +++ b/server/sonar-docs/src/pages/scan/sonarscanner-for-azure-devops.md @@ -22,7 +22,7 @@ Version 4.x1.x -The SonarQube Extension embeds its own version of the [SonarScanner for MSBuild](/scan/sonarqube-scanner-for-msbuild/). +The SonarQube Extension embeds its own version of the [SonarScanner for MSBuild](/scan/sonarscanner-for-msbuild/). ## Installation diff --git a/server/sonar-docs/src/pages/scan/sonarscanner-for-jenkins.md b/server/sonar-docs/src/pages/scan/sonarscanner-for-jenkins.md index 435dc435059..5238cc65722 100644 --- a/server/sonar-docs/src/pages/scan/sonarscanner-for-jenkins.md +++ b/server/sonar-docs/src/pages/scan/sonarscanner-for-jenkins.md @@ -11,10 +11,10 @@ This plugin lets you centralize the configuration of SonarQube server connection Then you can trigger SonarQube analysis from Jenkins using standard Jenkins Build Steps or [Jenkins Pipeline DSL](https://jenkins.io/solutions/pipeline/) to trigger analysis with: -* [SonarScanner](/scan/sonarqube-scanner/) -* [SonarScanner for Maven](/scan/sonarqube-scanner-for-maven/) -* [SonarScanner for Gradle](/scan/sonarqube-scanner-for-gradle/) -* [SonarScanner for MSBuild](/scan/sonarqube-scanner-for-msbuild/) +* [SonarScanner](/scan/sonarscanner/) +* [SonarScanner for Maven](/scan/sonarscanner-for-maven/) +* [SonarScanner for Gradle](/scan/sonarscanner-for-gradle/) +* [SonarScanner for MSBuild](/scan/sonarscanner-for-msbuild/) Once the job is complete, the plugin will detect that a SonarQube analysis was made during the build and display a badge and a widget on the job page with a link to the SonarQube dashboard as well as quality gate status. diff --git a/server/sonar-docs/src/pages/scan/sonarscanner-for-msbuild.md b/server/sonar-docs/src/pages/scan/sonarscanner-for-msbuild.md index 842d4418c08..7cd6dbbdee6 100644 --- a/server/sonar-docs/src/pages/scan/sonarscanner-for-msbuild.md +++ b/server/sonar-docs/src/pages/scan/sonarscanner-for-msbuild.md @@ -14,7 +14,7 @@ url: /scan/sonarscanner-for-msbuild/ The SonarScanner for MSBuild is the recommended way to launch an analysis for projects/solutions using MSBuild or dotnet command as a build tool. It is the result of a [collaboration between SonarSource and Microsoft](http://www.sonarqube.org/announcing-sonarqube-integration-with-msbuild-and-team-build/). -SonarScanner for MSBuild is distributed as a standalone command line executable, as a extension for [Azure DevOps](/scan/sonarqube-scanner-for-azure-devops/)[Azure DevOps Server](/scan/sonarqube-scanner-for-azure-devops/), and as a plugin for [Jenkins](/scan/sonarqube-scanner-for-jenkins/). +SonarScanner for MSBuild is distributed as a standalone command line executable, as a extension for [Azure DevOps](/scan/sonarscanner-for-azure-devops/)[Azure DevOps Server](/scan/sonarscanner-for-azure-devops/), and as a plugin for [Jenkins](/scan/sonarscanner-for-jenkins/). It supports .Net Core multi-platform projects and it can be used on non-Windows platforms. -- 2.39.5