Release Notes 6.8.5
Release Notes 6.8.4
Release Notes 6.8.3
Release Notes 6.8.2
Release Notes 6.8.1
Release Notes 6.8.0
Release Notes 6.7.3
Release Notes 6.7.2
Release Notes 6.7.1
Release Notes 6.7.0
Release Notes 6.6.20
Release Notes 6.6.19
Release Notes 6.6.18
Release Notes 6.6.17
Release Notes 6.6.16
Release Notes 6.6.15
Release Notes 6.6.14
Release Notes 6.6.13
Release Notes 6.6.12
Release Notes 6.6.11
Release Notes 6.6.10
Release Notes 6.6.9
Release Notes 6.6.8
Release Notes 6.6.7
Release Notes 6.6.6
Release Notes 6.6.5
Release Notes 6.6.4
Release Notes 6.6.3
Release Notes 6.6.2
Release Notes 6.6.1
Release Notes 6.6.0
Release Notes 6.5.10
Release Notes 6.5.9
Release Notes 6.5.8
Release Notes 6.5.7
Release Notes 6.5.6
Release Notes 6.5.4
Release Notes 6.5.3
Release Notes 6.5.2
Release Notes 6.5.1
Release Notes 6.5.0
Release Notes 6.4.41
Release Notes 6.4.40
Release Notes 6.4.39
Release Notes 6.4.38
Release Notes 6.4.37
Release Notes 6.4.36
Release Notes 6.4.35
Release Notes 6.4.34
Release Notes 6.4.33
Release Notes 6.4.32
Release Notes 6.4.31
Release Notes 6.4.30
Release Notes 6.4.29
Release Notes 6.4.28
Release Notes 6.4.27
Release Notes 6.4.26
Release Notes 6.4.25
Release Notes 6.4.24
Release Notes 6.4.23
Release Notes 6.4.22
Release Notes 6.4.21
Release Notes 6.4.20
Release Notes 6.4.19
Release Notes 6.4.18
Release Notes 6.4.17
Release Notes 6.4.16
Release Notes 6.4.15
Release Notes 6.4.14
Release Notes 6.4.13
Release Notes 6.4.12
Release Notes 6.4.11
Release Notes 6.4.10
Release Notes 6.4.9
Release Notes 6.4.8
Release Notes 6.4.7
Release Notes 6.4.6
Release Notes 6.4.5
Release Notes 6.4.4
Release Notes 6.4.3
Release Notes 6.4.2
Release Notes 6.4.1
Release Notes 6.4.0
Release Notes 6.3.5
Release Notes 6.3.4
Release Notes 6.3.3
Release Notes 6.3.2
Release Notes 6.3.1
Release Notes 6.3.0
Release Notes 6.2.10
Release Notes 6.2.9
Release Notes 6.2.8
Release Notes 6.2.7
Release Notes 6.2.6
Release Notes 6.2.5
Release Notes 6.2.4
Release Notes 6.2.3
Release Notes 6.2.2
Release Notes 6.2.1
Release Notes 6.2.0
Release Notes 6.1.3
Release Notes 6.1.2
Release Notes 6.1.1
Release Notes 6.1.0
Release Notes 6.0.41
Release Notes 6.0.40
Release Notes 6.0.39
Release Notes 6.0.38
Release Notes 6.0.37
Release Notes 6.0.36
Release Notes 6.0.35
Release Notes 6.0.34
Release Notes 6.0.33
Release Notes 6.0.32
Release Notes 6.0.31
Release Notes 6.0.30
Release Notes 6.0.29
Release Notes 6.0.28
Release Notes 6.0.27
Release Notes 6.0.26
Release Notes 6.0.25
Release Notes 6.0.24
Release Notes 6.0.23
Release Notes 6.0.22
Release Notes 6.0.21
Release Notes 6.0.20
Release Notes 6.0.19
Release Notes 6.0.18
Release Notes 6.0.17
Release Notes 6.0.16
Release Notes 6.0.15
Release Notes 6.0.14
Release Notes 6.0.13
Release Notes 6.0.12
Release Notes 6.0.11
Release Notes 6.0.10
Release Notes 6.0.9
Release Notes 6.0.8
Release Notes 6.0.7
Release Notes 6.0.6
Release Notes 6.0.5
Release Notes 6.0.4
Release Notes 6.0.3
Release Notes 6.0.1 & 6.0.2
Release Notes 6.0
Release Notes 5.4
Release Notes 6.8.5
CodeScene version 6.8.5 includes the following:
- Bug fix: Bad delta results from links on projects with the local folder
If you are running the JAR directly, you can download it here.
Release Notes 6.8.4
CodeScene version 6.8.4 includes the following:
- Improvement: Optimised webhook performance
- Changed HTTP server threads from 4 to 8.
- Added environment variable CODESCENE_SERVER_THREADS to change the number of threads.
- Improved GitHub App Webhook processing speed when encountering payloads we don't handle.
- Feature: REST API components - Added missing Code Health insights.
- Feature: The Analysis Data, Commits view now include additional commit detail.
If you are running the JAR directly, you can download it here.
Release Notes 6.8.3
CodeScene version 6.8.3 includes the following:
- Bug fix: Setting a custom user ID will no longer cause errors in logs
- Bug fix: Code coverage data is now included in the analysis for local path projects
If you are running the JAR directly, you can download it here.
Release Notes 6.8.2
CodeScene version 6.8.2 includes the following:
- Bug fix: Changes to the code health rules are now applied on PRs, regardless if the PRs are against the repo containing the global code health rules
If you are running the JAR directly, you can download it here.
Release Notes 6.8.1
CodeScene version 6.8.1 includes the following:
- Bug fix: Prevent errors from crashing the PR integration page
- Improvement: LoC count on the projects page
If you are running the JAR directly, you can download it here.
Release Notes 6.8.0
CodeScene version 6.8.0 includes the following:
- Feature: Code Health: make the code duplication criteria configurable as part of Custom Code Health.
We’re unifying the way code duplication is reported. We made the thresholds configurable and also unified them across programming languages. So you might notice small discrepancies from previous code health scores. In previous versions, the Code Duplication had less impact on larger files, a behavior that we have now changed to be independent of file size.
Use the following custom thresholds to tailor how Code Duplication is reported:
-
- function_duplication_min_lines_of_code_for_check specifies the lower threshold for when to report duplicated code with respect to function length. Default value: 10 (LoC). The idea is that you don’t care about 1 or 2 line functions that happen to be similar – that would generate tons of false positives.
- function_duplication_min_similarity_percentage specifies the thresholds for when two – or more – functions are considered copies of each other. Default: 75 (%). Code is considered duplicated when its structural similarity exceeds this threshold.
- Feature: Added ability to filter the system map on tickets to visualize which areas of the code base were modified
The System Maps now include a filtering feature that enables visualization of modified areas in the codebase based on ticket data. Filtering can be done by selecting multiple tickets simultaneously.
This filtering feature empowers you to quickly focus on specific areas of the codebase tied to relevant issues, enabling targeted visualization and better analysis. It’s a simple and powerful tool to focus on specific issues and see how they impact the system.
To enable filtering at system maps, PM integration has to be enabled.
If you are running the JAR directly, you can download it here.
Release Notes 6.7.3
CodeScene version 6.7.3 includes the following:
- Improvement: Improve the efficiency of global hooks
If you are running the JAR directly, you can download it here.
Release Notes 6.7.2
CodeScene version 6.7.2 includes the following:
- Feature: Include
.tuning
XML files in analysis
If you are running the JAR directly, you can download it here.
Release Notes 6.7.1
CodeScene version 6.7.1 includes the following:
- Improvement: Software Portfolio minor UI improvements
- Improvement: System Maps minor UI improvements
If you are running the JAR directly, you can download it here.
Release Notes 6.7.0
CodeScene version 6.7.0 includes the following:
- Feature: Code Coverage tab at Software Portfolio
The Software Portfolio now gives a high-level overview of all your projects in terms of CodeScene's four factors and Code Coverage. It is designed to make it easy to see trends impacting your entire organization and to make high-level prioritization.
More information on how the average coverage calculation is done can be found here.
- Added exclusion filters on a project level for Code coverage
Projects will often have only partial code coverage data. This could be for several reasons:
-
- Multiple programming languages in a project: they do not have coverage data yet for one or more of the languages they use
- Multiple repositories: they are currently generating CC data on some repos, but not all
There might also be parts of a codebase that cannot or will not be tested.
All of these situations would lead to many files being marked as having 0% code coverage, in other words as false positives. This would result in an incorrect representation of the code coverage situation, both in terms of which files appear as red 0% files and for the averages that we calculate.
We now have a way for the user to tell CodeScene when the absence of CC data does not mean the absence of code coverage.
If you are running the JAR directly, you can download it here.
Release Notes 6.6.20
CodeScene version 6.6.20 includes the following:
- Feature: Introducing a global configuration for GitHub Apps (delta analysis)
If you are running the JAR directly, you can download it here.
Release Notes 6.6.19
CodeScene version 6.6.19 includes the following:
- Bug fix: Analyses using the SonarQube plugin now work properly again. (but note that plugins are deprecated)
Release Notes 6.6.18
CodeScene version 6.6.18 includes the following:
- Bug fix: Local repo path is used as regex when transforming paths in Code Coverage data
If you are running the JAR directly, you can download it here.
Release Notes 6.6.17
CodeScene version 6.6.17 includes the following:
- Bug fix: Fixed issue with couplings parsing that results in extremely slow system map initial load.
- Feature: For Rust code, CodeScene now supports custom rules specific to tests when embedded in a file with application code.
- Feature: Added an infinite scroll for the improved performance of the project page.
If you are running the JAR directly, you can download it here.
Release Notes 6.6.16
CodeScene version 6.6.16 includes the following:
- Bug fix: Updated Azure PM data is now combined correctly with a cached date. Previously historical transitions were sometimes lost
- Bug fix: Fixed display of team labels for "unmodified"
If you are running the JAR directly, you can download it here.
Release Notes 6.6.15
CodeScene version 6.6.15 includes the following:
- Improvement: Improved sorting of the files in the Detailed Delta Analysis page inside the tooltips popups that show a list of files: sort by largest negative impact first in this list; Remove files where there is zero impact to code health; By default sort the list by largest impact to least.
- Improvement: Azure repository: URL case insensitive match
- Feature: Indicate Code Coverage items on the system map that are mismatched, ie. “a discrepancy between the test commit and the analyzed commit.”
If you are running the JAR directly, you can download it here.
Release Notes 6.6.14
CodeScene version 6.6.14 includes the following:
- Bug fix: Fix missing paging of repositories when determining Azure repo external ID
- Feature: Add support for minimum level slider control for Code Coverage score in System Map
- Note: With this release, the code health for all files will be recalculated. This is because the cache format has changed, meaning the first analysis for each project will take longer than usual.
Release Notes 6.6.13
CodeScene version 6.6.13 includes the following:
- Bug fix: Fixed calculation of branch coverage.
- Improvement: Added a server-side setting for Jira PM data page size.
If you are running the JAR directly, you can download it here.
Release Notes 6.6.12
CodeScene version 6.6.12 includes the following:
- Feature: Data validation errors (e.g. the data is not for an ancestor commit…) are now also shown under Analysis Warnings in the analysis results
Release Notes 6.6.11
CodeScene version 6.6.11 includes the following:
- Improvement: Clicking on a project in the Software portfolio now opens a relevant page.
- Improvement: dnsjava dependency upgrade to fix CVE-2024-25638
- Feature: Added Code Coverage slider control at System Maps.
If you are running the JAR directly, you can download it here.
Release Notes 6.6.10
CodeScene version 6.6.10 includes the following:
- Improvement: Limited HTTP sessions to 7 days - this can be adjusted
- Bug fix: Absolute Windows file paths are not handled properly when uploading
Release Notes 6.6.9
CodeScene version 6.6.9 includes the following:
- Improvement: Improved and detailed view of projects that are not displayed in the graph because they lack data due to missing configurations.
- Feature: Added the ability to filter the Code Coverage System Maps on hotspots.
If you are running the JAR directly, you can download it here.
Release Notes 6.6.8
CodeScene version 6.6.8 includes the following:
- Bug fix: Handle uploading coverage data that contains BOM
If you are running the JAR directly, you can download it here.
Release Notes 6.6.7
CodeScene version 6.6.7 includes the following:
- Bug fix: Bitbucket Server runs 2 delta analyses when a closed PR is re-opened if a branch has been updated between close and re-open actions.
Release Notes 6.6.6
CodeScene version 6.6.6 includes the following:
- Bug fix: Bitbucket Server runs delta when the PR title is changed.
- Bug fix: Code Health details in the delta analysis view list files incorrectly.
- Bug fix: The file list in the Code Health details view is not scrollable.
If you are running the JAR directly, you can download it here.
Release Notes 6.6.5
CodeScene version 6.6.5 includes the following:
- Improvement: Minor UI improvements
If you are running the JAR directly, you can download it here.
Release Notes 6.6.4
CodeScene version 6.6.4 includes the following:
- Bug fix: Fixed cutting off the visualization above the bottom of the page at Team-Code Alignment Explorer.
- Bug fix: Fixed undefined values at Code Age Trends graph.
- Improvement: Gray out non-available ranges in the legend of code coverage at system maps.
- Feature: Custom default settings when creating new projects: New option to select a “template project”, which is a project that will define the settings that will be used when creating new projects.
If you are running the JAR directly, you can download it here.
Release Notes 6.6.3
CodeScene version 6.6.3 includes the following:
- Bug fix: Fixed generation of the Portfolio report for users using LDAP provider
Release Notes 6.6.2
CodeScene version 6.6.2 includes the following:
- Bug Fix: Projects now always get unique analysis results folders, even if started the same second and using the same result root.
- Bug fix: Fixed sorting of duration time at Project Usage Activity
Release Notes 6.6.1
CodeScene version 6.6.1 includes the following:
- Bug fix: Fresh install fails on MySQL
If you are running the JAR directly, you can download it here.
Release Notes 6.6.0
CodeScene version 6.6.0 includes the following:
- Feature: Code Coverage integration providing REST API endpoints for uploading coverage data
More details here.
If you are running the JAR directly, you can download it here.
Release Notes 6.5.10
CodeScene version 6.5.10 includes the following:
- Improvement: Previously, the y-axis scaling in this graph exaggerated even minor changes, making them appear overly dramatic. We’ve now improved the scaling by introducing vertical padding for smaller changes whereby the highest and lowest points are now closer to the center of the graph, providing a more accurate and balanced view.
If you are running the JAR directly, you can download it here.
Release Notes 6.5.9
CodeScene version 6.5.9 includes the following:
- Bug fix: Fixed accessibility of badges
- Improvement: Added aggregated "Defect Count" on folder level at System Maps
- Feature: Code Health scores in the Delta Analysis page
- Feature: Impact on Code Health score for affected files displayed in Pull Request
If you are running the JAR directly, you can download it here.
Release Notes 6.5.8
CodeScene version 6.5.8 includes the following:
- Bug fix: Fixed user-guiding overlay popups
- Bug fix: Fixed setup PR integration using REST-API
If you are running the JAR directly, you can download it here.
Release Notes 6.5.7
CodeScene version 6.5.7 includes the following:
- Bug fix: Fixed report URLs
- Minor UI fixes
If you are running the JAR directly, you can download it here.
Release Notes 6.5.6
CodeScene version 6.5.6 includes the following:
- Bug fix: Fixed incorrect rendering of Group names in the group name edit field
- Bug fix: Remove invalid report subscriptions from DB
- Bug fix: Suppress findings fail with the BitBucket server when the workspace name is capitalized
- Improvement: Updated base docker image to ubuntu 24.04 (latest LTS release)
- For the codescene docker image, changed the codescene user UID to 10999 (previously 999) and the codescene group GID to 10999 (previously 999).
Release Notes 6.5.4
CodeScene version 6.5.4 includes the following:
- Bug fix: Updating report schedule now works properly for H2 database again
- Bug fix: Fixed broken link for hotspots declining in Code Health at 'Active risks & improvement opportunities'
- Improvement: Support analyzing method implementations in Java interfaces
Release Notes 6.5.3
CodeScene version 6.5.3 includes the following:
- Bug fix: Fixed a bug in the migration of the H2 database
If you are running the JAR directly, you can download it here.
Release Notes 6.5.2
CodeScene version 6.5.2 includes the following:
- Improve error logging for unexpected startup failures
Release Notes 6.5.1
CodeScene version 6.5.1 includes the following:
- Bug fix: Fix work type label mismatch in work type trend modal
If you are running the JAR directly, you can download it here.
Release Notes 6.5.0
CodeScene version 6.5.0 includes the following:
- Improvement: Upgraded the H2 JDBC driver because of vulnerabilities from 1.4.193 to 2.2.224
- CVE-2022-23221
- CVE-2022-45868
- CVE-2021-42392
Release Notes 6.4.41
CodeScene version 6.4.41 includes the following:
- Feature: hidden /admin endpoint for advanced troubleshooting (thread dumps)
If you are running the JAR directly, you can download it here.
Release Notes 6.4.40
CodeScene version 6.4.40 includes the following:
- Improvement: Add a new special configuration variable REPO_UPDATE_SLEEP_SECONDS (default 0) that will make CodeScene sleep the given number of seconds after an update of each repository in a project. This can be useful if you are facing intermittent network problems when updating a larger number of repositories in quick succession. It is NOT recommended for standard use.
Release Notes 6.4.39
CodeScene version 6.4.39 includes the following:
- Improvement: Default ENABLED_TLS_PROTOCOLS the TLSv1.3 for mysql (5.7 or 8.0) and mariaDB
- Improvement: Added CODESCENE_DB_ENABLED_TLS_PROTOCOLS and CODESCENE_DB_SSL_MODE for mariaDB
- Improvement: Updated the docs /getting-started/installation.html#set-up-an-external-database
If you are running the JAR directly, you can download it here.
Release Notes 6.4.38
CodeScene version 6.4.38 includes the following:
- Improvement: Minor UI improvement for the Architectural Components Editor
Release Notes 6.4.37
CodeScene version 6.4.37 includes the following:
- Bug fix: Jira ticket ID extraction fails when a subtask issue type has a localized name.
- Bug fix: Handle that BitBucket can return 404 when fetching commits for a PR.
If you are running the JAR directly, you can download it here.
Release Notes 6.4.36
CodeScene version 6.4.36 includes the following:
- Feature: Support C# local functions in Code Health calculations.
Release Notes 6.4.35
CodeScene version 6.4.35 includes the following:
- Bug fix: Kotlin multi-line string parsing bug.
If you are running the JAR directly, you can download it here.
Release Notes 6.4.34
CodeScene version 6.4.34 includes the following:
- Bug fix: Changed A-E scoring for off-boarding risk to code health category in Bus Factor
- Improvement: Minor UI improvements for the empty PR statistics page
Release Notes 6.4.33
CodeScene version 6.4.33 includes the following:
- Bug fix: Fixed parsing of function arguments of an instantiated template type.
- Bug fix: Fixed issues with LDAP connection after upgrade.
- Improvement: C# language: support Attributes on method arguments.
If you are running the JAR directly, you can download it here.
Release Notes 6.4.32
CodeScene version 6.4.32 includes the following:
- Bug fix: The option to disable updating repositories now works again
If you are running the JAR directly, you can download it here.
Release Notes 6.4.31
CodeScene version 6.4.31 includes the following:
- Improvement: Security improvements
- Improvement: Improved Gerrit URL parsing
Release Notes 6.4.30
CodeScene version 6.4.30 includes the following:
- Improvement: Improved error handling
Release Notes 6.4.29
CodeScene version 6.4.29 includes the following:
- Improvement: Java: support records from JDK16
Release Notes 6.4.28
CodeScene version 6.4.28 includes the following:
- Bug fix: Access is now allowed on developer settings when permissions come only from the project.
Release Notes 6.4.27
CodeScene version 6.4.27 includes the following:
- Bug fix: Excluded authors aren't visible in the Author Statistics anymore.
- Bug fix: Increase the size of the PM config values column.
Release Notes 6.4.26
CodeScene version 6.4.26 includes the following:
- Bug fix: "Costs per Type of Work" are now shown at Virtual Code Review for the files that haven't been changed that often (non-hotspots)
- Bug fix: Delivery performance summary for multi-repo projects: Repos with no releases should not be included when averaging release properties, but when averaging the number of releases they should be included (as having 0 releases)
- Improvement: File-level complexity trends available for all files in Virtual code review
- Improvement: updating several dependencies to newer versions, including xerces and ldapsdk.
Release Notes 6.4.25
CodeScene version 6.4.25 includes the following:
- Improvement: Improved presentation of delta analysis comments
Release Notes 6.4.24
CodeScene version 6.4.24 includes the following:
- Bug fix: C# complexity calculation bug
Release Notes 6.4.23
CodeScene version 6.4.23 includes the following:
- Bug fix: Code Health directives are now parsed correctly in C++ classes
- Feature: Support BrighterScript Code Health
Release Notes 6.4.22
CodeScene version 6.4.22 includes the following:
- Bug Fix: Gerrit PR Integration will no longer comment on each push if there's nothing to say unless the option to Always Comment is enabled.
- Bug Fix: Gerrit PR Integration will comment on errors and skipped checks where appropriate.
- Bug Fix: Gerrit PR integration filtering on the source branch was broken, the pattern was tested on pull reference ID instead of branch name.
- Bug Fix: GitHub PR checks were erroneously done on HTTP server threads, blocking UI requests while being executed, it also limited resources used to 4 CPUs.
- Improvement: On a branch push, each project configured for GitHub PR checks would create a check run for each PR on a branch, which fired PRs * projects check run created events and each was handled by each configured project, causing PRs * projects * projects delta runs. This was changed so only a single check run and delta is done per PR (though check runs of every PR of the branch will show up in each PR in Github UI, that's how it works).
- Improvement: DELETE developer settings via REST-API.
Release Notes 6.4.21
CodeScene version 6.4.21 includes the following:
- Bug fix: Fixed over logging during errors
Release Notes 6.4.20
CodeScene version 6.4.20 includes the following:
- Feature: Detect BrighterScript files
- Feature: Have CodeScene recognize D-language files
- Feature: Use markdown in Gerrit when available
- Feature: Update webhooks when adding/removing repos to the project
Release Notes 6.4.19
CodeScene version 6.4.19 includes the following:
- Bug fix: It is now possible to disable secure mail transport after one of the two options is selected
Release Notes 6.4.18
CodeScene version 6.4.18 includes the following:
- Bug fix: Fix Azure PR integration throwing error when posting file comments
- Bug fix: Azure PR Integration shouldn't recreate file comments that are the same after another push
Release Notes 6.4.17
CodeScene version 6.4.17 includes the following:
- Bug fix: Fix importing teams using REST-API
Release Notes 6.4.16
CodeScene version 6.4.16 includes the following:
- Improvement: The project ID added to the log messages for easier identification of what repository is not configured.
Release Notes 6.4.15
CodeScene version 6.4.15 includes the following:
- Improvement: Fetch commits to analyze with retry when running delta analysis
- Feature: Add user-managed webhooks for Gerrit
Release Notes 6.4.14
CodeScene version 6.4.14 includes the following:
- Bug fix: Added support for C# Property Constructor syntax.
- Improvement: Added REST API documentation with examples for replacing a custom report.
Release Notes 6.4.13
CodeScene version 6.4.13 includes the following:
- Bug fix: Azure work-item transition dates are now correctly fetched from Azure.
Release Notes 6.4.12
CodeScene version 6.4.12 includes the following:
- Improvement: Removed UI dependencies on the Bootstrap.js library
- Improvement: Various minor UI improvements
Release Notes 6.4.11
CodeScene version 6.4.11 includes the following:
- Bug fix: Admin user can now delete Teams/Developers configuration which isn't linked to any project.
- Feature: Allow updating developer settings for a project via REST API.
Release Notes 6.4.10
CodeScene version 6.4.10 includes the following:
- Bug fix: Fix the order of args in storage-precondition.
Release Notes 6.4.9
CodeScene version 6.4.9 includes the following:
- Bug fix: Spaces are now allowed in the passwords.
- Improvement: Optimize the Ruby parsing.
Release Notes 6.4.8
CodeScene version 6.4.8 includes the following:
- Improvement: Added a list of files currently being scored to System Configuration
Release Notes 6.4.7
CodeScene version 6.4.7 includes the following:
- Bug fix: Fix StackOverFlowError impacting the analysis.
Release Notes 6.4.6
CodeScene version 6.4.6 includes the following:
- Bug fix: Fix for a C# cyclomatic complexity bug - nullable reference suffix being penalized as cyclomatic complexity
Release Notes 6.4.5
CodeScene version 6.4.5 includes the following:
- Feature: REST-API: New endpoint for Long-Lived Branch.
Release Notes 6.4.4
CodeScene version 6.4.4 includes the following:
- Bug fix: Azure PM configuration now uses state names instead of column names.
Release Notes 6.4.3
CodeScene version 6.4.3 includes the following:
- Bug fix: YouTrack issue ID mapping handles casing correctly.
- Feature: The project dashboard can now be filtered by goals.
- Feature: The Hotspot Code Health view can now be filtered by the team.
Release Notes 6.4.2
CodeScene version 6.4.2 includes the following:
- Bug fix: Permissions are now correctly required for the kpi-trend/code-health endpoint
- Bug fix: The endpoint for listing projects now works for users with roles only in single projects
- Feature: Introduced a simple password policy
- Feature: Remove the SSH key on a group
- Feature: REST-API endpoint to return JSON application version information
Release Notes 6.4.1
CodeScene version 6.4.1 includes the following:
- Bug fix: Support "Code Duplication" as a directive.
- Bug fix: Incorrect pop-up when adding an invalid repository URL.
Release Notes 6.4.0
CodeScene version 6.4.0 includes the following:
- Improvement: View code smells that are getting worse, but not enough to lower your Code Health.
- Feature: At system maps when a file with change coupling is selected, a third tab will appear in the sidebar, providing detailed information about the different change couplings.
- Feature: Clicking at a node at a system map will “lock” the change coupling visualization, enabling better-continued interaction with the system map.
- Feature: Disable function-level code smells via directives provided as source code comments.
- Feature: CodeScene now supports additional PM integration providers: GitLab issues and YouTrack.
Release Notes 6.3.5
CodeScene version 6.3.5 includes the following:
- Bug fix: The YouTrack PM Integration now fetches transition data even if the state field is not named "State".
- Bug fix: File-level hotspots now display the correct list of files.
Release Notes 6.3.4
CodeScene version 6.3.4 includes the following:
- Feature: Add filter capability to REST API
Release Notes 6.3.3
CodeScene version 6.3.3 includes the following:
- Bug fix: fix Bitbucket Server PR Integration error when CodeScene's older comments have replies (error due to failure to delete). Instead, such comments will now be tagged as outdated.
Release Notes 6.3.2
CodeScene version 6.3.2 includes the following:
- Improvement: Show unsupported language warning at Virtual Code Review
Release Notes 6.3.1
CodeScene version 6.3.1 includes the following:
- Bug fix: Filter teamless authors in developer configuration now takes team analysis interval into account.
- Bug fix: Sorting by goals in HotSpot Code Health views now works properly.
- Improvement: Smoother System Map navigation and rendering, file names shown on hover.
- Feature: Projects with local pre-cloned repositories are now supported when using the docker image.
Release Notes 6.3.0
CodeScene version 6.3.0 includes the following:
- Improvement: It is now possible to add empty repositories and analyze them (though the results will be empty until commits are made)
- Feature: Updated the PDF reports to better reflect the Four Factors. Existing report subscriptions are migrated to the new reports.
- Feature: In the system map legends, hovering over an item creates an effect that highlights the matching files.
- Feature: The developer's REST API endpoint now includes all emails used by a developer.
Release Notes 6.2.10
CodeScene version 6.2.10 includes the following:
- Bug fix: Multiple fixes of Bitbucket and BitBucket Server comments that CodeScene generates.
- Bug fix: Added support for newer (BB Server 7+) PR events, which adds support for PR check triggering when the PR target branch changes and fixes a bug with stale PR head commit in analyses.
- Feature: Handle the option for using labels as work types for Jira Server.
Release Notes 6.2.9
CodeScene version 6.2.9 includes the following:
- Bug fix: The link for functions doesn't lead to a broken page anymore.
Release Notes 6.2.8
CodeScene version 6.2.8 includes the following:
- Bug fix: Allow target ref switching to trigger GitLab requests.
- Bug fix: The Golang parser now handles the empty interface construct.
- REST-API endpoint: /projects/activity
Release Notes 6.2.7
CodeScene version 6.2.7 includes the following:
- Bug fix: Bitbucket Server URL parsing
- Feature: At the system, maps glow background to identify coupled nodes without hovering
Release Notes 6.2.6
CodeScene version 6.2.6 includes the following:
- Bug fix: Global hook handling should trigger all projects regardless of errors.
Release Notes 6.2.5
CodeScene version 6.2.5 includes the following:
- Feature: Add a “Configure Ex-Developers” button in Team Dynamics
- Feature: Add a "Teamless authors" filter at developers page
Release Notes 6.2.4
CodeScene version 6.2.4 includes the following:
- Bug fix: Bitbucket Server Webhook will not fail now if using BitBucket version 5.9.0
Release Notes 6.2.3
CodeScene version 6.2.3 includes the following:
- Activating form for On-prem Start Free Trial flow for data gathering that will be used for analytics and later to make improvements based on analytics.
Release Notes 6.2.2
CodeScene version 6.2.2 includes the following:
- Improvement: Make it possible to turn off some expensive analysis steps, for extremely large code bases
- Bug fix: Add timespan indications to file details on system maps
Release Notes 6.2.1
CodeScene version 6.2.1 includes the following:
- Bug fix: Incorrect filtering of the worst performer at system maps
- Improvements: Minor UI improvements on the new PR statistics page and new system maps
Release Notes 6.2.0
CodeScene version 6.2.0 includes the following:
- A new system map with many improvements, including
- Animated change coupling visualization
- Improved legends
- Better documentation inside the system map
- Improved zooming (pinch-to-zoom, scroll-to-zoom, panning)
- It is now possible to suppress findings reported in PR checks to make the check pass.
- New PR statistics page with more detailed statistics for findings in PR checks.
- Bug fix: Ambiguous branch names are now handled properly and can be selected for analyses
Release Notes 6.1.3
CodeScene version 6.1.3 includes the following:
- Improvement: Allow disabling of login with license key
- Feature: Add an option to ignore non-main/master branches
Release Notes 6.1.2
CodeScene version 6.1.2 includes the following:
- Feature: Analysis rules are always read from the git repository
- Feature: Link detailed delta results page to the PR
- Improvement: Delete results on disk when analysis is interrupted
Release Notes 6.1.1
CodeScene version 6.1.1 includes the following:
- Improvement: Allow all (internal) users to change their password
- Bug fix: Make sure code duplication has details when degrading and several functions have the same name
- Improvement: Add scores to the hotspot code health graph popup
Release Notes 6.1.0
CodeScene version 6.1.0 includes the following:
CodeScene 6.1 comes with several improvements to the Code Health metric:
- Expand the code review with the detection of Complex Conditionals: complex conditional expressions make code hard to read, and contribute to the Complex Method code smell. It's a common issue, so we decided to add direct support for it. Complex Conditionals will be reported in the Virtual Code Review, the X-Ray, as well as our PR and IDE integrations.
- By default, any conditional expression with two or more logical operators (&&, ||) is flagged. You can change that default using the custom code health mechanism.
- Open range code health score to capture trends in complex hotspots: In previous versions, really complex code could hit the `1.0` code health floor. That meant there weren't any further trend warnings in case the code got worse. Starting with this release, we introduce a new code health algorithm with an open bottom range. That way, you can discover trends — both negative and positive — no matter how low the code health score is.
- New Code Health trend on the dashboard: For this release, we're changing what's shown in the code health trend graph to be the Average Code Health straight off. More intuitive. The scale of the y-axis adapts to the actual changes during the selected time span, making it easy to spot even small changes in the average code health trend regardless of the size of your code base.
The 6.1 release also contains all the features we released iteratively. Some key highlights:
- Software Portfolio Overview: The Software Portfolio gives a high-level overview of all your projects in terms of CodeScene’s four factors. It is designed to make it easy to see trends impacting your entire organization and to make high-level prioritization.
- New presentation page for PR reviews: the result page for a specific PR has been re-designed to provide a clearer presentation of the issues, including documentation and motivation for each rule.
Release Notes 6.0.41
CodeScene version 6.0.41 includes the following:
- Bug fix: Bad link on the license-exceeded page
- Improved erroneous release trend warning for mono-repo projects
Release Notes 6.0.40
CodeScene version 6.0.40 includes the following:
- Bug fix: Missing architectural system health biomarkers
- Bug fix: Missing color indication on X-ray for any file with a perfect score
- Improvement: Cut the duration of the X-ray in half and reduce the memory consumption
- Support Azure PM integration for any provider
Release Notes 6.0.39
CodeScene version 6.0.39 includes the following:
- Add metadata to code health trend sample points
Release Notes 6.0.38
CodeScene version 6.0.38 includes the following:
- Improved trial sign-up and login flow
Release Notes 6.0.37
CodeScene version 6.0.37 includes the following:
- GitHub PR integration now presents the results as a GitHub review.
- All PR integration presentations have been updated to provide more informative results
Release Notes 6.0.36
CodeScene version 6.0.36 includes the following:
- Introducing a new process of activating a free trial license
Release Notes 6.0.35
CodeScene version 6.0.35 includes the following:
- Bug fix: Malformed custom code health rules file causes analysis failure
- the Feature: Access the projects page filtered on groups via the Groups overview page
Release Notes 6.0.34
CodeScene version 6.0.34 includes the following:
- Add email taken from all-authors CSV to the endpoint GET /developer-settings/{developer_setting_id}/developers
- Bug fix: Inconsistent code health KPIs on dashboards and in reports
Release Notes 6.0.33
CodeScene version 6.0.33 includes the following:
- Improvement: Make branch warning into an INFO trace with a clear message for debugging
Release Notes 6.0.32
CodeScene version 6.0.32 includes the following:
- Bug fix: Character reference in the project's title
Release Notes 6.0.31
CodeScene version 6.0.31 includes the following:
- Bug fix: On-prem proxy auto-detection for MacOS machine
Release Notes 6.0.30
CodeScene version 6.0.30 includes the following:
- Bug fix: Corrected link URL for status badges
Release Notes 6.0.29
CodeScene version 6.0.29 includes the following:
- Bug fix: Prevent double "/" when saving Jira URLs in PM-issues
- Bug fix: Status badge generation
- Bug fix: Group layout
- Bug fix: Re-add Azure API URL as an advanced setting
Release Notes 6.0.28
CodeScene version 6.0.28 includes the following:
- Change the ssh folder owner to codescene
Release Notes 6.0.27
CodeScene version 6.0.27 includes the following:
- Bug fix: Support nullable reference types as C# arguments.
- Bug fix: Scheduling custom reports on "management overview reports"
Release Notes 6.0.26
CodeScene version 6.0.26 includes the following:
- Bug fix: Delta analysis fails when .keep files are renamed
Release Notes 6.0.25
CodeScene version 6.0.25 includes the following:
- Validate project ID when accessing analysis results
Release Notes 6.0.24
CodeScene version 6.0.24 includes the following:
- Button to return to the latest analysis from the project's configuration
- Add Docs for PM integration REST-API
- Fix error handling in case of invalid remote service SSL/TLS certificates (e.g. when configuring PR integration)
- Updated appearance of CodeScene status badges
Release Notes 6.0.23
CodeScene version 6.0.23 includes the following:
-
Bug fix: Custom thresholds when using a repository with global code health rules
-
Bug fix: Submit buttons on plugin configuration pages are unavailable
Release Notes 6.0.22
CodeScene version 6.0.22 includes the following:
-
Fix license server authorization
Release Notes 6.0.21
CodeScene version 6.0.21 includes the following:
-
Bug fix: Java Heap space depleted when updating exclude content
-
Bug fix: Fix parsing git file names with backslash followed by numbers
-
REST-API: PM Integration endpoints added
Release Notes 6.0.20
CodeScene version 6.0.20 includes the following:
-
Bug fix: DB migration column length
-
Upgrade Memento to 1.1
Release Notes 6.0.19
CodeScene version 6.0.19 includes the following:
-
Bug fix: Restore dashboard data items for the Architectural code health widget
Release Notes 6.0.18
CodeScene version 6.0.18 includes the following:
-
New tutorials available
Release Notes 6.0.17
CodeScene version 6.0.17 includes the following:
-
Bug Fix: Make all input fields in Swagger UI work properly
Release Notes 6.0.16
CodeScene version 6.0.16 includes the following:
-
Improve performance for Code Health calculations
Release Notes 6.0.15
CodeScene version 6.0.15 includes the following:
-
Improved code viewer
Release Notes 6.0.14
CodeScene version 6.0.14 includes the following:
-
Fixed DB migration for scheduled reports
-
Fixed the issue with the "always comment" option for PR request
-
Added a markdown editor at Configuration
Release Notes 6.0.13
CodeScene version 6.0.13 includes the following:
-
Software Portfolio
-
Fixed analyses of housekeeping based on age
-
Support for Roku's BrightScript language
-
Support personal access tokens for the Jira server. Password is used as a token if no user is specified.
Release Notes 6.0.12
CodeScene version 6.0.12 includes the following:
-
PR Integration: File comments and annotations are now put correctly on the diffs in the PR.
Release Notes 6.0.11
CodeScene version 6.0.11 includes the following:
- REST API: New endpoints for fetching analysis author statistics, see more: author-statistics
Release Notes 6.0.10
CodeScene version 6.0.10 includes the following:
- Fix another problem with a DB Migration
Release Notes 6.0.9
CodeScene version 6.0.9 includes the following:
- Fix a problem with DB Migration in 6.0.8 when using MariaDB
Release Notes 6.0.8
CodeScene version 6.0.8 includes the following:
- Additional fix to the problem with Sonar plugin configuration when using the H2 database
Release Notes 6.0.7
CodeScene version 6.0.7 includes the following improvements:
- Fix for SonarQube plugin configuration when using the H2 database
- A more robust handling for offline-mode logins
- Fix to the license activation page when the license expires
Release Notes 6.0.6
We've deployed the following feature in CodeScene 6.0.6:
-
REST API: New endpoints for fetching delta analyses data, see more: delta-analyses-list and delta-analysis-by-id
Release Notes 6.0.5
We've added a few improvements in CodeScene version 6.0.5:
-
PDF reports: removed subscriptions for deprecated report types.
-
Optimized page load performance for accounts with many projects:
- Drastic performance improvement of “Team and Developer” configuration pages if you share settings among many projects
- Faster projects dashboard polling
- Added a new LDAP connection setting: Disable recursive LDAP groups search that can significantly improve login times for LDAP users with many groups (See Configuration -> Users/Authentication -> LDAP Authentication Provider). The setting is disabled by default.
Release Notes 6.0.4
CodeScene version 6.0.4 includes 2 main bug fixes:
-
Fix for bug prevent the creation of duplicate aliases due to a race condition
-
Fix name mapping bug, now transition names are correctly mapped when using a custom language in Jira
Release Notes 6.0.3
We have deployed new features in CodeScene version 6.0.3:
- X-Ray: Code Health details are now presented per function in the X-Ray view
- REST API: added endpoints for KPI trends: getting the data behind the 4-factor graphs and metrics
Release Notes 6.0.1 & 6.0.2
The last two releases, 6.0.1 & 6.0.2, are targeting specific features and bug fixes:
- CodeScene now supports mapping users to roles at the project level to give access in a smaller scope.
- Bug fix: The analysis start date is now properly adjusted when adding a repo with a longer history to a project.
Release Notes 6.0
Our 6.0 release represents CodeScene’s largest product shift to date: the officially released 4-factor model delivers software engineering intelligence for your complete development life cycle.
The 4-factor model comes with new dashboards, giving you an instantaneous overview of any software project.
Fig. 254 CodeScene’s main dashboard offers a high-level overview of the current status with key trends for all projects.
Read all about the new 4-factor support in From Code to Delivery: the 4 factors model.
CodeScene 6.0 also includes this:
-
Anonymized diagnostics and usage information are now sent to CodeScene to help improve the product. This behavior can be disabled by setting the env var CODESCENE_SEND_DIAGNOSTICS_AND_USAGE to false.
Download instructions:
- For Docker installation pull the latest image here.
Release Notes 5.4
Cloud and On-prem:
- Now you can see how each of your projects is fairing across each of the 4 factors without having to dive into each of them individually.
Cloud:
- REST-API (Pro Plan and above): Previously only available to on-premise customers, you can now extract crucial data and execute commands using our REST API
- Ruby 3.0 Support: We are proud to announce full support for Ruby 3.0. A list of all languages CodeScene currently supports is available here
Coming soon:
Product Portfolio (Pro Plan and above): We are excited to share one more feature in the making, a Product Portfolio view... stay tuned for further updates.
Download instructions:
- For Docker installation pull the latest image here.