diff options
| author | Stas Vilchik <stas.vilchik@sonarsource.com> | 2018-05-25 09:37:15 +0200 |
|---|---|---|
| committer | SonarTech <sonartech@sonarsource.com> | 2018-05-25 20:20:48 +0200 |
| commit | e8b90e724c5f8d4eac7607f8e40db222eb7555e9 (patch) | |
| tree | 743dd3128222c4ac0c9bad1cdfabdbed334f0ab2 /server/sonar-docs/src/pages/branches | |
| parent | 7031c2ae9d1a5caefd9c27cc302624e01403687b (diff) | |
| download | sonarqube-e8b90e724c5f8d4eac7607f8e40db222eb7555e9.tar.gz sonarqube-e8b90e724c5f8d4eac7607f8e40db222eb7555e9.zip | |
SONAR-10676 Add documentation for team onboarding on SonarCloud "Members" page (#251)
Diffstat (limited to 'server/sonar-docs/src/pages/branches')
4 files changed, 16 insertions, 0 deletions
diff --git a/server/sonar-docs/src/pages/branches/branches-faq.md b/server/sonar-docs/src/pages/branches/branches-faq.md index 63bc9cab628..58bacdcf22e 100644 --- a/server/sonar-docs/src/pages/branches/branches-faq.md +++ b/server/sonar-docs/src/pages/branches/branches-faq.md @@ -2,8 +2,12 @@ title: Frequently Asked Branches Questions --- +<!-- sonarqube --> + _Branch analysis is available as part of [Developer Edition](https://redirect.sonarsource.com/editions/developer.html)_ +<!-- /sonarqube --> + **Q:** How long are branches retained? **A:** Long-lived branches are retained until you delete them manually (**Administration > Branches**). Short-lived branches are deleted automatically after 30 days with no analysis. diff --git a/server/sonar-docs/src/pages/branches/index.md b/server/sonar-docs/src/pages/branches/index.md index 29f168cff2f..67de486046c 100644 --- a/server/sonar-docs/src/pages/branches/index.md +++ b/server/sonar-docs/src/pages/branches/index.md @@ -2,8 +2,12 @@ title: Branches --- +<!-- sonarqube --> + _Branch analysis is available as part of [Developer Edition](https://redirect.sonarsource.com/editions/developer.html)_ +<!-- /sonarqube --> + Branch analysis allows you to * analyze long-lived branches diff --git a/server/sonar-docs/src/pages/branches/long-lived-branches.md b/server/sonar-docs/src/pages/branches/long-lived-branches.md index 6498ae65888..010edc13b9c 100644 --- a/server/sonar-docs/src/pages/branches/long-lived-branches.md +++ b/server/sonar-docs/src/pages/branches/long-lived-branches.md @@ -2,8 +2,12 @@ title: Long-lived Branches --- +<!-- sonarqube --> + _Branch analysis is available as part of [Developer Edition](https://redirect.sonarsource.com/editions/developer.html)_ +<!-- /sonarqube --> + ## Status vs Quality Gate The same quality gate that is applied to the project as a whole is automatically applied to long-lived branches as well. This is not editable. diff --git a/server/sonar-docs/src/pages/branches/short-lived-branches.md b/server/sonar-docs/src/pages/branches/short-lived-branches.md index cdf79fc9c7c..25ebadbe4ea 100644 --- a/server/sonar-docs/src/pages/branches/short-lived-branches.md +++ b/server/sonar-docs/src/pages/branches/short-lived-branches.md @@ -2,8 +2,12 @@ title: Short-lived Branches --- +<!-- sonarqube --> + _Branch analysis is available as part of [Developer Edition](https://redirect.sonarsource.com/editions/developer.html)_ +<!-- /sonarqube --> + ## Status vs Quality Gate For short-lived branches, there is a kind of hard-coded quality gate focusing only on new issues. Its status is reflected by the green|red signal associated with each short-lived branch: |