...
Code Block | ||
---|---|---|
| ||
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 |
| |||||
---|---|---|---|---|---|---|
Windows |
|
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 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
|
|
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 | ||
---|---|---|
| ||
java -jar sl-build-scanner.jar -scan -tokenfile sltoken.txt -buildsessionidfile integrationBSID.txt -componentfile sl-integration-components.json |
Nodejs Agent
Unix |
| |||||
---|---|---|---|---|---|---|
Windows |
|
Once this has run, all components listed in the dependencies file will be added to the newly created integration build.
...