Validation Task
Last updated
Last updated
Validation task is added to perform Static Code Analysis checks and generate the validation report to view the errors encountered. You can continue the execution of the pipeline even upon failure by checking the checkbox – Continue On Failure by fixing the errors seen in the log and re-running the release pipeline.
Field / Option
Description
Name
Enter any name of your choice for the validation task being created. Note: Only letters, numbers, underscores (_), and periods (.) are permitted.
Description
Any message that is to be conveyed to the task approver can be mentioned here.
Domain Controller
Dropdown to select the domain controller for the transport landscape.
Source
Source system from where transports will be validated.
Target
Target system where the transport is expected to move.
Pipeline Execution
Section indicating execution preferences for the task.
Continue on Failure
Checkbox to allow pipeline execution to continue even if validation fails.
Quality Checks
ATC Checks: Executes ABAP Test Cockpit (ATC) checks to analyze code quality, syntax errors, performance, and security compliance.
Impact Analysis: Checks how the changes in the transport affect other dependent or referencing objects across systems.
Unit Tests: Runs ABAP Unit Tests to verify the functional correctness of the objects in the transport.
User Story Dependencies (Beta): Identifies and validates dependent user stories to prevent conflicts or incomplete deployments.
Note: You can select any one or more of the following Quality Checks when configuring the validation task.
Field / Option
Description
Name
Enter any name of your choice for the validation task being created. Note: Only letters, numbers, underscores (_), and periods (.) are permitted.
Description
Any message that is to be conveyed to the task approver can be mentioned here.
CPI / API
Select the respective target environment where validation is to be performed.
Pipeline Execution
Section indicating execution preferences for the task.
Continue on Failure
Checkbox to allow pipeline execution to continue even if validation fails.
Quality Checks
CPI Lint Analysis: Validates integration flows, scripts, and configuration for SAP Integration Suite.
Unit Tests: Executes CPI unit tests to validate business logic.
User Story Dependencies (Beta): Identifies and validates dependent user stories to prevent conflicts or incomplete deployments.
Note: You can select any one or more of the following Quality Checks when configuring the validation task.