> For the complete documentation index, see [llms.txt](https://sealights-docs.tricentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sealights-docs.tricentis.com/sealights-agents-and-plugins/abap-agent/command-line-interface/monitor-your-pipeline-for-build-modifications.md).

# 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.

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

<figure><img src="/files/9qW8rFJogrRwaDlW9bB9" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="/files/PUnXmkODbOTSSvqONx5Z" alt=""><figcaption></figcaption></figure>

The Coverage Report hierarchy has the following structure:

```
App
	<Development Class/Package>
		<Object Type>
			<Object Name>
				{} <Component Type> <Component Name>
				…
			…
		…
	…
```

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

<figure><img src="/files/obJETbiZL6ni6Xgk3qEQ" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
When you stop or replace a buildmods task, the agent automatically terminates any running watcher process for that task. Orphaned watcher processes are no longer possible.
{% endhint %}

### 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 — e.g. an INIT\_BUILD\_MAP task is still running when BUILD\_MODS starts, or vice versa. |

### 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 <a href="#toc201668102" id="toc201668102"></a>

To stop monitoring a Pipeline for Build Modifications, run the following from your terminal:

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Command" overflow="wrap" %}

```batch
slabapcli.exe buildmods stop --pipeline "HH_SLABAPCLI_170625"
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Command" overflow="wrap" %}

```powershell
.\slabapcli.exe buildmods stop --pipeline 'HH_SLABAPCLI_170625'
```

{% endcode %}
{% endtab %}
{% endtabs %}

{% code title="Expected output (PowerShell)" overflow="wrap" lineNumbers="true" %}

```log
.\slabapcli.exe buildmods stop --pipeline 'HH_SLABAPCLI_170625'
[2025-06-18 14:45:19.637+01:00] [info] Current ANSI Code Page: 65001 (UTF-8) (65001)
[2025-06-18 14:45:19.638+01:00] [info] Config pathname: ../config/config.toml
[2025-06-18 14:45:19.652+01:00] [info] Stopped buildmods run
[2025-06-18 14:45:19.652+01:00] [info] Total time: 00:00:00.015
```

{% endcode %}