From 7c31fe04f91c65bb44bb6593f4568ff92b05d3b8 Mon Sep 17 00:00:00 2001 From: Tobias Trabelsi <64127335+tobias-trabelsi-sonarsource@users.noreply.github.com> Date: Tue, 10 Nov 2020 15:29:09 +0100 Subject: [PATCH] [DOCS] document azdo agent bug Co-authored-by: MikeBirnstiehl --- .../src/pages/analysis/scan/sonarscanner-for-azure-devops.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-azure-devops.md b/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-azure-devops.md index cf5d0b55a2c..80bffe8caf3 100644 --- a/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-azure-devops.md +++ b/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-azure-devops.md @@ -174,3 +174,8 @@ _Note : The number of comments posted in a PR is limited to 50. If this limit ha We believe that breaking a CI build is not the right approach. Instead, we are providing pull request decoration (to make sure that issues aren't introduced at merge time) and we'll soon add a way to check the quality gate as part of a Release process. + +**Missing Build Agent Capability** + +If you add a Windows Build Agent and install a non-oracle Java version on it, the agent will fail to detect a needed capability for the SonarQube Azure DevOps plugin. If you are sure that the `java` executable is available in the `PATH` environment variable, you can add the missing capability manually by going to **your build agent > capabilities > user capabilities > add capability**. Here, you can add the key, value pair java, and null which should allow the SonarQube plugin to be scheduled on that build agent. +This Bug has been reported to the Microsoft Team with [azure-pipelines-agent#2046](https://github.com/microsoft/azure-pipelines-agent/issues/2046) but is currently not followed up uppon. -- 2.39.5