Enhancement
Sonar Project Management Enhancement
Previously, a new Sonar project was created for every build executed through the Build Pipeline. This resulted in multiple Sonar projects being generated for the same application across different build executions.
The system has been enhanced to create a single Sonar project for an application and associate subsequent build executions with the same project using version numbers. This provides better project organization and simplifies Sonar project management. Only the user who creates a Sonar project can view and access it. Other users cannot view, search for, or access projects created by another user.
Default Workbench Client Support for Multi-Landscape Deployments
Previously, the deployment configuration supported only a single target client for transport imports. As a result:
-
Customizing transports were imported into the configured target client.
-
Workbench transports were also imported only into the same target client.
-
If Workbench transports needed to be deployed to additional clients or landscapes, users had to perform manual import activities.
Current Enhancement
A new field, Default Workbench Client, has been introduced in the Validation ,Deployment and Import via TOC tasks.
When the Default Workbench Client is configured:
-
Customizing transports continue to be imported only into the primary target client.
-
Workbench transports are automatically imported into:
-
The primary target client configured for the deployment.
-
The Default Workbench Client specified in the deployment configuration.
Example Scenario
A deployment is configured with the following settings:
-
-
Default Workbench Client: Client B
Deployment Behavior
As a result, Customizing transports continue to be imported only into their designated target client, while Workbench transports are automatically imported into both the primary target client and the configured Default Workbench Client.
