Archive

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.

Released on February 22, 2024

Enhancements

• Inside the DevOps Portal Harbor was automatically added to all existing projects and users which are using the DevOps functions Docker registry and Helm chart repository.
• Automated testing is now done with Playwright directly on the Jenkins agents. Test results are presented by Allure Report which is integrated into the DevOps-as-a-Service Jenkins.

Improvements

• Improved error logging
• Prepared for more Jira project customization options

Bugfixes

• Project admins are automatically maintained as administrators for the oldest Agile Board connected with a Jira Project. When a role was saved for a project admin, this could lead to a pending sync when no Agile Board was found for the affected Jira project. Since it's allowed that project admins delete all Agile Boards connected with a Jira Project, this is now fixed.
• Assigning a user to a project which has none of his or her tools lead to a harmless pending sync. This has been fixed.
• Fixed flickering table columns which could occur when scrolling under certain circumstances.

Released on February 15, 2024

New Features

Harbor

• Added support for the new tool Harbor. Harbor is now the standard tool for the DevOps functions Docker registry and Helm chart repository inside DevOps-as-a-Service.
• A new tile for Harbor was added to the dashboard.
• Robot accounts for projects are automatically created in Harbor and injected as credentials into Jenkins projects. This allows the Jenkins Shared Library starting with v2.15.0 to automatically login to the hosted Docker registry and Helm chart repository of the project for pulling or pushing artifacts. The name of the user in Harbor and of the credentials in Jenkins is doaas-PKEY+jenkins-push-harbor where PKEY is the project key as defined in the DevOps Portal.

Gitea

• Added support for the new tool Gitea. Gitea will become the new standard tool for the DevOps function Artifact repository inside DevOps-as-a-Service. Furthermore, it's a viable alternative to seasoned SCM tools like Bitbucket or GitLab.
• Technical users for projects are automatically created in Gitea and injected as credentials into Jenkins projects. This allows your delivery pipelines to automatically login to the hosted Artifact repository of the project for pulling or pushing artifacts. 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.

Bugfixes

• A problem with unnecessary white space was fixed, which could occur with the new turbo scrolling feature when a search filter was previously used.

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.

Released on February 07, 2024

Enhancements

• When a project is created, it's now possible to deselect some tools. Therefore, you can now create projects which use just a subset of tools. By editing the project later, you can add at any time more tools. Removing tools after the project creation is not possible to avoid any data loss.
• Introduced tiles for the new tools AI Engineer and IDEaaS on the dashboard.
• Prepared support for the new tool Harbor.

Improvements

• The ApacheDS LDAP server was updated to the latest version
• Text in table columns is now automatically shortened (e.g. very long email addresses) to avoid line breaks or very wide columns.
• Improved OIDC group management to better support upcoming new tools.

Bugfixes

• Searching in the audit log was not working, but is fixed now.
• The selection count now only counts selected and visible elements. Elements can be hidden by a search filter and were previously counted, too.
• On the users page sorting by project role could be wrong when a search filter was used, another project was selected and then the filter removed again. This works now as expected.
• Creating new technical users on Jenkins was broken, but now works again.

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.