Release Notes v4.2
We’re thrilled to announce that we’ve released version 4.2.0 onDec 23, 2020
Download on the Atlassian Marketplace for Data Center and Server
When upgrading from an app version 2.x or 3.x, please read our Migration guide to app version 4.
Improvements
Allow creation of manual webhooks and do not enforce SonarQube admin permissions
App version 4.1 configured SonarQube webhooks for the app automatically, and this required SonarQube admin permissions, which were also enforced when configuring a SonarQube server connection.
This has now been changed and the app also allows the manual creation of webhooks, and thus SonarQube admin credentials within the app are not required anymore. For manual webhook creation, see our dedicated Wiki page Configure Webhook in SonarQube™.
Support SonarQube 7.7 as lower bound version
While app version 4.1 required SonarQube >= 7.8, we now also allow 7.7. When using SonarQube 7.7, please make sure to pass -Dsonar.analysis.scmRevision=COMMIT_ID to your SonarQube analysis.
Show warning in server settings if the minimum SonarQube version 7.7 is not given
The app now displays a warning when the configured SonarQube servers do not have versions >= 7.7 in the SonarQube server settings.
Bug fixes
Error “Field 'NO_SONAR_PROJECT_BEHAVIOUR' does not accept null values” when using project settings inheritance when upgrading from older app versions
For main branch with branch in Sonar project key, app shows “component not found” error in source file view
Changelog
4.2.4: released on Jun 28, 2021
Simplify Merge Check configuration
Fix presentation differences in ‘coverage’ and ‘duplication' measures compared to SonarQube
Option to hide access to all sonar projects in repository settings
Improved error message when multiple repositories use the same sonar project key
4.2.3: released on May 26, 2021
Fix Bitbucket 7.13 support, missing backbone-brace module
4.2.2: resolved issues on May 11, 2021
Sonar Quality Gates are not shown in pull request on Bitbucket 6.10
A Sonar Server configuration couldn’t be deleted when a User still had a token present.
Existing user tokens get now automatically removed with Sonar server configuration.
Added support for newly introduced Sonar Quality Gates.
4.2.1: resolved issues on Apr 16, 2021
Global app settings requires Super Admin permissions, Admin permissions only lead to a permission error
Error occurs when enabling “User-level authentication” without any token configured
Return non-successful HTTP error codes from the app in case of webhook problems
When there is no SCM reference during Sonar analysis and webhook callback, the app cannot create annotations in Bitbucket
An endless "Fetching data from SonarQube..." spinner can be shown in the file source view of Bitbucket
Show timeout status label if timeouts occur on pull request and branch lists
SonarQube tags cannot be selected in the combo box of the Sonar annotated panel on first render
Do you have any questions, suggestions, or problems?
Let us know. We’re glad to help!
SONAR™, SONARQUBE™ and SONARCLOUD™ are independent and trademarked products and services of SonarSource SA: see sonarsource.com, sonarqube.org, sonarcloud.io.