Generating a session ID

Before running the build scan and tests, create a session ID. Pass the same ID to each step so SeaLights links them as one complete cycle.

See 'Generating an Agent token' for instructions on how to generate a token.

Generating a session ID in Node.js

Use config to open the build session and write buildSessionId.

BUILD_NAME="$(date -u +"%Y%m%d_%H%M%S")"

npx slnodejs config \
  --tokenFile ./sltoken.txt \
  --appName "myApp" \
  --branchName "main" \
  --buildName "$BUILD_NAME"

- name: Generate SeaLights Build Session ID
  env:
    SL_TOKEN: ${{ secrets.SL_TOKEN }}
  run: |
    npx slnodejs config \
      --token "$SL_TOKEN" \
      --appName "${{ github.event.repository.name }}" \
      --branchName "${{ github.ref_name }}" \
      --buildName "${{ github.run_id }}"

- script: |
    npx slnodejs config \
      --token "$(SL_TOKEN)" \
      --appName "$(Build.Repository.Name)" \
      --branchName "$(Build.SourceBranchName)" \
      --buildName "$(Build.BuildId)"
  displayName: Generate SeaLights Build Session ID

Each successful call creates the data structures for this build.

The appName / branchName / buildName trio must be unique on every run.

Locally, use a timestamp for buildName.

In CI, use the platform run ID or build ID.

The most common cause of the "Module already exists" error is reusing the same buildName.

See NodeJS Agent — Command Reference for the full parameter details.

Using the session ID

The command prints the session ID and writes it to buildSessionId. Reuse that file in later agent commands, or export it as an environment variable.

export SL_BUILD_SESSION_ID=$(cat buildSessionId)

PreviousDownloading the Node.js Agent NextScanning Your Application

Last updated 23 days ago

Was this helpful?