Skip to main content
Version: 1.1.0

Visual Pipeline

You can configure pipelines visually. First, select the visual pipeline and corresponding branch:

vis_workflow1

Basic Information​

You can edit the pipeline's name and description.

Pipeline names must be unique within the same repository.

vis_workflow2

Triggers​

Note: When orchestrating the pipeline, triggers should be placed before the start node; currently, only one trigger is supported per pipeline.

  • Cron Trigger: You can set specific trigger times by filling in cron expressions vis_workflow2

  • GitLink_Webhook Event Trigger: Provides common code change event triggers, including push code, pull requests, and create tags vis_workflow3

Global Parameters​

Once added, these can be used throughout the current pipeline

vis_workflow4

Usage Example

vis_workflow5

Concurrent Execution​

vis_workflow6

When enabled, the same pipeline can execute n pipeline instances simultaneously (each trigger creates one pipeline instance);

vis_workflow7

If not enabled, while the current pipeline instance is executing, subsequent instances will be in a queued state (maximum 5 instances can be queued). The next instance begins execution after the current instance completes.

vis_workflow8

Pipeline Orchestration​

Each pipeline must have one start node, one end node, and at least one task node. Both serial and parallel orchestration are supported.