Table of Contents |
---|
The SeaLights Pull Request Integration exposes Quality Risks to the developer as part of the Pull Request process, to be displayed and handled before the code is merged into the main branch.
...
Code Block | ||||
---|---|---|---|---|
| ||||
java -jar sl-build-scanner.jar -prConfig {-token <arg> | -tokenfile <arg>}tokenfile "./myapp/sltoken.txt" -appname <arg>"MyApp" -targetBranch <arg>"master" -latestCommit <arg>$GIT_PR_COMMIT -pullRequestNumber <arg>123 -repoUrl <arg> [-pi <arg>] [-pe <arg>] |
token
tokenfile
appname
latestCommit
pullRequestNumber
repoUrlÂ
pi, packagesincluded
Comma-separated list of packages to include in scan
Supports wildcards (* = any string, ? = any character). For example: 'com.example.* ,io.*.demo, com.?ello.world'
pe,packagesexcluded
Comma-separated list of packages to exclude from scan
Supports wildcards (* = any string, ? = any character). For example: 'com.example.* ,io.*.demo, com.?ello.world'
proxy
...
https://github.com/mycomp/myapp -pi "*com.company.*" |
Note |
---|
The packages included and excluded should be exactly the same as what was defined to SeaLights for the merged branch so that the compared results will be the same |
Info |
---|
See prConfig - Command Reference ' for full parameter details in Java agent, node agent or via the Sealights Jenkins plugin. |
Pull Request parameters as seen on a Bitbucket page
...