![]() Make sure to use a version compatible with your server. This can be done by executing the following SQL commands from the MySQL console:Ĭreate database collate utf8mb4_bin - or utf8_bin on MySQL 5.5.2 or earlierĭownload the MySQL JDBC driver. The MySQL user account that will be used by TeamCity must be granted all permissions on the TeamCity database. See also recommendations for MySQL server settings. Make sure that the time zone of the JVM running TeamCity and that of MySQL instance are the same using the my.cnf file or by configuring time zones at the OS level. Use utf8mb4 character set (or utf8 if MySQL version is 5.5.2 or earlier). ![]() The section below describes the required configuration on the database server and the TeamCity server. Otherwise, you might get the " Unsupported major.minor version" errors related to the database driver classes. jar files should be compiled for the Java version not later than the one used to run TeamCity. jar files (see driver-specific sections below) from it into the /lib/jdbc directory. You will need to download the Java JDBC driver and put the appropriate. Due to licensing terms, TeamCity does not bundle the driver. You may also need to download the JDBC driver for your database. The user account used by TeamCity should have permissions to create new, modify, and delete existing tables in its schema, in addition to usual read/write permissions on all tables. The schema is not changed when TeamCity is working normally. The database structure is created on the first start and actively modified during the upgrade to the new TeamCity version. Note that TeamCity assumes ownership over the database schema. General StepsĬonfigure the external database to be used by TeamCity (see the database-specific sections below).Ĭonfigure the connection to the database via the form on the first TeamCity server start or by configuring the database connection settings manually. You may also want to estimate the required database capacity. While we strive to make sure TeamCity functions equally well under all the supported databases, issues may surface in some of them under high TeamCity-generated load. Selecting External Database EngineĪs a general rule, you should use the database that suits your environment best and that you can better maintain/configure in your organization. Migrate to an external database the moment you start relying on the data stored on your TeamCity server. Please note that our support does not cover any performance or database data loss issues if you are using the internal database. The internal database may become extremely slow on large data sets (database storage files over 200 MB). An external database is usually more reliable and provides better performance: the internal database may crash and lose all your data (for example, on the "out of disk space" condition). However, we strongly recommend using an external database as a backend TeamCity database in a production environment. The internal database suits evaluation purposes only it works out of the box and requires no additional setup. ![]() On the first TeamCity run, using an internal HSQLDB database is suggested by default. If you have been evaluating TeamCity with the internal database and want to copy the data from it, read how to migrate to an external database. HSQL* means that the internal database is in use. It is also mentioned in teamcity-server.log on the server startup. ![]() The currently used database is shown on the Administration | Global Settings page. TeamCity stores build history, users, build results, and some runtime data in an SQL database.
0 Comments
Leave a Reply. |