Changelog for Teamscale 6.6
Newer Release Available
Our current release is available here.
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.
Deprecated XML REST Interface (since Teamscale 6.0)
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 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.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.
Upgrades from pre-4.0.0 Versions no Longer Supported
As of Teamscale 6.3, importing data from versions earlier than 4.0.0 is no longer supported
Re-Analysis when Upgrading
- 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.12
Fixes
- Metrics perspective overview did not load in cases where the URL was exceedingly long
Version 6.6.11
Fixes
- The option to Preview Repository Files did not work for the ABAP connector
Version 6.6.10
Fixes
- Errors in the Artifactory connection caused problems with analysis granularity settings in rare cases
- Special characters in the titles of SCM-Manager pull requests were not rendered correctly
Version 6.6.9
Fixes
- Teamscale sometimes triggered very costly rollbacks in special cases
- Rollback analysis message was sometimes displayed in the Activity perspective without any relevant jobs queued
- Active users by project chart's y axis on the System Information page was not scaled correctly
Version 6.6.8
Fixes
- Some Analysis Profile options no longer showed explanatory tooltips
- Voting on SCM-Manager pull requests failed if the branch names contained slashes
- Teamscale REST API page did not list all available Media types for some requests
- Newlines in external upload commit messages were ignored.
- The Compare method view sometimes showed incorrect file versions for methods added after a selected baseline.
Version 6.6.7
Fixes
- Type-based architecture analysis was mistakenly offered for C/C++
NullPointerExceptionin "Calling contains on List" check in certain situations.ArrayIndexOutOfBoundsExceptioninFindingsTrackerfor large external finding upload- HTTP 414 (Request-URI Too Long) error when viewing coverage from a large number of partitions
- JavaScript Error Log entries failed to load
- The External Report Uploads page was empty after uploading coverage for a project
- Editor links were missing for architectures with only one component in the Test Gap perspective
- The shortened Method history view was empty when selected branch was incorrect
- Hidden names and flipped positions of Simulink blocks were not displayed correctly.
- The Projects table in the Projects perspective had no maximum width.
- Table headers in the System Overview slide were not rendered correctly when the report was saved as PDF
- Test-gap treemap tooltips sometimes remained on the page
- Python architecture dependencies were incomplete in case of omitted
__init__.pyfiles - FindBugs and SpotBugs finding descriptions were rendered incorrectly
- False positives for "Unused Variable or Parameter" check in C#
- False positives for "Value assigned to variable not read" check in C# due to new pattern-matching enhancements
- False positives for "Unused Variable or Parameter" check in C++ in the case of output parameters
- False positives for C++ naming convention check when using unnamed parameters
- False positives for "Variable was assigned to itself" check in Kotlin
Version 6.6.6
Fixes
- Incorrect description for comment aggregation feature of voting connectors
- Testwise coverage behaved unexpectedly when uniform path is followed by a
\n - The API reference page displayed the wrong Teamscale icon
- Default branch with branch transformation failed to load files in the Metrics perspective
- Annotating Bitbucket pull requests with comments failed in case of architecture findings
- The Event Log view permanently showed "Loading more entries" without showing entries at all
- The ABAP connector ignored coverage information and Code Inspector findings
- The Architecture Editor asked for confirmation twice when navigating away with unsaved changes
- Image badge from Jira voting support was incorrectly replaced by text representation
- Findings uploaded via Artifactory were not correctly updated at fork commits in some cases
Version 6.6.5
Fixes
- Eclipse plugin: Findings view was not correctly refreshed after switching projects
- Metric Trend Chart widget did not include the set start date if it was before the first commit
- Only my dashboards toggle did not work when All projects was selected in the Dashboards perspective
- False positives in dead store analysis for C# due to null-coalescing assignment operator
ExternalAnalysisResultsPersisterthrewIllegalStateExceptionin rare cases- User with Developer role was able to view the issue list, but could not interact with it
- ABAP Data Dictionary files were mistakenly considered in clone detection
- Scheduling of external analysis results failed in the context of skipped nodes and non-trivial branching structures
- Dashboards were not sorted in the dashboard selector
- Projects could not be edited without the Create Project permission
- External credentials could only be edited when the user had the Create External Credential permission
- The preprocessor directive "nullable" in C# could not be parsed correctly
- Treemap widgets did not consider include/exclude patterns
- Baseline selection did not correctly work in case there were multiple baselines with the same name
- In the Method History view the note about merged coverage was incorrectly shown at the merge origin instead of at the merge target commit
Version 6.6.4
Fixes
- Repeatedly hiding/showing policies in the architecture editor caused performance problems
- Validation of the advanced project configuration setting Parent project id was incorrect
- The table of projects in Projects view was misaligned and did not use the available space properly
- Unlinked Changes view contained a link to itself
- False positives in dead store analysis for C# due to contextual keyword
yield - Markdown was not rendered correctly for inactive check descriptions in the Analysis Profiles edit view
- C# parser failed to parse code using nullable array types
- Architecture editor properties view decreased in size when resizing window
- Action Open in External Editor was not shown in the Code view for ABAP
IndexOutOfBoundsExceptionin theMethodCallIndexSynchronizeroccurred during parsing of ABAP methodsClang-Tidyintegration did not resolve project-header includes correctly- Method length findings were shown as new after method lengths were reduced but above threshold
- External Metrics could not be saved or modified in the External Metrics View
- C++ class constants were marked as coverable
- Adding code snippets to tasks triggered a page reload
- Pretty print function in the Code view did not show all comments
- Services "servicedoc.html" and "indexdoc.html" were delivered with the wrong content type
Improvements
- "Declarations should be a part of a namespace" check had an insufficient rationale
Version 6.6.3
Fixes
- Teamscale sometimes skipped imported external analysis results due to errors
- Path chooser in the widget edit dialog showed unrelated directories while typing
- False positives for "Avoid ternary operator" check when using TypeScript nullish coalescing operator
(??) - External credentials could be overwritten by users without the required permissions
- Finding locations were cut off in the findings list such that the file name was not readable anymore
- False positives for "Each variable should be declared on a separate line" check for attributes with a C# tuple type
- Teamscale Jenkins plugin was uploading coverage files in individual sessions per file
NullPointerExceptionin the findings detail view when viewing a Simulink finding that is reported for an entire file (top-level)
Improvements
- Added Jacoco and JUnit upload support to the Teamscale Gradle plugin
Version 6.6.2
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
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
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