Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Code has been added which will be later used by the Jenkins Shared Library to allow even better integration of SonarQube within DevOps-as-a-Service. The first planned feature is the possibility to automatically connect Bitbucket git repositories with SonarQube results. This will enable the Pull-request decoration in Bitbucket which is supported by SonarQube instances with Developer or Enterprise licenses. The second planned feature will allow the delivery pipeline to set the desired quality gate for the git repository.
A new RestAPI v2 has been added for pilot customers, which can be used to automate actions in the DevOps Portal. The API will be released for all customers when all important calls have been added.
Improvements
For larger customers with possibly hundreds of projects, DevOps Portal will now configure longer intervals for the Bitbucket organization folders in Jenkins. This will ensure that the load on the Jenkins controller is not getting too high due to continuously checking for new git repositories on Bitbucket.
Bugfixes
When the user changes the project on the Home page, some links in the tiles have to be updated. When the new link was arriving too slow, it could happen that a link was still pointing to the previously selected project. This has been changed, so that the link will be a general one until the new project information has been retrieved.
The selection box for the current project on the Home page was not properly losing focus when a new project had been selected. This led to the problem that the first click on one of the links was swallowed. This is fixed now.
The portal role of a user was not properly displayed on the user details page, if the logged-in user was not a Portal Admin.
When an organization was created containing some specific special characters, it could happen that the success message was not properly readable.
