To configure automatic start of a TeamCity build agent, see the dedicated section. The TeamCity server will now start automatically when the machine starts. This instruction assumes that TeamCity is installed to /Library/TeamCity.Ĭreate the /Library/LaunchDaemons/ file with the following content:
TEAMCITY DARK MODE INSTALL
Install TeamCity and make sure it works if started from the command line with bin/teamcity-server.sh start. Starting up the TeamCity server on macOS is quite similar to starting Tomcat on macOS.
TEAMCITY DARK MODE UPDATE
Review differences between the default Tomcat conf directory and one from TeamCity, update Tomcat files with TeamCity-specific settings ( teamcity-* files, and portions of server.xml)ĭelete the default Tomcat webapps/ROOT directory and replace it with the one provided by TeamCity Unpack the Tomcat distribution to the TeamCity Home directory.Ĭopy TeamCity-specific files from the previously backed-up/moved directories to the TeamCity Home:įiles under bin which are not present in the Tomcat distribution When upgrading the version of Tomcat to be used by TeamCity, we suggest that you:ĭelete/move from the TeamCity Home directories that are also present in the Tomcat distribution. To use another version of the Tomcat web server instead of the bundled one, you need to perform the Tomcat upgrade/patch. You can use an alternative Tomcat version, but note that other combinations are not guaranteed to work correctly. The TeamCity Server distributions include a Tomcat version tested to work fine with the current version. It is recommended to set the -Xmx4g option for 64-bit JVM. To update to 64-bit Java, either use the bundled version of Java or: Make sure to specify at least twice as much memory as for 32-bit JVM. If you need to update 32-bit Java to 64-bit JVM, note that the memory usage is almost doubled when switching from 32- to 64-bit. TeamCity server is bundled with the 64-bit JVM but can run under both 32- and 64-bit versions. The variable should point to the home directory of the installed JRE or JVM (Java SDK) respectively. If you use a different Java version, specified via an environment variable ( TEAMCITY_JRE, JRE_HOME, or JAVA_HOME), make sure it is available for the process launching the TeamCity server (it is recommended to set a global OS environment variable). If you also run a TeamCity agent from the \buildAgent directory, install JDK (Java SDK) installation instead of JRE and copy the content of the JDK installation directory into \jre.
If your TeamCity installation has a bundled JRE (there is the \jre directory), update it by installing a newer JRE per installation instructions and copying the content of the resulting directory to replace the content of the existing \jre directory. The necessary steps to update the Java installation depend on the distribution used.
If both variables are declared, JRE will be used. If there is no \jre directory present, TeamCity looks for the JRE_HOME or JAVA_HOME environment variable pointing to the installation directory of JRE or JVM (Java SDK) respectively. To use a different JRE, specify its path via the TEAMCITY_JRE environment variable. TeamCity selects the Java version to run the server process as follows:īy default, if your TeamCity installation has a bundled JRE (the \jre directory exists), it will be used to run the TeamCity server process.
TEAMCITY DARK MODE .EXE
exe installer but needs to be installed separately when using other distributions. A compatible JRE version is bundled in the TeamCity. TeamCity Server requires a Java SE JRE installation to run.
0 kommentar(er)
