Archive

Released on April 25, 2024

Enhancements

• When Jenkins discovers new Git repositories on Gitea, it will now automatically configure webhooks in Gitea, which will trigger Jenkins automatically when new branches or commits are added. In addition, the latest build status is now shown in Gitea for each repository. Therefore, the Gitea-Jenkins integration now offers the same functionality as the Bibucket-Jenkins integration.
• The display names of automatically populated organization folders in Jenkins are now set to "Projectname Bitbucket" and "Projectname Gitea". This helps esp. customers which use both tools to manage Git repositories to properly distinguish these two folders. To activate this for existing projects, simply Edit and Save the project in the DevOps Portal.

Improvements

• The language selected by the user is now remembered across sessions in the persisted user information.
• The Synchronization page is now using the Turbo scrolling with pageless access to all entries.
• The Service Desk link in the footer has been updated to lead to the new support Kanban boards.
• Added the AI Engineer logo.
• For some cases related to role changes, no relogin is required to adapt to the changed permission set.
• The job queue working on outstanding synchronizations has been improved for faster processing of pending actions that need to be retried again.
• Resyncing roles is now faster for Harbor.

We just published a new page, which gives our customers a better transparency regarding:

• Information to the latest release of the self-service portal (release notes)
• Information regarding planned improvements and enhancements (release planning)
• Information about other enhancements and new features, planned for the next months

All this information can be found here: Release Notes

We suggest watching that page to keep informed in case of any changes.

Released on March 27, 2024

Enhancements

• Gitea has been added to the Dashboard. Customers which use Gitea for Source Code Management get a tile for Git Repositories and Pull-Requests:
  
  Customers which use Gitea as an Artifact repository get a tile for Packages:
  
• We have developed an Extended API Plugin which adds missing functionality to Jira. The first version deletes Screens and Screen Schemes that are left behind when a project is deleted. Not deleting them makes Jira slow over time and clutters up the display of some administration pages.

Improvements

• Personal Git repositories on Gitea are now automatically deleted when a user is deleted. The DevOps Portal will show a warning message about this.
• The number of pending synchronizations is now shown on the Synchronization page.
• Clicking on the T-Systems logo on the login related screens will now make the browser go to the DevOps Portal. This can be used if the redirect to the DevOps Portal is not working properly after a password reset. This problem is caused by a known bug in Keycloak https://github.com/keycloak/keycloak/issues/21127 which was not fixed yet.

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 March 12, 2024

Improvements

• Matching the IDEaaS release, the links to the tool were adjusted to work in all DevOps-as-a-Service instances which have IDEaaS installed.

Bugfixes

• The additional Jira permissions introduced in 1.6.4 now also work on Jira instances without Jira Service Management installed.
• When scrolling through lists, it could happen that additional white space was visible between the rows. This has been fixed.

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.