Released on March 09, 2024
PSA (Privacy and Security Assessment) Compliance
- Updated all PostgreSQL databases to hardened version with additional network access protection.
Enhancements
- Portal CREATORs can now see all users and organizations, like Portal ADMINS, totally independent of their own organization. This is changed, so that every CREATOR can really onboard new users from different companies. If necessary you can at any time change the Portal role of a CREATOR back to USER, when he or she is finished with creating new projects and users. For standard USERs the visibility rule stays like it was: only project admins in the default organization can see users in other organizations.
- The credentials for pulling and pushing to Gitea which are automatically injected into Jenkins projects are now keeping a Gitea token in the password part of the credential. This allows to use the credential directly for any operation, since most package accesses require a token of the user instead of its password. As before, the name of the users in Gitea and of the credentials in Jenkins are PKEY-jenkins-pull-gitea and PKEY-jenkins-push-gitea where PKEY is the project key as defined in the DevOps Portal.
- Automated testing is now using Video Recording for Playwright.
Improvements
- The support for IDEaaS (IDE as a Service) was improved to allow the IDEaaS roll-out to pilot customers.
- To improve the reliability of the auto provisioning process, all outstanding synchronizations are now immediately persisted to the database. Previously this was only done when the first try was not successful.
- Some additional permissions which were added to Jira are now also set by the DevOps Portal. Effectively there is no change of functionality for the project roles.
- When a retired project has been long enough in RETIRED state (usually one day), the delete operation is now automatically enabled. It's no longer required to reload the page.
- Since Gitea is using a common namespace for users and organizations, the DevOps Portal will no longer accept to create a technical user and a project with the same name. In addition, some names reserved in Gitea won't be accepted by the Portal to avoid any problems.
- Automated auto provisioning testing of tool updates is now faster, allowing a quicker roll-out of updated tools.
Bugfixes
- The DevOps-as-a-Service permission scheme in Jira was not correctly set for freshly created projects. This has been fixed and affected projects have been repaired.
- Assigning roles to technical users which have not yet been created on Jira will now correctly fail to be triggered later again.
- Gitea is no longer sending invitation mails to users which manage their password on the DevOps Portal.
- The Gitea organization folder in Jenkins projects was broken after first discovery of a buildable git repository. This is fixed now.
Known Issues
- Unfortunately, the links to Agile Board and Backlog in the Jira tile of the DevOps Portal homepage do not work properly for users which have more than one project. In fact, the links will lead to the last visited agile board on Jira, independent to the project selection on the homepage of the DevOps Portal. This is caused by the fact, that agile boards are not part of a Jira project, but instead are independent entities. We are striving to find a solution for the problem in a future version.