Agent has a Update Agent Java flag, but java is updated and parameters are set

Update Agent Java flag is visible on the agents (Linux, macOS and Windows), although Java 17 is now installed, JAVA_HOME and JRE_HOME environment variable are correctly set in agents and the TeamCity agent service are restarted. 

After upgrading to Java 17,. these are the steps: 

  1. Disable Agent
  2. Update environment variable
  3. Stop and start agent services
  4. Enable Agent

Upload id: 2025_04_01_zhqBkaP5kC2YRxQK6dSryJ (file: Screenshot 2025-04-01 at 12.23.58.png)

0
2 comments

Everything is now Java21 minimum, since the latest release.    The agents won't update Java themselves, so you either need to re-run the installer, or do what I did, open the Windows agent installer usind 7ZIP and extract the JRE and copy the contents to the JRE sub-folder on each build agent.

0

Currently, the TeamCity server and build agents can run on Java 17 and it is still supported. However, as the warning states, Java 17 will no longer be supported in future versions of TeamCity. The suggestion at this time is to either upgrade to Java 21 or make a plan to upgrade to Java 21 ahead of the next release of TeamCity.

TeamCity Server warning:

This TeamCity server is running under Java 17. This version of Java will no longer be supported in future versions of TeamCity. Please upgrade Java to version 21.

TeamCity Build Agent warning:

Agent is running under Java 17 which will no longer be supported in future versions of TeamCity. Please upgrade Java to version 21

 

0

Please sign in to leave a comment.