

Reporting Java code inspection results for a buildĭetecting Java code duplicates in a build's sourceĭetailed test reports for JUnit and TestNG frameworks on the flyīuilding and Testing Java with Maven in TeamCity (2021) Running a Maven, Gradle, or Ant build step inside a Docker container Operating Systems and DatabasesĪpache Maven, using special build triggers for MavenĪutodiscovery of Maven, Gradle, and Ant build steps in a source projectĪutodetection of Maven and Gradle installations on a build agent The tables below are updated in accordance with the newly introduced integrations and whenever we have extra guides to share. See also versions of platforms and environments currently supported in TeamCity. Remember that you can extend this scope by installing additional plugins or even writing your own ones.
#TEAMCITY NODE JS SOFTWARE#
This article gives an overview of third-party software and platforms supported in TeamCity out of the box. There are many places in the TeamCity UI where you can set up or adjust software integrations, depending on their context. Provide smart detection and handy UI controls on the TeamCity side, orĮxpose specialized REST API endpoints for easier scripting and integration on a third-party system's side. To ensure our users are able to integrate every component of their CI/CD pipeline with TeamCity, we either:

One of the key features of TeamCity is straightforward integration with modern software technologies and platforms.
