Archive

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.