From: G. Ann Campbell Date: Fri, 15 Mar 2019 19:48:50 +0000 (-0400) Subject: DOC add `sonar.buildString` to params list X-Git-Tag: 7.7~10 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=7a14ccabaa72ee4636e8071dc5ae5b48695f4fcd;p=sonarqube.git DOC add `sonar.buildString` to params list --- diff --git a/server/sonar-docs/src/pages/analysis/analysis-parameters.md b/server/sonar-docs/src/pages/analysis/analysis-parameters.md index 1631f79be35..24b79d23834 100644 --- a/server/sonar-docs/src/pages/analysis/analysis-parameters.md +++ b/server/sonar-docs/src/pages/analysis/analysis-parameters.md @@ -72,6 +72,7 @@ Key | Description | Default `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.| `sonar.analysis.[yourKey]`| This property stub allows you to insert custom key/value pairs into the analysis context, which will also be passed forward to [webhooks](/project-administration/webhooks/). | | +`sonar.buildString`| The string passed with this property will be stored with the analysis and available in the results of `api/project_analyses/search`, thus allowing you to later identify a specific analysis and obtain its ID for use with `api/project_analyses/set_baseline`. | | ### Duplications