# Changelog for Teamscale 6.5
Check out the Release Newsletter for Teamscale 6.5.
Changed permissions when running Teamscale in Docker
- As of Teamscale 6.3, Teamscale is no longer executed as the root user in the Docker container, but as user
teamscale(UID=1000). 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.
user: technical-user, which refers to a user whose permissions should be mapped to
Versions older than 4.0.0 are no longer supported
- As of Teamscale 6.3, importing data from versions earlier than 4.0.0 is no longer supported
Changed System Requirements
- As of Teamscale 6.2, running the Teamscale server requires a Java Runtime Environment, Version 11 or later.
Deprecated REST XML Interface
- As of Teamscale 6.0, Teamscale's REST XML interface has been deprecated. Accordingly, any existing scripts should be migrated to the new public API.
Changed loading of configuration files and locating relative paths
- As of Teamscale 6.0, all configuration files are loaded using the same logic. In particular configuration files in the process working directory take precedence over ones in the Teamscale installation.
- Relative paths specified in configuration files will always be resolved to the working directory. The working directory usually equals the installation directory unless explicitly changed.
- Custom check JAR files can be deployed in a directory relative to the working directory and installation directory.
- Searching for a Teamscale configuration file
teamscale-config.propertiesin the installation root directory. Use the file
teamscale.propertiesin one of the config directories.
- Searching for a license in the installation root directory or a directory specified by the Java system property
teamscale.license.pathis no longer supported. Use the environment variable
TEAMSCALE_CONFIGto specify a separate configuration directory or pass the license using the
TS_LICENSEenvironment variable if you cannot place the license in one of the config directories.
- The administrative service to read and write configuration files via the Web API (
config-files) has been removed.
Update from Older Version
- When updating from 6.5.x, drop-in.
- When updating from 6.4.x or earlier, a full re-analysis via backup is required.
# Version 6.5.2 latest
19th January, 2021
- C header files were incorrectly resolved in case of overlapping header file names
- Architecture component mappings were sometimes saved in the wrong component
- Newly created architecture component mappings were sometimes not saved
- Entries for exclude component mappings in the architecture editor took some time to show up in some cases
- False positives for "No global
using" check when using type aliases in C++
- Invalid commit streams in the Activity perspective in case of virtual repositories with Artifactory
- Switching projects via the project chooser did not select the corresponding valid branch
- Dashboards created from the default dashboard template were not correctly scaled
- It is now possible to define the Java source level used by the integrated SonarLint runner
# Version 6.5.1
12th January, 2021
NullPointerExceptionwhile parsing some Simulink models
- It was not possible to add Test Gap Treemap slides in reports for projects with aliases
# Version 6.5.0
5th January, 2021
# Major Features
- Extraction of test cases from C++ test code developed using the GoogleTest framework
- Ability to add connectors to an existing project without reanalysis
- New Test Gap Treemap Slide
- Finding Detail Slide can now show introduction or removal diff
# Web UI
- New option to hide already resolved findings from issue badges and on the issue details page
- Architecture editor: Visualize dependency strength
- New dashboard widget showing the newest commit for a given project or branch
- Partition name is now added to default upload message
- Comment analysis now differentiates task tags (TODO) and problem tags (FIXME, HACK) using different severities
# New Checks
- "Require var keyword in case type defined on right side" check (C#)
- "Avoid C-style array declarations" check (Java)
# IDE Integrations
- The Pre-Commit Results window in IntelliJ contains a link to upload the project for pre-commit analysis for the first time
- PyLint checks are now grouped in more semantically rich categories and groups
- Extended backup export options to allow reduction of preserved external data
- Added support for forwarding Teamscale logs to Splunk
- Commit-message issue connector extracts assignee from commit meta-data
- Source code repository connectors can now be copied while editing a project
- Support for
tar.bz2archives in Artifactory connector