Team Services | TFS 2017 | TFS 2015 | Previous versions (XAML builds)
to build your Java code.
The build agent must have the following capability:
|Maven POM file||
Relative path from the repo root to the Maven POM .xml file.
|Options||Specify any Maven options you want to use.|
In most cases, set this to
|JUnit Test Results|
|Publish to Visual Studio Team Services/TFS||Select this option to publish JUnit Test results produced by the Maven build to Visual Studio Team Services/TFS.|
|Test Results Files||Test results files path. Wildcards can be used. For example,
|JDK Version||Will attempt to discover the path to the selected JDK version and set JAVA_HOME accordingly.|
|JDK Architecture||Optionally supply the architecture (x86, x64) of JDK.|
|Run SonarQube Analysis||Select if you want to run a SonarQube analysis. See The Maven build task now simplifies SonarQube analysis.|
|Run PMD Analysis||Select if you want to perform a PMD static analysis. A build result page for each .pom file is shown on the Artifacts tab of the completed build. See The Maven build task now supports PMD analysis out of the box.|
Do I need a build agent?
You need at least one agent to run your build. Get an agent.
I can't select a default agent queue and I can't queue my build. How do I fix this?