# Changelog for Teamscale 6.6


Check out the Release Newsletter for Teamscale 6.6.

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 teamscale.

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.properties in the installation root directory. Use the file teamscale.properties in 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.path is no longer supported. Use the environment variable TEAMSCALE_CONFIG to specify a separate configuration directory or pass the license using the TS_LICENSE environment 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.6.x, drop-in.
  • When updating from 6.5.x or earlier, a full re-analysis via backup is required.

# Version 6.6.2 latest

Download Teamscale v6.6.2 (ZIP)
23rd February, 2021

# Fixes

  • SAP Code Inspector findings did not have check groups from new quality model.
  • The Project selector input in the Navigate to Issue dialog sometimes showed project names twice
  • False positives for "Avoid comparisons with boolean literal" check for C# in case of nullable types
  • ABAP Taint Analysis reported assertion errors when an RFC-enabled function was called from program code
  • PHP Architecture Analysis missed dependencies for classes in default namespace
  • Visual Studio Plugin: Findings were unreadable when IDE used Blue or Blue (Extra Contrast) UI themes

# Version 6.6.1

Download Teamscale v6.6.1 (ZIP)
16th February, 2021

# Fixes

  • Clone detection missed C# clones that only differed in a var keyword
  • Navigating from the Compare view to another project specific subview selected the wrong project
  • Clone coverage metric was not correct when cross component clones were detected

# Version 6.6.0

Download Teamscale v6.6.0 (ZIP)
9th February, 2021

# Major Features

  • New ABAP (SAP) connector
  • Ability to mark Git branches as important
  • Cross-component clone detection
  • Repository connectivity status is now prominently indicated for each project

# Reports

  • New clone comparison option in Finding Detail slide

# Web UI

  • New Scatter Plot widget to visualize up to 4 file metrics

# Tools

  • Simulink Model Advisor: Imported findings now include recommended actions and block locations in referenced models

# Administration

  • New option to skip updating global data during backup import