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.
Download a token from the SeaLights dashboard and place the sltoken.txt file in the working directory
See 'Generating an agent token' for instructions on how to generate a token
Our Node.js agents ( For Customers that need to set a specific recommended agent version other than the default latest, the API will provide the recommended agent version that has been set on the dedicated settings page from the dashboard. In the following examples, replace Linux PowerShell GitLab YMLAgent File
slnodejs
) are published in the npm registry. You download it and all its dependencies using the npm
repository commands.Downloading latest version
npm i slnodejs
Downloading the recommended version by Sealights (Best Practice)
$DOMAIN
with your domain and $SL_TOKEN
with your SeaLights agent token# Fetch Agent version defined in Sealights dashboard settings
$SLVERSION=$(curl -X GET "https://$DOMAIN.sealights.co/api/v2/agents/slnodejs/recommended" -H "accept: application/json" -H "Authorization: Bearer $SL_TOKEN" -L)
# Install Sealights Agent (Recommended version)
npm i slnodejs@$SLVERSION
# Fetch Agent version defined in Sealights dashboard settings
$SLVERSION = Invoke-RestMethod -Uri "https://$DOMAIN.sealights.co/api/v2/agents/slnodejs/recommended" -Headers @{ "accept" = "application/json", "Authorization" = "Bearer $SL_TOKEN"}
# Install Sealights Agent (Recommended version)
npm i "slnodejs@$SLVERSION"
before_script:
- apt-get -qq update && apt-get install -y jq
script:
- |
SLVERSION=$(curl -X GET "https://$DOMAIN.sealights.co/api/v2/agents/slnodejs/recommended" -H "accept: application/json" -H "Authorization: Bearer $SL_TOKEN" -L | jq -r .agent.version )
npm install slnodejs@$SLVERSION
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
sl-python config config --appname myApp --branchname master --buildname 1 --exclude "*venv*"
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.
Unix: export SL_BUILD_SESSION_ID=`cat buildSessionId.txt` Windows: set /p SL_BUILD_SESSION_ID=<buildSessionId.txt