Using Node.js Agent - Generating a session ID

Before running the build scan and tests, you need to create a session ID. The session ID is provided to each step in order link them together as one complete cycle

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

Agent File

Our Node.js agents are published in the npm registry. You download it and all its dependencies using the npm repository commands, for example:

Unix:
npm i slnodejs

Windows:
call npm i slnodejs

BASH

Generating a session ID in Node.js

Generating a session ID in Node.js is done using the SeaLights Node.js Agent with the config flag

Unix:
./node_modules/.bin/slnodejs config --tokenfile /path/to/sltoken.txt --appname "myApp" --branch "master" --build "1"

Windows:
call .\node_modules\.bin\slnodejs config --tokenfile \path\to\sltoken.txt --appname "myApp" --branch "master" --build "1"

BASH

You can provide a timestamp for the buildname parameter --build `date +"%y%m%d_%H%M"` (Linux) or --build (Get-Date $date -Format "yyyMMdd_HHmm") (Windows Powershell)

See 'Node.js Command Reference - Creating a session ID' for full parameter details

Using the session ID

The session ID will be printed to the console output and a file called 'buildSessionId' will be generated containing it. The file can be used as is in the agent parameters or can be used to fill in an environment parameter to be in a command line.

Unix:
export SL_BUILD_SESSION_ID=`cat buildSessionId`

Windows:
set /p SL_BUILD_SESSION_ID=<buildSessionId

TEXT