# Changelog for Teamscale 7.3

Release Announcement

Check out the list of features and improvements for Teamscale 7.3.

REST XML Interface Removed (since Teamscale 7.0)

As of Teamscale 7.0, its REST XML interface (deprecated since Teamscale v6.0) has finally been removed. This affects only the legacy REST API; the new, versioned API is not affected. You have hence two options:

  • 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/….
  • 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. Note, however, that the legacy REST API will be deprecated and subsequently removed, too.
Changed Voting Behaviour for Bitbucket Server Integration (since Teamscale 6.7)

As of Teamscale 6.7, the Enable Voting option in the Bitbucket Server connector will only add the findings badge to the pull request description. Please enable the Enable pull request review option, if you want Teamscale to also review pull requests.

Changed Permissions when Using Docker Image (since Teamscale 6.3)

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.

Java 11 Required (since Teamscale 6.2)

As of Teamscale 6.2, running the Teamscale server requires a Java Runtime Environment, Version 11 or later.

Changed Resolving of Configuration Files (since Teamscale 6.0)
  • 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.
Re-Analysis when Upgrading
  • When updating from 7.3.x, drop-in.
  • When updating from 7.2.x or earlier, a full re-analysis via backup is required.

# Version 7.3.2 latest

Download Teamscale v7.3.2 (ZIP)
21st September, 2021

# Fixes

  • SonarQube Quality Profile import for Java was aborted due to an unsupported rule
  • Import of SonarQube Quality Profile for Javascript failed
  • Execution Status view showed an error page when opened during project deletion
  • Teamscale sometimes failed to analyze merge requests when it could not attribute a commit to the merge request
  • Simulink: Some ports in Simscape Multibody (formerly "SimMechanics") models were not processed correctly
  • C++ parser failed for constructors starting with an uppercase and certain method parameters
  • Editing ABAP connectors always prompted for re-analysis, even if there were no changes
  • Spec Item custom fields for Polarion work items were not formatted using the client time zone
  • False positives for C# naming conventions in case of expression-bodied members
  • Pre-commit jobs were sometimes delayed by repository scanning

# Improvements

  • Clarified finding description for "If statement without braces" check

# Version 7.3.1

Download Teamscale v7.3.1 (ZIP)
14th September, 2021

# Fixes

  • False positives for "Unused variable or parameter" check in C++ in case of method output parameters
  • Identifier highlighting did not highlight connected macro definitions
  • False positives for "Types shall be explicitly specified" check in C++
  • False positives for "No write access to SAP standard tables" check in ABAP
  • AbapLint failed to run in case no git installation or internet connection was available
  • Add as metric button in the Tests page's filter view was not aligned with other input fields in Safari
  • Duplicate forks in external analysis uploads sometimes led to unprocessed external analysis data
  • Clone detection result was incomplete for Delphi code
  • Some Gerrit changes were not included during live analysis
  • False positives for "Declarations should be part of namespace" check in C++ in case of Extern "C" definitions
  • Some custom user-enumeration fields in Polarion were not resolved
  • MC/DC coverage information was ignored in case it was imported via Artifactory
  • TestGapSynchronizer was not executed in parallel for unrelated commits
  • Imported SonarQube quality profiles were not accessible by the importing user
  • NullPointerException in GerritAnalysisResultUploadTrigger when processing impacted specification items
  • Changing the selected project for all widgets in a dashboard did not correctly update the selected project in the project selector
  • A warning indicating long loading times was sometimes incorrectly displayed in the Issues page in the Test Gaps perspective

# Improvements

  • Faster loading and updating of Issues and Specification Items tables in the Metrics perspective

# Version 7.3.0

Download Teamscale v7.3.0 (ZIP)
7th September, 2021

# Major Features

  • New Azure DevOps connector for requirements tracing
  • New interaction log shows Teamscale's voting and comment annotation interactions with code collaboration platforms
  • Merged merge requests are no longer removed from the Merge Requests page

# Web UI

  • Test pyramid widget
  • Ability to sort the impacted specification items in the merge request detail view
  • Columns in the issue and spec item table are now configurable
  • Ability to filter findings according to the guideline they belong to (e.g. AUTOSAR C++14)

# Analysis

  • The newly introduced predicate extendsType can now be used in comment completeness analysis

# New Checks

  • "Repeated subcondition" check (C/C++, C#, Java, JavaScript/TypeScript & Python)