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
  1. ReleaseOwl User Guide
  2. Working with Release Pipelines
  3. Pipeline Tasks

GCTS Merge Task

PreviousMessage Listener TaskNextGCTS Activate Task

Last updated 6 days ago

GCTS Merge Task

This Task is used when a hotfix changes need to be merged to other development branches. After a major release of a project, the changes from the master branch can be merged to other development branches.

Fill in the required details:

Field

Details

Name

Enter a unique name for the GCTS Merge task of your choice.

GCTS Environment

Select the source and target GCTS environments from the dropdown menu. This defines the environments for the merge.

Domain Controller

Automatically populated based on the selected GCTS environment. Indicates the transport controller managing the process.

System ID (SID)

Auto-filled field that uniquely identifies the systems involved (e.g., S4D.100). Ensures proper linkage between environments.

GCTS Repository (Repo)

Select the repository from the dropdown menu in the source environment. The corresponding repository in the target environment is automatically displayed.

Branch

Select the source branch (e.g., dev) and target branch (e.g., qa) manually from dropdowns to ensure proper branch mapping.

Notify Users

Sends notifications to relevant stakeholders upon merge completion. Ensures transparency and team awareness.

Forward Merge

Automatically propagates merged changes according to system landscape hierarchy (e.g., dev → QA → preprod → prod).

Description

Any message that is to be conveyed to the task performer can be mentioned here.

Note: If you are moving from dev to prod directly without going through quality, you don't need to check the forward merge.