Searching for a license in the installation root directory, or a directory specified by the Java system property is no longer supported.Use the file teamscale.properties in one of the config directories. Searching for a Teamscale configuration file teamscale-config.properties in the installation root directory.Custom check JAR files can be deployed in a directory relative to the working directory and installation directory.The working directory usually equals the installation directory unless explicitly changed. Relative paths specified in configuration files will always be resolved to the working directory.In particular configuration files in the process working directory take precedence over ones in the Teamscale installation. As of Teamscale 6.0, all configuration files are loaded using the same logic.Changed Resolving of Configuration Files (since Teamscale 6.0) Java 11 Required (since Teamscale 6.2)Īs of Teamscale 6.2, running the Teamscale server requires a Java Runtime Environment, Version 11 or later. user: technical-user, which refers to a user whose permissions should be mapped to teamscale. Please make sure to either allow this user to access the mounted directories and files or add a user mapping to your docker-compose file, e.g. Changed Permissions when Using Docker Image (since Teamscale 6.3)Īs of Teamscale 6.3, Teamscale is no longer executed as the root user in the Docker container, but as user teamscale (UID=1000). Please enable the Enable pull request review option, if you want Teamscale to also review pull requests. Note, however, that the legacy REST API will be deprecated and subsequently removed, too.Ĭhanged Voting Behaviour for Bitbucket Server Integration (since Teamscale 6.7)Īs of Teamscale 6.7, the Enable Voting option in the Bitbucket Server connector will only add the findings badge to the pull request description. A temporary solution is to keep using the legacy REST API but always send an Accept: application/json request header and accept JSON rather than XML responses.The preferred long-term solution is to migrate to the new, versioned REST API, i.e., to use REST endpoints like …/api/v7.0.0/….This affects only the legacy REST API the new, versioned API is not affected. REST XML Interface Removed (since Teamscale 7.0)Īs of Teamscale 7.0, its REST XML interface (deprecated since Teamscale v6.0) has finally been removed. Check out the list of features and improvements for Teamscale 7.0.

Rubymine 7.0.4