Ctrlk
Contact SupportProduct
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Create & List Pipelines

Create a Pipeline

A Pipeline identifies a QAS (or DEV) and Production system in your SAP landscape, and links them to a SeaLights application.

slabapcli pipeline set

Creates a pipeline that links a QAS (or DEV) and Production system in your SAP landscape to a SeaLights application.

Syntax (QAS and PRD systems)
slabapcli.exe pipeline set --appname <app> --qas <rfc> --prd <rfc> [--name <name>] [--labid <labid>]
Syntax (DEV and PRD systems)
slabapcli.exe pipeline set --appname <app> --dev <rfc> --prd <rfc> [--name <name>] [--labid <labid>]
Syntax (QAS and PRD systems)
.\slabapcli.exe pipeline set --appname <app> --qas <rfc> --prd <rfc> [--name <name>] [--labid <labid>]
Syntax (DEV and PRD systems)
.\slabapcli.exe pipeline set --appname <app> --dev <rfc> --prd <rfc> [--name <name>] [--labid <labid>]
Parameter
Short flag
Required
Description

--appname

-a

Yes

The SeaLights application name to associate with this pipeline.

--qas

-q

One of --qas or --dev

The QAS RFC Destination name.

--dev

-d

One of --qas or --dev

The DEV RFC Destination name. Use this instead of --qas when your source system is a DEV system. The key is stored as dev in the config file and is not normalized to qas.

--prd

-p

Yes

The PRD RFC Destination name.

--name

-n

No

A custom name for the pipeline. If omitted, the name is auto-generated as <appname>-<qas> (for example, myapp-S21). Allowed characters: A-Za-z0-9._-

--labid

—

No

Leave unset so the agent derives the lab ID automatically as <QAS SID> <QAS RFC hostname> (for example, S21 vwsvtstsap13.tricentis.com). Do not set this unless you have a specific reason to override.

Leave --labid unset when you create a pipeline. The agent derives the lab ID automatically so it matches the QAS branch name: "<SID> <ashost>" (for example, S21 vwsvtstsap13.tricentis.com).

Overriding --labid casually breaks Test Cycles in SeaLights.

The auto-derived lab ID is what SeaLights uses for Test Cycles and Footprints. Only override --labid when you deliberately need a different lab ID and understand the Test Cycle impact.

Multiple pipelines can share the same --appname. Each pipeline's name must be unique — the auto-generated name (appname-qas) ensures this when pipelines use different QAS systems.

Example: Create a pipeline using a QAS system

If a pipeline with the same name already exists, the command updates it and prints has been updated instead of has been created.

This writes the following entry to config.toml:

Example: Create a pipeline using a DEV system

This writes the following entry to config.toml. Note that the key is stored as dev, not qas:

List Pipelines

To list the Pipelines defined in your config.toml file, run the following from your PowerShell window:

slabapcli pipeline list

Lists all pipelines defined in your config.toml file. The pipeline name is the identifier you use when running buildmap, buildmods, and footprints commands.

This command takes no parameters.

Example

PreviousUpload usage data to an RFC DestinationNextConfigure Test Repositories

Last updated

Was this helpful?