Versions Compared

Key

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

Table of Contents

...

ParameterDescription
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
es-modulesIndicates 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)
scmProviderThe 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 When there are decorators in the code, you should use this flag with the "decorators-legacy" value

...

ParameterDescription 
tokenAccess token generated from the SeaLights server
tokenfilePath to file containing access token generated from the SeaLights server
buildsessionidSession ID of configuration created
buildsessionidfilePath to file containing the Session ID of configuration created
componentIdsOne or several build session ID's (comma separated) of the component(s) to be updated or deleted
componentFileA path to a json file that is in the following format:
[{"appName":"","branch":"","build":""}, {...}]
or
[{"buildSessionId":"", {...}]
proxyAddress of proxy to run connection through

...

ValueDescription
sl
Display log output to the console
sl-file
Export the log information to a log file named 'sl.node.log'

...