Roll-out to customers starting Unknown macro: time. Click on this message for details.
The [time] macro is not in the list of registered macros. Verify the spelling or contact your administrator.
.

Enhancements

• The projects page now shows the amount of members of a project. Suitable to learn about the size of a project. Old projects with 0 members are certainly good candidates for a retirement.
• Issue-type schemes in Jira are now automatically deleted when the matching project is deleted on the portal.
• Prepared the UI at multiple places for the upcoming Bulk Role Management feature.
• Prepared LDAP structure for the upcoming Rancher 2.x auto-provisioning support.
• Adapted security measures to the upcoming hosting based on Rancher 2 and Kubernetes.

Bugfixes and Improvements

• Streamlined the different pages so that similar things are solved similar.
• The top magenta header is now better aligned and uses less space.
• Jira ServiceDesk was renamed to Jira Service Management to reflect the change of the product name of Atlassian. The short version is ServiceMgmt.
• Changes on the Terms & Conditions are now logged to the audit log.
• Audit log now shows real usernames instead of UUIDs for logins.
• Searching for translated columns is now working using the currently selected locale.
• Projects could not be created if a Rancher environment with the same prefix had been already manually created.
• Caching problem after version update is now solved. Reload message will no longer appear starting with 1.2.2.
• Improved automated testing during development.

Known Issues

• User update/lock action can be stuck when the user was assigned to another organization after the user's first project role assignment. The ops team can automatically repair it for you.

SDCLOUD-3046 For maven projects the default values of imageName, appName and helmReleaseName are now automtatically set to the artifactId as defined in pom.xml. For appVersion the version as defined in pom.xml is used. For all other types of projects the default remains to be the name of the build job respectively '1.0.0'. The default for chatVersion has been slightly changed, too. Now appVersion with '00' appended is used. Of course you can still override all of these values by passing the matching arguments to sdcPipeline().

See Jenkins Shared Library for more information.

Enhancements

• When the portal creates a new project on Jira an associated Agile Scrum Board is automatically created, too. In the past users could not modify the configuration of this default board. Now if a new ADMIN role is assigned the user will be automatically added to the list of administrators of the board. This allows project admins to configure the board like they wish. One of the most useful possibilites is to add new columns and statuses. By doing this, new kinds of workflows can be created on the fly for the project. See Jira#ManageBoards for complete instructions. To put all existing ADMIN users of a project to the list of board administrators simply invoke Resync Roles using the More menu on the Projects page of the portal. This feature is available both to Project Admins as well as to Global Admins. Further changes to the roles will automatically sync with the list of board administrators.
• A User Profile page was added to the Account menu which shows information about the own user account.
• Added search filter for Technical Users like already available for Users.

Bugfixes and Improvements

• Searching now also considers the created timestamp of Projects and Users.
• For Projects, Users and Technical Users the page header now shows the amount of displayed items when the search is used, but also shows always the total amount of items.
• The amount of used licenses is now also in detail calculated for Open Source tools. See Administration / Limits in the portal for more information.
• Massively improved the German translation of the portal.
• The validity of invitation links in invitation emails is now by default 1 week. You still can send out new invitations by using the Reinvite menu item in the More menu of the affected user.
• The footer is now always displayed at the very bottom of the page and displays the complete content also on very narrow windows.
• Due to data privacy issues the created timestamp and list of assigned tools for other users than themselves can no longer be seen by ordinary users. It's still available for Global Admins.
• Solved problem with removing user roles in Gitlab which could be triggered only in some special conditions.

Known Issues

• User update/lock action can be stuck when the user was assigned to another organization after the user's first project role assignment. The ops team can automatically repair it for you.

We want to inform that our DevOps Helpdesk number has changed.

• new number: +49 69 9731799115

Our old number has been replaced by the new one.
The number is available since 25.03.2021 and occupied between 08-18 CET.

The Project DevOps as a Service as well as the included System SDCLOUD Release 1.0 have passed the PSA process. These are the official identifiers used in the PSA process of Deutsche Telekom Group for the product DevOps-as-a-Service.

The Privacy and Security Assessment (PSA) process was introduced to ensure compliance with security and data privacy requirements in development projects. It regulates support and advice from security and data privacy experts – Project Security Manager (PSM) and Data Protection Consulter (DPC) as well as the security and data privacy approval of the systems.

The process has three main objectives:

• A consistent and adequate security and data privacy level in all products, systems and platforms that have to be updated or created from scratch.
• A support level adapted to project complexity and criticality through the introduction of categorization at the start of each development project.
• An integrated process for information security and data privacy as part of the product and system development process (to avoid redundancies in the approval process).

