diff options
Diffstat (limited to 'server/sonar-docs/src/pages/analysis')
| -rw-r--r-- | server/sonar-docs/src/pages/analysis/background-tasks.md | 1 | ||||
| -rw-r--r-- | server/sonar-docs/src/pages/analysis/generic-issue.md (renamed from server/sonar-docs/src/pages/analysis/generic_issue.md) | 4 | ||||
| -rw-r--r-- | server/sonar-docs/src/pages/analysis/generic-test.md (renamed from server/sonar-docs/src/pages/analysis/generic_test.md) | 1 | ||||
| -rw-r--r-- | server/sonar-docs/src/pages/analysis/overview.md (renamed from server/sonar-docs/src/pages/analysis/index.md) | 3 | ||||
| -rw-r--r-- | server/sonar-docs/src/pages/analysis/pull-request.md | 3 | ||||
| -rw-r--r-- | server/sonar-docs/src/pages/analysis/scm-integration.md (renamed from server/sonar-docs/src/pages/analysis/scm_integration.md) | 3 |
6 files changed, 11 insertions, 4 deletions
diff --git a/server/sonar-docs/src/pages/analysis/background-tasks.md b/server/sonar-docs/src/pages/analysis/background-tasks.md index 62157db41da..c12fcfde131 100644 --- a/server/sonar-docs/src/pages/analysis/background-tasks.md +++ b/server/sonar-docs/src/pages/analysis/background-tasks.md @@ -1,5 +1,6 @@ --- title: Background Tasks +url: /analysis/background-tasks/ --- A Background Task can be: diff --git a/server/sonar-docs/src/pages/analysis/generic_issue.md b/server/sonar-docs/src/pages/analysis/generic-issue.md index 33c3ff456f6..27ef5577131 100644 --- a/server/sonar-docs/src/pages/analysis/generic_issue.md +++ b/server/sonar-docs/src/pages/analysis/generic-issue.md @@ -1,5 +1,6 @@ --- title: Generic Issue Data +url: /analysis/generic-issue/ --- SonarQube supports a generic import format for raising "external" issues in code. It is intended to allow you to import the issues from your favorite linter even if no plugin exists for it. @@ -11,7 +12,7 @@ External issues suffer from two important limitations: External issues and the rules that raise them must be managed in the configuration of your linter. -## Import +## Import The analysis parameter `sonar.externalIssuesReportPaths` accepts a comma-delimited list of paths to reports. Each report must contain, at top-level, an array of `Issue` objects named `issues`. @@ -39,6 +40,7 @@ Each report must contain, at top-level, an array of `Issue` objects named `issue * `startColumn` - integer, optional. 0-indexed * `endColumn` - integer, optional. 0-indexed +## Example Here is an example of the expected format: { "issues": [ diff --git a/server/sonar-docs/src/pages/analysis/generic_test.md b/server/sonar-docs/src/pages/analysis/generic-test.md index 47a5850076e..d7fa694f7d9 100644 --- a/server/sonar-docs/src/pages/analysis/generic_test.md +++ b/server/sonar-docs/src/pages/analysis/generic-test.md @@ -1,5 +1,6 @@ --- title: Generic Test Data +url: /analysis/generic-test/ --- Out of the box, SonarQube supports generic formats for test coverage and test execution import. If your coverage engines' native output formats aren't supported by your language plugins, simply covert them to these formats. diff --git a/server/sonar-docs/src/pages/analysis/index.md b/server/sonar-docs/src/pages/analysis/overview.md index e6603fe0a8c..1dc4166abed 100644 --- a/server/sonar-docs/src/pages/analysis/index.md +++ b/server/sonar-docs/src/pages/analysis/overview.md @@ -1,5 +1,6 @@ --- -title: Analyzing Source Code +title: Overview +url: /analysis/overview/ --- Once the SonarQube platform has been installed, you're ready to install an analyzer and begin creating projects. To do that, you must install and configure the scanner that is most appropriate for your needs. Do you build with: diff --git a/server/sonar-docs/src/pages/analysis/pull-request.md b/server/sonar-docs/src/pages/analysis/pull-request.md index 497b5ffb830..4e17d90c01d 100644 --- a/server/sonar-docs/src/pages/analysis/pull-request.md +++ b/server/sonar-docs/src/pages/analysis/pull-request.md @@ -1,5 +1,6 @@ --- title: Pull Request Analysis +url: /analysis/pull-request/ --- <!-- sonarqube --> @@ -24,7 +25,7 @@ PR analyses on SonarQube are deleted automatically after 30 days with no analysi <!-- sonarcloud --> ## Integrations for GitHub, Bitbucket Cloud and VSTS -If your repositories are hosted on GitHub, Bitbucket Cloud or VSTS, check out first the dedicated ["Integrations" pages](/integrations/index). Chances are that you do not need to read this page further since those integrations handle the configuration and analysis parameters for you. +If your repositories are hosted on GitHub, Bitbucket Cloud or VSTS, check out first the dedicated Integrations for: [BitBucketCloud](/integrations/bitbucketcloud/), [GitHub](/integrations/github/), and [VSTS](/integrations/vsts/). Chances are that you do not need to read this page further since those integrations handle the configuration and analysis parameters for you. <!-- /sonarcloud --> ## Analysis Parameters diff --git a/server/sonar-docs/src/pages/analysis/scm_integration.md b/server/sonar-docs/src/pages/analysis/scm-integration.md index 8771b78b2f1..78a498f9c81 100644 --- a/server/sonar-docs/src/pages/analysis/scm_integration.md +++ b/server/sonar-docs/src/pages/analysis/scm-integration.md @@ -1,12 +1,13 @@ --- title: SCM Integration +url: /analysis/scm-integration/ --- Collecting SCM data during code analysis can unlock a number of SonarQube features: * Automatic Issue Assignment * code annotation (blame data) in the Code Viewer -* SCM-driven detection of new code (to help with [Fixing the Water Leak](/fixing-the-water-leak)). Without SCM data, SonarQube determines new code using analysis dates (to timestamp modification of lines). +* SCM-driven detection of new code (to help with [Fixing the Water Leak](/user-guide/fixing-the-water-leak/)). Without SCM data, SonarQube determines new code using analysis dates (to timestamp modification of lines). ### Turning it on/off SCM integration requires support for your individual SCM provider. Git and SVN are supported by default. <!-- sonarqube -->For other SCM providers, see the Marketplace.<!-- /sonarqube --> |