#Standalone openjdk 16 how to#
#Standalone openjdk 16 install#
#Standalone openjdk 16 windows 10#

NET Framework 4.6.1 or later installed on the build agent Supported languages are C# up to version 4.0 and VB.NET version 8.0 - 10.0 NET Framework or Mono installed on the build agentĪ corresponding version of Microsoft Visual Studio installed on the build agentĭuplicates Finder for C# and VB.NET code based on ReSharper Command Line Tools NET 6.0 or later installed on the build agent, or can be run inside a Docker container with. The recent versions of the following browsers have been specifically tested and reported to work correctly: The TeamCity web interface is mostly W3C-compliant, so any modern browser should work well with TeamCity. If you are using a different architecture that is not explicitly mentioned above, you may expect the TeamCity Agent to run on it, provided that your operating system is supported and a suitable Java Virtual Machine (JVM) option exists. TeamCity Agent is tested under the following operating systems: Builds can utilize other versions installed on agent machines (for example, JDK 19). Note that Java versions specified in this section are requirements to run the agent itself. The TeamCity agent Windows installer and agent Docker images come bundled with Amazon Corretto 64-bit Java 17.įor Apple ARM systems (for example, Apple M1 or M2), consider using a different version of Java 17, like Azul OpenJDK.

We recommend using the latest available version of JDK. Supported Java versions: OpenJDK and Oracle Java 8-17.

#Standalone openjdk 16 how to#

See notes on how to configure Java on agents. It requires a Java SE JRE installation to run. TeamCity Agent is a standalone Java application. If you are using a different architecture that is not explicitly mentioned above, you may expect the TeamCity server to support it, provided that your operating system is supported and a suitable Java Virtual Machine (JVM) option exists. The verified and thoroughly tested architectures include: Regarding architectural compatibility, TeamCity is not limited to any specific list. Reportedly works without known issues on:

#Standalone openjdk 16 windows 10#

Windows 10 and 11 under the Tomcat 8.5+ web application server Server Core installation of Windows Server 2016 Linux (Ubuntu, Debian, RedHat, SUSE, and others) TeamCity Server is tested under the following operating systems: If you find any compatibility issues with any of the operating systems, let us know. Generally, all the recent versions of Windows, Linux, and macOS are supported. See considerations on choosing the server platform. The core features of TeamCity Server are platform-independent. If you use a non-bundled version of Java 8, we highly recommend that you migrate your server to Java 11 or 17. Java 8 support will be discontinued in one of the future TeamCity Server versions. The TeamCity server Windows installer and server Docker images come bundled with Amazon Corretto 64-bit Java 17.įor Apple ARM systems (for example, Apple M1 or M2), consider using a different version of Java, like Azul OpenJDK. Supported Java versions: OpenJDK and Oracle Java 8 (8u16 or later), 11, and 17 (32 or 64 bit).

#Standalone openjdk 16 install#

See notes on how to install Java on a TeamCity server. TeamCity Server is a web application that runs within a capable J2EE servlet container. For hardware-related notes, see this section. This page covers software-related environments TeamCity works with.