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. Utilities

gCTS Merge

PreviousABAP Version Compare

Last updated 1 day ago

gCTS Merge Configurations

This feature allows you to define merge configurations between two Git-enabled SAP systems using gCTS (Git-enabled Change and Transport System). It helps in synchronizing and merging branches across different systems within your transport landscape.

To create a merge configuration, the following fields are used:

  • Name: A unique name for the merge configuration.

Source Configuration:

  • GCTS Environment: Select the source environment from the dropdown.

  • Domain Controller: Automatically populated based on the selected environment.

  • System ID: Automatically populated based on the environment.

  • GCTS Repo: Select the source repository.

  • Branch: Choose the source branch to be compared or merged.

Target Configuration:

  • GCTS Environment: Select the target environment from the dropdown.

  • Domain Controller: Automatically populated based on the selected environment.

  • System ID: Automatically populated based on the environment.

  • GCTS Repo: Automatically populated based on the source repository selection.

  • Branch: Choose the target branch into which changes will be merged.

  • Once all required fields are filled, click Save. A success message will be displayed confirming that the configuration has been created successfully..

Executing the Merge

To initiate the merge process:

  1. Click on the Actions button (...) next to the desired merge configuration.

  2. Select Start Merge to begin the merge process based on the defined configuration.

Viewing Merge Configuration Details

By clicking into an existing merge configuration, you can view the following details:

  • Source System ID

  • Target System ID

  • Source Branch

  • Target Branch

  • Created By

  • Created On

  • Merge Status

Viewing Merged Files

To inspect the files involved in the merge:

  1. Click on the Actions button (...) for the configuration.

  2. Select View Files.

  1. This will redirect you to the corresponding GitHub repository, where you can review the status of the merged files.