From: G. Ann Campbell Date: Thu, 31 Jan 2019 09:48:46 +0000 (+0100) Subject: SONAR-11631 document `sonar.codePeriodVersion` X-Git-Tag: 7.7~172 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=bc7e1d7ab9188e9892fc216ec13af622bab17e00;p=sonarqube.git SONAR-11631 document `sonar.codePeriodVersion` and expand slightly on `sonar.projectVersion` --- diff --git a/server/sonar-docs/src/pages/analysis/analysis-parameters.md b/server/sonar-docs/src/pages/analysis/analysis-parameters.md index f88bbbbe2b1..e1962b9fb18 100644 --- a/server/sonar-docs/src/pages/analysis/analysis-parameters.md +++ b/server/sonar-docs/src/pages/analysis/analysis-parameters.md @@ -38,7 +38,8 @@ Key | Description | Default Key | Description | Default ---|----|--- `sonar.projectName`|Name of the project that will be displayed on the web interface.|`` for Maven projects, otherwise project key. If there is already a name in the DB, it won't be overwritten -`sonar.projectVersion` | The project version. | `` for Maven projects, otherwise "not provided" +`sonar.projectVersion` | The project version. If the project's New Code Period setting is `previous_version`, changing this value resets the project's New Code Period | `` for Maven projects, otherwise "not provided" +`sonar.codePeriodVersion` | When present, this _optional_, additional parameter acts as the project version for the purposes of resetting the New Code Period (see above), allowing a full semantic version (i.e. ending with build number, and so changing with each analysis) to be passed in to `sonar.projectVersion` _without_ resetting the new code period. Under these circumstances, the semantic version is stored with the analysis and available via Web Services and in the UI. |   ### Authentication