Upgrading from teamcity 10.0.3 to 2018 (java path issue)
I tried to upgrade teamcity to the latest version from 10.0.3. After uninstalling the previous version and the new one, I picked teamcity and build agent to run under a service account. When I first launched teamcity in localhost, the application was not available. The server logs suggested Java path was not set properly and it couldn't execute java commands. I had teamcity pointing to the built in JRE folder and also had JAVA_HOME variable set in the environment variables for the user. I tried pointing java_home and jre_home to the teamcity jre folder, the actual java path in C:/program files and everything else but I was not able to see the application in the browser. What M ai missing here? I do not have any logs because I had to restore the server to a snapshot I took before the upgrade. My current teamcity _10.0.3 is working fine without any environment variable set for user or system. The build agent property is pointing to C:/JRE which does not exist. Please give suggestions for my next attempt to upgrade teamcity.
Please sign in to leave a comment.
Hi,
is this issue happening on the server side or on the agent side?
If it's on the agents, there are some requirements depending on how you installing it: https://confluence.jetbrains.com/display/TCD18/Setting+up+and+Running+Additional+Build+Agents#SettingupandRunningAdditionalBuildAgents-ConfiguringJava
On the server, please note the possible issues with running the server as a service: https://confluence.jetbrains.com/display/TCD18/Installing+and+Configuring+the+TeamCity+Server#InstallingandConfiguringtheTeamCityServer-InstallingTeamCityviaWindowsinstallationpackage
Setting up Java for the server is performed as described here: https://confluence.jetbrains.com/display/TCD18/Installing+and+Configuring+the+TeamCity+Server#InstallingandConfiguringtheTeamCityServer-JavaInstallation
While it shouldn't be needed for basic scenarios, there are some possibilities for errors. The default version included is 32 bit, while any installation beyond test purposes or very small installations will very likely want to move into 64 bits and increase the amount of allowed memory.
If you try it again and face again the issues, please add the logs this time so we can find the root of the issue.
I have found the issue and upgraded teamcity. I had to add the path variable for findstr .