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

Monitor your Pipeline for Build Modifications

Monitor your Pipeline for Build Modifications

The next step is to configure the agent to monitor your Pipeline for Build Modifications. The agent creates Build Modifications from changes you make by importing transports into the Pipeline's QAS system.

slabapcli buildmods run

Configures the agent to monitor a pipeline's QAS system for Build Modifications.

Syntax
slabapcli.exe buildmods run --pipeline <pipeline-name>
Syntax
.\slabapcli.exe buildmods run --pipeline <pipeline-name>
Parameter
Required
Description

-p, --pipeline

Yes

The pipeline name (as shown in pipeline list).

Example

Command
slabapcli.exe buildmods run --pipeline "HH_SLABAPCLI_170625"
Command
.\slabapcli.exe buildmods run --pipeline 'HH_SLABAPCLI_170625'
Expected output (PowerShell)
.\slabapcli.exe buildmods run --pipeline 'HH_SLABAPCLI_170625'
[2025-06-18 09:24:49.485+01:00] [info] Current ANSI Code Page: 65001 (UTF-8) (65001)
[2025-06-18 09:24:49.486+01:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
[2025-06-18 09:24:49.516+01:00] [info] Total time: 00:00:00.031

This command creates a BUILD_MODS scheduled task that runs every five minutes to create Build Modifications from transports imported into the pipeline's QAS system.

When you import transports or refresh links (REFRESH_LINKS), pause BUILD_MODS for that window: stop the task → import transports → run refresh and wait until it finishes → start BUILD_MODS again. BUILD_MODS and refresh use the same build-mode lock, so running them together can produce watcher exit code 11 (see Watcher Exit Codes below).

To display the Build Modifications in SeaLights, go to the Coverage Dashboard and open the Build history window for your app.

In the Build column:

  • The Initial Build Map name has the format Initial <QAS system>|<QAS hostname>|<Creation datetime>

  • Build Modifications have the format <Transport name>|<Import datetime>

The Coverage Report's Overall Coverage tab lists all the objects in your SeaLights app.

The Coverage Report hierarchy has the following structure:

The Code Changes tab lists all the code changes introduced by Build Modifications.

Watcher Exit Codes

If the watcher exits with a non-zero code visible in Windows Task Scheduler, use this table to interpret it:

Exit code
Meaning

0

Success.

1

General failure — check the watcher log for details.

10

Another watcher for the same action is already running.

11

Build-mode conflict — INIT_BUILD_MAP, BUILD_MODS, and REFRESH_LINKS are mutually exclusive for the same pipeline; an overlap exits with this code.

Timestamp Behavior

When monitoring picks up a transport, it uses the current (clock-synced) time as the build timestamp. This ensures builds always appear in the correct chronological order in the SeaLights dashboard, even when the transport itself was imported some time ago.

Stop monitoring a Pipeline for Build Modifications

slabapcli buildmods stop

Stops the scheduled BUILD_MODS task for a pipeline.

Parameter
Required
Description

-p, --pipeline

Yes

The pipeline name (as shown in pipeline list).

Example

Last updated

Was this helpful?