Released on December 01, 2022
Only released to SonarQube pilot customers.
Enhancements
- Now offering SonarQube as an additional optional tool with full integration into DevOps-as-a-Service. The latest version of SonarQube - at the moment of writing - v9.7.1 is offered. Project roles are fully managed by the DevOps portal. Please note that SonarQube projects are different to projects in the DevOps portal and the existing tools. In Bitbucket a project can have multiple git repositories which all have their own build pipelines in Jenkins. SonarQube projects contain the scan results of just one git repository. They are created on-the-fly using the Jenkins Shared Library when a scan is executed but the projects is not yet existing. To activate SonarQube it's required to save every project in the DevOps portal first. After this step SonarQube can be added to individual users just by editing them. More information about SonarQube and its integration into the DevOps toolchain will be published seperately.
- Auto-provisioning for project roles in Rancher 2.6 was added.
Improvements
- Since LDAP cannot properly handle organization names which differ just concerning uppercase and lowercase letters, the check for unique organization names is now case-insensitive.
- Improved testing of auto-provisioning for Confluence, Bitbucket and Keycloak.
- Updated to more recent nodejs and npm versions.
- Improved JavaScript code.
- Moved more internal testing to new Rancher 2 RKE clusters.
Bugfixes
- Improved layout of bubble help pop-ups.
Known Issues
- If a user is locked or saved after editing it can happen that the portal lists a pending synchronization if the user cannot be found on SonarQube because he or she never got the tool assigned. This warning is harmless and will be fixed in the next release.
- For customers which have their own support email address configured in the portal footer there is the following issue: permanent pending syncs are sent as a warning email to this address. This was not intended and will be fixed in the next release.
- User update/lock action can be stuck when the user was assigned to another organization after the user's first project role assignment. The ops team will automatically repair it for you. Problem is fixed for customers which have Rancher v2.6 in their toolchain as it happens only with Rancher 1.6.