The process can be used on all IT and NT systems, regardless of size and complexity. It ensures greater transparency, improved project support and an adequate level of protection for products from the Deutsche Telekom Group.

Please see the PSA Booklet for more information:

The new version v2.7.1-11 of the Prometheus Global Stack was just released. This version contains the following highlights:

• The Blackbox-Exporter is included again, to be an integral part of a global monitoring solution
• Configuration file for Blackbbox-Exporter is located on a persistent volume and can be adjusted to individual needs
• prom-conf helper container now includes some useful editors like nano and vim to edit the config files more convenient
• Some other improvements, see Readme file

Before upgrading existing stacks, customers must check if a Blackbox-Exporter service has already been integrated manually.  If this is the case, then please note:

• If the existing exporter has been named "blackbox-exporter", then it would be overwritten by the catalog update.
• If the existing exporter has a different name, then a second exporter would be installed into the stack during upgrade. Migrate your existing config (see next point) and change the hostname for the exporter in Prometheus config to "blackbox-exporter:9115". Afterwards manually delete the old exporter from the stack.
• An already existing adapted persistent config file wouldn't be overwritten during the update. But the new exporter from the update would use the config file under /etc/prom-conf/blackbox.yml within the blackbox container. Thus ensure, that your existing adapted config file is moved to /etc/prom-conf/blackbox.yml within the blackbox container.

If there are any questions, please contact the DevOps-as-a-Service support via Service Desk.

We would also like to refer to the renewed Monitoring Documentation.

This week we started to roll-out IAM (Identity and Access Management) 1.0.0 for our customers.

New Features

Global Licence Management

For each user, ADMINs can now decide which licenses should be assigned and which not. This helps you to save licences as some users may not require access to all tools. The feature is available using the Edit User menu item as shown below:

Access to Open Source Tools is always granted since no licence costs are involved.

ServiceDesk is an optional commercial plug-in to Jira. It's now possible to use the self-service portal to assign or unassign ServiceDesk licenses to your users that are working as agents for your service desk. From the user perspective you already know ServiceDesk since we are using it ourselves to offer you the best possible support for your DevOps-as-a-Service instance.

Helm Chart Repositories

Support for Helm Chart Repos was added. So for each project created by the self-service portal there's now also a Helm Chart Repo in addition to the existing Maven2 Repo and the private Docker Registry. Since Helm Repos share the same namespace with Maven2 Repos the suffix -helm is added to the Project Key.

Further Improvements

• Added support for Jira v8 auto-provisioning

• Prepared support for connecting to customer's ActiveDirectory or LDAP-Server.

• The Audit log is now sorted with last entries first by default.
• Navigation improved on some pages
• Security was increased a lot.
• Several bugs were fixed.

Known Issues

In the past, users received a licence when they logged in to Jira, Confluence or Bitbucket the first time. This is now done instead by the portal when a user is created. It can be that you have users that never logged in to Jira, Confluence or Bitbucket and therefore never received a licence inside the application. Therefore they will not be able to login now to these tools. To repair this, simply remove the licence from the affected user and save. Then add the licence again and save.

We're proud to announce that our product DevOps-as-a-Service is now officially promoted on https://cloud.telekom.de/de/infrastruktur/devops-as-a-service. We managed to get the German version published before christmas and will add the English version beginning of 2020.

If you use the menu on https://cloud.telekom.de/ simply go to the Infrastruce as a Service menu and select one of the six detailed pages that we currently offer for DevOps-as-a-Service. A contact form which you can use to Order DevOps-as-a-Service is also available.

We whish you a Merry Christmas and a Happy New Year!

This is your wiki's blog first post. Its goal is to provide a short description of your blog's main features.

• You can create new blog posts through the input field located on your Blog's homepage. The status of a blog post may be any one of the following:
  • Unpublished: your post is still a draft. It can be seen by its creator and by administrators. Once you have clicked publish, you cannot unpublish a post. However, you can choose to hide it.
  • Published: your post can be read by every user that has access to your blog.
  • Published & hidden: your post is published but only its creator and admins can see it. This is useful if you need to make modifications on a post that has already been published by mistake.

• Every blog article can be tagged and/or categorized:
  • You will be able to browse posts by category using the panel located on the left of the page
  • You can create new categories and subcategories when creating a new post
  • The use of tags allows your article to be found by browsing your wiki's tags, along with any other wiki document

• Blog-specific panels are available on the left of your blog page:
  • The recent posts lists the most recent entries to any visitor of the blog
  • The unpublished panel lists the blog posts you created, but didn't yet publish
  • The categories panel lets you browse blog posts listed by category and subcategory
  • The archive panel lets you browse blog posts by publication date

Happy blogging!