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. To see the full syntax, run the following from your PowerShell window:

Command

.\slabapcli.exe pipeline help

Expected output

C:\apps\SLABAPAgent\bin>slabapcli pipeline help
[2026-03-08 10:58:04.643+02:00] [info] Detected Windows version: Windows 11
[2026-03-08 10:58:04.643+02:00] [info] Config pathname: ../config/config.toml
pipeline <command> [args]:
commands:
  help : setup command help
  list : list pipelines
  set  : set pipeline
    --appname <sealights application name>
    --qas <qas rfc destination name> | --dev <dev rfc destination name>
                                      (exactly one of --qas or --dev)
    --prd <prd rfc destination name>
    [--name <pipeline name override>]  (default: appname-qas)
                                       (allowed chars: A-Za-z0-9._-)
    [--labid <lab ID>]                 (default: "<qas SID> <qas rfc hostname>")

Parameters

Parameter	Required	Description
--appname	Yes	The SeaLights application name to associate with this pipeline.
--qas	One of --qas or --dev	The QAS RFC Destination name.
--dev	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	Yes	The PRD RFC Destination name.
--name	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	The lab ID for this pipeline. If omitted, it is auto-generated as <QAS SID> <QAS RFC hostname> (for example, S21 vwsvtstsap13.tricentis.com).

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

Command

.\slabapcli.exe pipeline set --appname ALM_Demo --qas S21 --prd S23

Expected output

C:\apps\SLABAPAgent\bin>slabapcli pipeline set --appname ALM_Demo --qas S21 --prd S23
[2026-03-08 10:33:36.956+02:00] [info] Detected Windows version: Windows 11
[2026-03-08 10:33:36.957+02:00] [info] Config pathname: ../config/config.toml

This writes the following entry to config.toml:

config.toml

[[pipeline]]
  name = "ALM_Demo-S21"
  appname = "ALM_Demo"
  qas = "S21"
  prd = "S23"
  labid = "S21 vwsvtstsap13.tricentis.com"
  disablesetref = false

Example: Create a pipeline using a DEV system

Command

.\slabapcli.exe pipeline set --appname ALM_Demo --dev S21 --prd S23

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

config.toml

[[pipeline]]
  name = "ALM_Demo-S21"
  appname = "ALM_Demo"
  dev = "S21"
  prd = "S23"
  labid = "S21 vwsvtstsap13.tricentis.com"
  disablesetref = false

List Pipelines

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

Command

.\slabapcli.exe pipeline list

Expected output

C:\apps\SLABAPAgent\bin>slabapcli pipeline list
[2026-03-08 10:58:38.376+02:00] [info] Detected Windows version: Windows 11
[2026-03-08 10:58:38.377+02:00] [info] Config pathname: ../config/config.toml
appname       : ALM_Demo
name          : ALM_Demo-S21
qas           : S21
prd           : S23
labid         : S21 vwsvtstsap13.tricentis.com
disablesetref : false
Use the pipeline name 'ALM_Demo-S21' with the buildmap, footprints, and buildmods commands.

appname       : ALM_Demo
name          : ALM_Demo-S23
qas           : S23
prd           : S23
labid         : S23 vlsvprdsap02.tricentis.com
disablesetref : false
Use the pipeline name 'ALM_Demo-S23' with the buildmap, footprints, and buildmods commands.

The pipeline name is the identifier you use when running buildmap, buildmods, and footprints commands.