Blog

Release of CodeScene 2.2

We’re proud to announce our 2.2 release of the CodeScene on-premise version!

CodeScene 2.2 comes with a new set of branch analyses that let you detect delivery risks and measure your lead times for different features. We also introduce an author mapping interface that lets you resolve author aliases directly in the UI, and expand the Project Management analyses to measure costs on an architectural level.

New Features

  • Branch Measures: CodeScene’s new branch analysis detects delivery risks and highlights the lead times for each feature branch. Use this information to prioritize tests and code reviews, and also to get insights into your branching practices to ensure branches are kept short lived. Read more about the branch measures here.

An example on CodeScene's new branch analysis.

  • New Branch Monitor: CodeScene presents an additional monitor view that is continuously updated with the status of your ongoing work. The monitor view is designed to be presented on a TV in the office.

Launch the branch monitor view from your project's history.

  • Calculate Costs on an Architectural Level: Earlier versions of CodeScene let you integrate with project management tools like JIRA to analyze cost trends on a file level. However, in many systems the semantically interesting unit isn’t individual files but rather sub-systems and components. Thus, CodeScene now calculates the same cost metrics on an architectural level too. All you have to do is to enable your architectural analyses. Read more about the cost analysis here.

Calculate hotspots by costs on architectural level.

  • Resolve Author Aliases via the UI: It’s quite common to find Git repositories where the same author has multiple aliases. This biases the social analyses, so we need to resolve those aliases. Previous versions of CodeScene relied upon Git’s .mailmap. While we still support .mailmap, this new version of CodeScene also lets you revolve aliases directly via the UI, which is faster and simpler.

Resolve authors with multiple aliases through the UI.

  • Support Google’s repo Tool: repo is a tool built on top of Git to manage codebases separated into multiple repositories. CodeScene now supports the repo tool. Just point CodeScene toward your project’s manifest file.

  • X-Ray support for Groovy: CodeScene’s X-Ray now has support for the Groovy language.

  • Customer Portal to Manage Subscriptions: CodeScene now gives you access to a customer portal where you can manage your subscription. This makes it straightforward to scale your subscription as the number of active authors in your projects varies.

Improvements

  • Correct handling of nested, escaped strings in the C# X-Ray.

  • Let code age measurement start from the time of the last commit.

  • Bug fix for the glob pattern handling in architectural components to ensure non-greedy consumption.

  • Use an ordinal color scale for the coordination needs visualizations.

  • Introduce a free text project description field where you can add notes about the configuration and/or stakeholders.

  • Document the configuration of Nginx and reverse proxies.

  • Minor bug fixes and improvements.

Get your license for CodeScene here.

Adam Tornhill avatar.
,
comments powered by Disqus