ReleaseOwl Docs
  • ReleaseOwl Admin Guide
    • General Administration
      • User & Role Management
      • Project Management
      • Landscape Registration
      • Global Credential Management
      • Settings
      • Landscape Connectors
      • Parallel Landscape Configuration
      • Static Code Analysis
      • RO Agents
    • ALM Integrations
      • Jira
        • Jira Cloud
        • Jira On-Premise
        • Jira Automation Rules
      • Azure DevOps
      • ServiceNow
      • Freshservice Integration
    • Other Integrations
      • ReleaseOwl Callout Feature
      • DocuSign
    • Landscape Mapping
  • ReleaseOwl User Guide
    • Change Management
      • Backlog
      • Sprints
      • User Stories
      • Release Versions
      • User Story Dependency
    • Transport Management
      • On-Prem Environment Registration
      • Creation of Transports
      • Transport Validation and Analysis Reports
      • Transport Promotion and Pipeline Activity
      • Transport Management Actions
      • Transport of Copies
      • Retrofit & Conflict Resolution
      • gCTS
        • Build pipeline support for onPrem Fiori
    • SAP BTP
      • Administration
        • Credential Management
        • Cloud Environment Registration
      • Working with Build Pipelines
        • Static Code Analysis
        • Change Log Analysis
        • Download Artifact
        • Labels
      • GIT Ops
    • SAP API
      • Adminstration
        • Credential Management
        • Cloud Environment Registration
      • API Management
    • SAP CPI
      • SAP CPI Integration with ReleaseOwl
      • CPI Test Generator
      • CPI Management
        • Synchronize CPI Artifacts
        • Artifact Versions
        • CPI Artifact Comparison
        • Backup & Rollback
        • CPI Validation - CPILint
        • iFlow Unit Testing
        • Integration Advisor
    • SAP Analytics Cloud
    • SAP Datasphere
    • Working with Release Packages
      • Create Release Package with User Stories
      • Create Release Package with Transports
      • Release Package Validation with Transports
    • Working with Release Pipelines
      • Pipeline Tasks
        • Approval Task
        • Callout Task
        • Manual Task
        • User Story Status Task
        • Test Execution Task
        • Message Listener Task
        • GCTS Merge Task
        • GCTS Activate Task
        • GCTS Switch Task
        • Import via Toc Task
        • Transport Retrofit Task
        • Release Transport Task
        • DocuSign Approval
        • Validation Task
      • Use Cases
        • Automated Transport import along with Transport Promotion
        • Automated MTAR Deployments
        • Automated CPI Deployments
    • Test Automation
      • HCL OneTest
        • Test Configurations
        • Running Automated Tests with Release Pipelines
      • Tosca Integration
      • Integrating UiPath with ReleaseOwl
    • My Tasks
    • Multiverse
    • Utilities
      • ABAP Version Compare
      • gCTS Merge
Powered by GitBook
On this page
  • Validation Task for Transport Management
  • Validation Task for CPI and API Projects
  1. ReleaseOwl User Guide
  2. Working with Release Pipelines
  3. Pipeline Tasks

Validation Task

PreviousDocuSign ApprovalNextUse Cases

Last updated 6 days ago

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.

Note: The behavior and configuration of the Validation Task differ based on the selected project type.

Validation Task for Transport Management

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.

Validation Task for CPI and API Projects

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.