Table of Contents

Parameter	Description
`token`	Access token generated from the SeaLights server
`tokenfile`	Path to file containing access token generated from the SeaLights server
`buildsessionid`	Session ID of configuration created
`buildsessionidfile`	Path to file containing the Session ID of configuration created
`workspacepath`	Path to the source workspace
`excludedpaths`	Comma-separated list of files to exclude from scan Supports wildcards (* = any string, ? = any character). For example: `'-with-dependencies.jar , bad-bad?.war, -source.jar'`
`projectRoot`	Path to the root of the project. Usually where the src folder resides
`uniqueModuleId`	Unique name when providing more than one build scan per build
`es6Modules`	Indicates that you use es6 modules
`jobName`	Name of Jenkins job
`logsUrl`	Path to Jenkins log folder
`scm`	Source control used. Current options are: `git`, `none`
`dependenciesFile`	A path to a JSON file that is in the following format: `[{"appName":"","branch":"","build":""}, {...}]`
`instrumentForBrowsers`	Instrument the JS files for providing browser front-end coverage information. Must be used with the `outputpath` parameter.
`downloadAgent`	Set this value to '`false`' in order to prevent the instrumented javascript to try and download the browser test listener (for example, when using 'Karma').
`instrumentationOnly`	Only instrument the javascript files, without sending the build information to the SeaLights server
`outputpath`	Folder to generate the instrumented JS files in when using the `instrumentForBrowsers` parameter
`labid`	Unique ID for a set of test labs in case multiple labs are running simultaneously or for an integration build. This needs to be done during the instrumentation process when using the `instrumentForBrowsers` option
`proxy`	Address of proxy to run connection through
`failbuild`	Exit with an error code if an error is encountered (Default: `false`)
`scmProvider`	The provider name of your Source Control Management (SCM) tool. Values: Github, Bitbucket and Gitlab (Default is `Github`)
`scmBaseUrl`	The URL to the repository which contains the code. If not provided, the URL of the remote GIT origin will be used Example: `https://my.bitbucket.com/projects/ABCD/repos/XYZ/browse/A1`
`scmVersion`	The version of your Source Control Management (SCM) tool. If not provided, Cloud version is assumed
`babylonPlugins`	Values: `decorators-legacy` - When there are decorators in the code, you should use this flag with the "decorators-legacy" value `jsx` - For React applications

Ending a multi module build

...

Parameter	Description
`token`	Access token generated from the SeaLights server
`tokenfile`	Path to file containing access token generated from the SeaLights server
`buildsessionid`	Session ID of configuration created
`buildsessionidfile`	Path to file containing the Session ID of configuration created
`componentIds`	One or several build session ID's (comma separated) of the component(s) to be updated or deleted
`componentFile`	A path to a JSON file that is in the following format: `[{"appName":"","branch":"","build":""}, {...}]` or `[{"buildSessionId":"", {...}]`
`proxy`	Address of proxy to run connection through

...

Code Block
./node_modules/.bin/slnodejs end {--token <token> \| --tokenfile <file>} {--buildsessionid <id> \| --buildsessionidfile <file>} [--labid <labid>] [--proxy <proxy>] [--failbuild {true\|false}]

Info

ex. command:

./node_modules/.bin/slnodejs run --tokenfile ./sltoken.txt --buildsessionidfile buildSessionId --labid "LAB_ID_2" --workspacepath "./server" --useinitialcolor true --useslnode2 -- "./server/app.js"

Note the /your/backend/server/command refers to "./server/app.js" in the above example.

Parameter	Description
`token`	Access token generated from the SeaLights server
`tokenfile`	Parameter	Description
`token`	Access token generated from the SeaLights server
`tokenfile`	Path to file containing access token generated from the SeaLights server
`buildsessionid`	Session ID of configuration created
`buildsessionidfile`	Path to file containing the Session ID of configuration created
`labid`	Unique ID for a set of test labs in case multiple labs are running simultaneously
`proxy`	Address of proxy to run connection through
`failbuild`	Exit with an error code if an error is encountered (Default: false)

...

Code Block

./node_modules/.bin/slnodejs run {--token  <token> | --tokenfile <file>} {--buildsessionid <id> | --buildsessionidfile <file>} [--workspacepath <path>] [--useinitialcolor {true|false}] [--teststage <teststage>] [--labid <labid>] [--proxy <proxy>] [--useinitialcolorfailbuild {true|false}] [--teststage <teststage>] [--labid <labid>] [--proxy <proxy>] [--failbuild {true|false}] args..args...

Info

Example of command:

./node_modules/.bin/slnodejs run --tokenfile ./sltoken.txt --buildsessionidfile buildSessionId --labid "LAB_ID_2" --workspacepath "./server" --useinitialcolor true --useslnode2 -- "./server/app.js"

Note the /your/backend/server/command refers to "./server/app.js" in the above example.

Parameter	Description
`token`	Access token generated from the SeaLights server
`tokenfile`	Path to file containing access token generated from the SeaLights server
`buildsessionid`	Session ID of configuration created
`buildsessionidfile`	Path to file containing the Session ID of configuration created
`workspacepath`	Path to the source workspace
`useinitialcolor`	When reporting tests manually this should be set to false (Default: false)
`teststage`	Name of the test stage
`labid`	Unique ID for a set of test labs in case multiple labs are running simultaneously
`proxy`	Address of proxy to run connection through
`failbuild`	Exit with an error code if an error is encountered (Default: false)
`args...`	Extra arguments for running mocha framework tests

...

Versions Compared

Old Version 64

New Version 65

Key

Ending a multi module build

Page Comparison

Versions Compared

Old Version 64

New Version 65

Key

Ending a multi module build