Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagebash
java -jar sl-build-scanner.jar -config -tokenfile /path/to/sltoken.txt -appname "IntegrationBuildName" -branchname "master" -buildname "1" -pi "*integration.build*" -buildSessionidfilebuildsessionidfile integrationBSID.txt

Nodejs Agent

Unix

Code Block
languagepowershell
./node_modules/.bin/slnodejs config --tokenfile /path/to/sltoken.txt --appname "IntegrationBuildName" --branch "master" --build "1"
mv buildSessionId integrationBSID.txt

Windows

Code Block
languagepowershell
call .\node_modules\.bin\slnodejs config --tokenfile \path\to\sltoken.txt --appname "IntegrationBuildName" --branch "master" --build "1"
ren buildSessionId integrationBSID.txt

Please notice that for clarity, we have changed the default file name of the Build Session ID to integrationBSID.txt (instead of default buildSessionId.txt in Java or buildSessionId in slnodejs)

...

Create a dependencies file using one of the formats available below. You can name this file sl-integration-components.json for example.

Using the app/branch/build format for every component

Using the buildSessionId format for every component

Code Block
languagejson
[
	{
		"appName": "sl-sample-backend",
		"branch": "master",
		"build": "1.0.1_233"
	},
	{
		"appName": "sl-sample-frontend",
		"branch": "master",
		"build": "1.2.2_44"
	}
]
Code Block
languagejson
[
	{
		"buildSessionId": "123456789"
	},
	{
		"buildSessionId": "abcdefghi"
	}
]

Note

The components listed in the dependencies file must be referring to builds already reported to Sealights (including the Build Scan step) using exact same appName/branchName/buildName parameters reported.

...

Code Block
languagebash
java -jar sl-build-scanner.jar -scan -tokenfile sltoken.txt -buildsessionidfile integrationBSID.txt -componentfile sl-integration-components.json

Nodejs Agent

Unix

Code Block
languagepowershell
./node_modules/.bin/slnodejs build --tokenfile sltoken.txt --buildsessionidfile integrationBSID.txt --dependenciesFile sl-integration-components.json

Windows

Code Block
languagepowershell
call .\node_modules\.bin\slnodejs build --tokenfile sltoken.txt --buildsessionidfile integrationBSID.txt --dependenciesFile sl-integration-components.json

Once this has run, all components listed in the dependencies file will be added to the newly created integration build.

...