Changelog for Teamscale 6.5
Newer Release Available
Our current release is available here
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 toteamscale.
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 fileteamscale.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 variableTEAMSCALE_CONFIGto specify a separate configuration directory or pass the license using theTS_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.10
Fixes
CodeChangeIndexSynchronzierwas very slow when a lot files were moved- Issue trend CSV exports sometimes contained dates in the future
- Annotating Bitbucket pull requests with comments containing special characters failed
- Configuration of multiple projects annotating the merge requests of the same repository with line comments was possible
- Voting on GitHub pull requests failed if the number of check run annotations exceeded the maximum limit
- Dead connector detection sometimes created unnecessary rollbacks
- Worker log download did not contain hashes of analyzed commits
Version 6.5.9
Fixes
- Project with a GitLab connector could not be created, if there were any projects on the instance with invalid GitLab connector configurations
- Loading of issue-based Test Gaps view did not work when coverage was annotated from another project
- Preprocessor directives were not shown in the Code view
- Fetching impacted tests only for specific partitions was not possible
- Branch coverage reported missing cases in context of C++ macro expansion
- Include paths with mixed Windows/Unix path separators were not imported correctly from compilation databases for C/C++
Improvements
- Minimum change-creation dates for Gerrit connectors can be set to future dates
Version 6.5.8
Fixes
- New licenses could not be loaded
- Exporting project backup from projects list did not export Git repository infos
- Navigation from the Findings Churn widget to the Delta perspective did not work correctly
- Pre-commit results were extremely delayed when the instance was under heavy load
- Eclipse Plugin: Findings links to Teamscale were disabled
Version 6.5.7
Fixes
NullPointerExceptionin the Method history view caused by merged coverage- Clone findings were sometimes falsely shown as introduced or resolved in a commit that did not change related files
- Uploading external data via the External Reports Upload view required project-edit permission
Improvements
- Improved performance in the Impacted Tests page in the delta perspective
Version 6.5.6
Fixes
- Switching to deleted branches was often not possible if the overall number of branches was high
- Rare storage level exception in the
TestExecutionMerger - Comment analysis mistakenly required interface comment for unexported top-level function
- Architecture editor did not remember the zoom factor
- Visual Studio Plugin: Pre-Commit staging dialog was empty due to file-name casing
Version 6.5.5
Fixes
- False positives for "C# naming conventions" check when using tuple types
NullPointerExceptionin "Comments should not contain nested comments" check when encountering malformed comments- Files from merge commits were wrongly displayed in branch merge TGA delta in some cases
- Simulink findings in the Metrics perspective did not redirect to the Finding Details view
- Project could not be saved and no error was shown in certain connector error conditions
- Try it out button in API Reference page did not respect Teamscale instance base URL setting
- Duplicate projects are shown in the project selector when projects with an alias are deleted and then recreated
- Findings introduction and removal diff did not open at expected line
- C++ dependency extraction missed dependencies in the context of
using namespacedirectives - Eclipse plug-in: The Open in Web Browser action in the Findings view sometimes led to a non-existent finding
Improvements
- SVN connector has new expert option to ignore certain revisions
Version 6.5.4
Fixes
- Download of trend data as CSV caused a 404 error
- Failed validation in Metrics Table configuration dialog disabled all buttons
MonitoringDataUploadTriggercould get stuck if monitoring endpoint was temporarily not reachable- Findings in the Findings perspective were not loaded correctly when time travel was active
- False positives for "Arithmetic operation on text literal" check for ABAP
- Changes to baseline parameters for dashboard widgets were not persisted
- Issue Table widget showed issues which were not from the selected filter
- Git submodules with SSH access could not be fetched if their parent repository was accessed via HTTPS
- Non-admin users could not access the External Credentials page in any case
- Project chooser and Metrics perspective sometimes incorrectly displayed single file children as deep links
- State of the Fetch Pre-Commit Results toggle in Netbeans was incorrectly preserved across IDE restarts
- Microsoft C++ Properties were not parsed correctly
- Gerrit connector missed patchsets for changes originally created before the configured minimum change creation date
SonarLintRunnercaused errors in some cases if the Teamscale installation directory was not writable- False positives for C# naming convention check
- Adding line comments to Bitbucket's pull requests sometimes failed
- False positives for "String interpolation argument number" check caused by implicit throwable argument in Log4J and SFL4J logging messages
- Creating dashboard widgets sometimes selected the wrong project
Version 6.5.3
Fixes
- SVN repositories allowing access to subfolders but not the root folder could not be added to Teamscale and caused
ProjectConfigurationException - Backup import failed during migration of some dashboards with
ClassCastException - SAML authentication selected wrong key from metadata causing assertion validation errors
- Simulink signal name labels were not displayed
- False positives for "C++ naming conventions" check when using template specialization
- False positives for "Missing virtual destructor" check in C++ in case of destructors inside macros
- Minor wording inconsistencies in the Changed files page in the Delta perspective
- Redundant scrollbars were shown in treemap widgets
- File names in the Test Code tab in the Tests page were not clickable
- Architectures were listed in a random order in the Architecture perspective
- Static analysis tools were split into two groups in the analysis profiles
Version 6.5.2
Fixes
- 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
Improvements
- It is now possible to define the Java source level used by the integrated SonarLint runner
Version 6.5.1
Fixes
SimulinkModelBuilderencountered aNullPointerExceptionwhile parsing some Simulink models- It was not possible to add Test Gap Treemap slides in reports for projects with aliases
Version 6.5.0
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
Reports
- 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
Analysis
- 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
Administration
- 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.gzandtar.bz2archives in Artifactory connector