aboutsummaryrefslogtreecommitdiffstats
path: root/server
diff options
context:
space:
mode:
authormichaelbirnstiehl <michael.birnstiehl@sonarsource.com>2020-12-09 15:08:16 -0600
committersonartech <sonartech@sonarsource.com>2020-12-13 20:06:50 +0000
commit7bef61b574f3e80fb04b6d426b8332b0e73ffadd (patch)
tree518f8a154a9dd43ad4dd1345333900138c511edd /server
parent5c55c92b791298f7f70fce4a180f760e094f9a0f (diff)
downloadsonarqube-7bef61b574f3e80fb04b6d426b8332b0e73ffadd.tar.gz
sonarqube-7bef61b574f3e80fb04b6d426b8332b0e73ffadd.zip
DOCS add note about automatic branch analysis only with Git
Diffstat (limited to 'server')
-rw-r--r--server/sonar-docs/src/pages/analysis/azuredevops-integration.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/server/sonar-docs/src/pages/analysis/azuredevops-integration.md b/server/sonar-docs/src/pages/analysis/azuredevops-integration.md
index 8b58cd3648f..624f161f507 100644
--- a/server/sonar-docs/src/pages/analysis/azuredevops-integration.md
+++ b/server/sonar-docs/src/pages/analysis/azuredevops-integration.md
@@ -42,6 +42,9 @@ For information on analyzing your projects with Azure Pipelines, see the followi
## Analyzing projects with Azure Pipelines
SonarScanners running in Azure Pipelines jobs can automatically detect branches or pull requests being built, so you don't need to specifically pass them as parameters to the scanner.
+[[info]]
+| Automatic branch detection is only available when using Git.
+
You can find a tutorial on setting up analysis with Azure Pipelines by selecting **Azure Pipelines** when asked how you want to analyze your repository:
![Analyzing repositories with Azure Pipelines](/images/AzurePipelinesAnalysis.png)