diff options
| author | Duarte Meneses <duarte.meneses@sonarsource.com> | 2022-03-21 13:04:54 -0500 |
|---|---|---|
| committer | sonartech <sonartech@sonarsource.com> | 2022-03-23 20:02:45 +0000 |
| commit | 6a65e721a78da9cb82b5990100bb62b907311310 (patch) | |
| tree | a5300ed2f6701cdf127b8874bcae6f8d2e44ecd6 | |
| parent | a38eda46c2f174efe54e6a584f12895a3d3c7f3c (diff) | |
| download | sonarqube-6a65e721a78da9cb82b5990100bb62b907311310.tar.gz sonarqube-6a65e721a78da9cb82b5990100bb62b907311310.zip | |
SONAR-16164 Document new scanner parameter 'sonar.newCode.referenceBranch'
| -rw-r--r-- | server/sonar-docs/src/pages/analysis/analysis-parameters.md | 4 | ||||
| -rw-r--r-- | server/sonar-docs/src/pages/project-administration/new-code-period.md | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/server/sonar-docs/src/pages/analysis/analysis-parameters.md b/server/sonar-docs/src/pages/analysis/analysis-parameters.md index 0f713564c63..6accf76362e 100644 --- a/server/sonar-docs/src/pages/analysis/analysis-parameters.md +++ b/server/sonar-docs/src/pages/analysis/analysis-parameters.md @@ -77,7 +77,7 @@ Key | Description | Default `sonar.scm.revision`| Overrides the revision, for instance the Git sha1, displayed in analysis results. By default value is provided by the CI environment or guessed by the checked-out sources.| `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`. | | `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.newCode.referenceBranch`| Defines the new code period for this branch to use the given branch as a reference branch, overriding the server's setting. See [New Code Period](/project-administration/new-code-period/). ### Duplications Key | Description | Default @@ -106,4 +106,4 @@ Key | Description | Default Key | Description ---|----|--- -`sonar.links.scm_dev` **Deprecated since SQ 7.1** | Developer connection. | `<scm><developerConnection>` for Maven projects
\ No newline at end of file +`sonar.links.scm_dev` **Deprecated since SQ 7.1** | Developer connection. | `<scm><developerConnection>` for Maven projects diff --git a/server/sonar-docs/src/pages/project-administration/new-code-period.md b/server/sonar-docs/src/pages/project-administration/new-code-period.md index 904cfc918f3..387f32934db 100644 --- a/server/sonar-docs/src/pages/project-administration/new-code-period.md +++ b/server/sonar-docs/src/pages/project-administration/new-code-period.md @@ -35,7 +35,7 @@ You can define New Code as changes from a previous version, a specific analysis, - **Reference Branch** – Choose a specific branch to define your New Code. Any changes made from your reference branch are considered New Code. - Available at the project and branch level. + Available at the project and branch level. You can also specify a reference branch using a scanner parameter, overriding the server's definition. See the [Scanner Analysis Parameters](/analysis/analysis-parameters/). - **Number of days** – Specify a number of days for a floating New Code period. For example, setting **Number of Days** to 30 creates a floating New Code period beginning 30 days from the current date. Available at the global, project, and branch level. |