Before running the build scan and tests, you need to create a session ID. The session ID is provided to for each step in order to link them together as one complete cycle.Download a token from the SeaLights dashboard and place the sltoken.txt file in the working directory

...

Generating

...

a

...

session ID

...

The Build Session is used to uniquely identify a build of your application and to associate test coverage (i.e. all test stages and tests) with that build

Code Block
language bash
sl-python./slcli config create-bsid --appname myAppapp <your-app-name> --branchnamebranch master <your-branch-buildname 1name> --exclude "*venv*" [--workspacepath /path/to/app]

Using the session ID

The session ID will be printed to the console output and a file called 'buildSessionId.txt' 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.

Copying token to environment variable

Unix:
export SL_BUILD_SESSION_ID=`cat buildSessionId.txt`

Windows:
set /p SL_BUILD_SESSION_ID=<buildSessionId.txtbuild <your-build-number>