We’re proud to announce a new release of CodeScene, version 3.2!
CodeScene 3.2 comes with single sign-on support using OAuth2/Open ID Connect, which means you can authenticate using GitHub, GitLab, Google ID, Azure AD, etc. We also include a new team composition analysis that is used to highlight the effects on author churn on a project.
Team Composition and other New Features
- Single sign-on support using OAuth2/Open ID Connect: CodeScene supports the Authorization Code Grant flow, and uses the token received through the authorization process to access user and team info from configurable URL:s at the OAuth2 provider. Configure a provider to enable single sign-on in CodeScene.
An example on SSO using GitHub as an OAuth2 provider.
- Team Composition analysis: We introduce a new graph that shows the team stability over time. We have found it useful to highlight the effects of High Author Churn with respect to on-boarding effects as described in our blog article. Here are two contrasting examples:
CodeScene visualizes team composition with respect to contribution time on the project.
An example on high developer churn, likely to lead to low system mastery and constant on-boarding costs as the team isn't allowed to build up experience.
- Optionally rename Jira tasks to group multiple tasks to the same logical type of work: This feature lets you aggregate different Jira tasks to the same logical type of work. This lets you calculate trends to differentiate between planned and unplanned work.
CodeScene calculates trends in planned vs unplanned work.
Improvements
- Include the project name in the CI/CD response for presentation purposes.
- Fix the view for System Level trends when no trends configured.
- Detect test code smells for Groovy assertions.
- Fix UI glitches for the X-axis in commit trends for long-lived projects.
- Minor bug fixes and improvements.
Get your license for CodeScene here.
