diff options
| author | MikeBirnstiehl <michael.birnstiehl@sonarsource.com> | 2019-09-27 15:03:10 -0500 |
|---|---|---|
| committer | SonarTech <sonartech@sonarsource.com> | 2019-09-28 20:21:04 +0200 |
| commit | 213ac5101c72969e70fd1f781d63dd57e4e72793 (patch) | |
| tree | 337c7d4b39cb2fdaee7b1757c1b66e3aef0fcae7 /server/sonar-docs/src/pages/analysis | |
| parent | 2542ddd092f5910aed39895a1b3061148aa8e03f (diff) | |
| download | sonarqube-213ac5101c72969e70fd1f781d63dd57e4e72793.tar.gz sonarqube-213ac5101c72969e70fd1f781d63dd57e4e72793.zip | |
DOCS update default working directory
Diffstat (limited to 'server/sonar-docs/src/pages/analysis')
| -rw-r--r-- | server/sonar-docs/src/pages/analysis/analysis-parameters.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/server/sonar-docs/src/pages/analysis/analysis-parameters.md b/server/sonar-docs/src/pages/analysis/analysis-parameters.md index 03f1825b8a5..c555d5c73bf 100644 --- a/server/sonar-docs/src/pages/analysis/analysis-parameters.md +++ b/server/sonar-docs/src/pages/analysis/analysis-parameters.md @@ -68,7 +68,7 @@ Key | Description | Default `sonar.externalIssuesReportPaths` | Comma-delimited list of paths to Generic Issue reports. | `sonar.projectDate` | Assign a date to the analysis. This parameter is only useful when you need to retroactively create the history of a not-analyzed-before project. The format is `yyyy-MM-dd`, for example: 2010-12-01. Since you cannot perform an analysis dated prior to the most recent one in the database, you must analyze recreate your project history in chronological order, oldest first.  Note: You may need to adjust your housekeeping settings if you wish to create a long-running history. | Current date `sonar.projectBaseDir` | Use this property when you need analysis to take place in a directory other than the one from which it was launched. E.G. analysis begins from `jenkins/jobs/myjob/workspace` but the files to be analyzed are in `ftpdrop/cobol/project1`. The path may be relative or absolute. Specify not the the source directory, but some parent of the source directory. The value specified here becomes the new "analysis directory", and other paths are then specified as though the analysis were starting from the specified value of `sonar.projectBaseDir`. Note that the analysis process will need write permissions in this directory; it is where the `sonar.working.directory` will be created. | -`sonar.working.directory` | Set the working directory for an analysis triggered with the SonarScanner or the SonarScanner for Ant (versions greater than 2.0). This property is not compatible with the SonarScanner for MSBuild. Path must be relative, and unique for each project.  Beware: the specified folder is deleted before each analysis. | `.sonar` +`sonar.working.directory` | Set the working directory for an analysis triggered with the SonarScanner or the SonarScanner for Ant (versions greater than 2.0). This property is not compatible with the SonarScanner for MSBuild. Path must be relative, and unique for each project.  Beware: the specified folder is deleted before each analysis. | `.scannerwork` `sonar.scm.provider` | This property can be used to explicitly tell {instance} which SCM plugin should be used to grab SCM data on the project (in case auto-detection does not work). The value of this property is always lowercase and depends on the plugin (ex. "tfvc" for the TFVC plugin). Check the documentation page of each plugin for more. | `sonar.scm.forceReloadAll` | By default, blame information is only retrieved for changed files. Set this property to `true` to load blame information for all files. This can be useful is you feel that some SCM data is outdated but {instance} does not get the latest information from the SCM engine. | `sonar.scm.exclusions.disabled`| For supported engines, files ignored by the SCM, i.e. files listed in `.gitignore`, will automatically be ignored by analysis too. Set this property to `true` to disable that feature.| |