# Changelog for Teamscale 8.5

Java 17 Required (since Teamscale 7.7)

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

Changed startup on non-Docker Linux installations (since Teamscale 7.7)

As of Teamscale 7.7, Teamscale is no longer executed using nohup on non-Docker Linux installations. This requires manual intervention:

  • If you are using systemd to manage Teamscale as service, you have to change the startup type from Type=forking to Type=simple in the Teamscale systemd unit. Remember to reinstall the service.
  • For custom linux setups that depend on nohup, start Teamscale like: nohup ./teamscale.sh &.

In general, we strongly recommend running Teamscale on Linux with Docker.

Changed Teamscale systemd service type (since Teamscale 7.7)

As of Teamscale 7.7, the Teamscale systemd service type must be updated to type=simple, instead of the previous type=forking

Improved administration experience (since Teamscale 7.7)

Teamscale 7.7 features several changes that improve the default administration experience.

  • Breaking: Teamscale is no longer executed using nohup on non-Docker Linux installations. If nohup is required for your setup, start Teamscale like: nohup ./teamscale.sh & However, we strongly recommend running Teamscale on Linux with Docker or as Service.
  • The default location of storing backups is a folder named backup relative to the process working directory. Existing instances are not affected and the location previously configured will be set upon backup import.
  • The default location of cloning remote Git (or SAP) repositories is a folder named repo relative to the process working directory. Existing instances are not affected and the location previously configured will be set upon backup import. The option has been moved to Admin / Global Settings / Git.
  • The following JVM arguments are now always specified and can be removed from JVM_EXTRA_ARGS in jvm.properties: -Djco.session_timeout=60 -XX:-OmitStackTraceInFastThrow -Dsvnkit.http.methods=Basic,Digest,Negotiate,NTLM
  • The Teamscale temporary directory is now configurable with the TEAMSCALE_TEMP environment variable. If you previously specified a custom temporary directory using -Djava.io.tmpdir=..., we recommend removing this JVM argument and using the environment variable instead. The directory may be relative to the process working directory and is created if it does not exist.
SAP Java Connector required for importing ABAPĀ® code (since Teamscale 7.7)

As of Teamscale 7.7, exporting ABAPĀ® code from SAP systems requires a manual installation of the SAP Java Connector (SAP JCo) 3.1 or later. For detailed information on the installation process, please refer to Installation of the SAP Java Connector (JCo).

Teamscale Integration for IntelliJ now requires the corresponding server to be at least Teamscale 8.2

If you cannot upgrade the server, please use version 8.3.x of the Teamscale Integration for IntelliJ.
Older versions are available from the Jetbrains Plugin Marketplace (opens new window)

Re-Analysis when Upgrading
  • When updating from 8.5.x, drop-in.
  • When updating from 8.4.x or earlier, a full re-analysis via backup is required.

# Version 8.5.0 latest

Bug Fixes
  • 8.5.0 contains all fixes from previous versions released on and before December 13th, 2022
  • For brevity, only new features are included in the changelog
Download Teamscale v8.5.0 (ZIP)
December 13th, 2022

# Major Features

  • TODO: Major Features here

# Web UI

  • TODO: Web UI Features here

# Security Improvements

  • TODO: Security Improvements here

# New Checks

  • TODO: New Checks here

# IDE Integrations

  • TODO: IDE Integrations here

# Administration

  • TODO: Admin features here