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
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
...
Generating a session ID in Node.js is done using the SeaLights Node.js Agent with the config flag
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
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" |
| Info |
|---|
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.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
Unix: export SL_BUILD_SESSION_ID=`cat buildSessionId` Windows: set /p SL_BUILD_SESSION_ID=<buildSessionId |