Released on April 27, 2023
Enhancements
- The Bitbucket Project Folder in Jenkins which automatically discovers and builds all git repositories gets now an improved configuration for freshly created projects
- Pull-requests opened on Bitbucket are automatically discovered and built on Jenkins. Previously, only real branches were discovered and built.
- A Pull-request is simulating the merge from one branch to another, but takes place on Jenkins only. To really merge the Pull-request to the destination branch, one of the reviewers has to press the Merge button on Bitbucket when the review and Pull-request builds are fine.
- The Discover branches strategy is set to all branches to prevent losing build information of the source branch. Instead, the Jenkins Shared Library is avoiding building new commits to the source branch if a Pull-requests was already opened. This reduces build work on Jenkins agents to 50%.
- In Scan Organization Folder Triggers the Interval for Periodically if not otherwise run is reduced from the Jenkins default of 1 day to 1 hour for quicker discovery of new git repositories. We don't recommend to use lower values since Jenkins will be otherwise busy the whole time scanning for new git repositories. If you have created a new git repository, you can at any time click on Scan Organization Folder Now in the Bitbucket Project Folder. This will trigger a manual scan for git repositories. All of this is not required to discover new branches or new commits. Both of these changes are automatically propagated from Bitbucket to Jenkins.
- On the backend, a feature has been prepared which will offer in the future the possibility to find users inactive for a longer time period like e.g. 90 days
- The description field of a project is now also propagated to the Jenkins folder of the project.
Improvements
- Improved backend monitoring
- The metrics page for Portal Admins was removed since it was of limited value for end-users.
- Added more automated tests to backend development
- Moved success and error message more towards the bottom of the screen, so that it's always visible even when scrolling long lists.
- Error messages concerning the password entry field have been improved to give more exact information about minimum and maximum length.
Bugfixes
- Fixed the edit tech user dialog so that changing the description without changing the password works again.
- Fixed a problem when 2FA was switched off for a user.
- Fixed pending syncs which could happen when a project admin had assigned a role to a user without licenses for freshly added tools, like e.g. SonarQube. The roles were already assigned, so the pending sync could be ignored.
- Fixed problems in back-end when handling more than 1000 users in the LDAP server.
- Since no customers are remaining using Rancher 1.6, the user update/lock action can no longer be stuck when the user was assigned to another organization after the user's first project role assignment.