GCTS Switch Task

The GCTS Switch Task in ReleaseOwl is used to change the branch associated with a system. For example, if a UAT system is currently pointing to the “QA” branch and a hotfix needs to be tested, this task can be used to switch the system to the “Hotfix” branch.

Prerequisites

The required transports must be added in the User Story.

GCTS Switch Task – Flow

Create a Pipeline and add the GCTS_SWITCH_TASK.
- Configure the task with:
  - GCTS Environment
  - GCTS Repo
  - Branch To Switch

Create a User Story.

Attach the pipeline (with the GCTS_SWITCH_TASK) to the user story.
In parallel, add a Transport to the same user story.
Save the user story.

Promote the User Story.

After promotion, the system begins monitoring the switch_status.
- If the switch_status = TIMEOUT, the user story moves to Suspend state with a Refresh icon. You can click this icon to retry the switch.

Upon clicking Refresh, the switch_status may update to SUCCESS or SWITCHED_WITH_WARNINGS.
- In this case, the Continue Deployment option becomes available. Clicking it resumes the process and marks the overall status as Completed.

Scenarios for SWITCHED_WITH_WARNINGS

Case 1: Transport ID Not Found in Logs
- If the GCTS Switch log does not contain a Transport ID, the system sets the switch_status = SWITCHED_WITH_WARNINGS.
Case 2: Transport ID Found but Validation Required
- If a Transport ID is found in the log, the system verifies whether the respective Transport ID is activated; if activated, the switch_status = SUCCESS, otherwise it is set to another status.

Additional Option – Manual Completion (Mark as Complete)

At any point, the user may choose to bypass waiting for the switch to complete by using the Mark as complete in the Manual completion option.
Steps:
1. In Manual Completion, click Mark as Complete.