| Table of Contents |
|---|
...
- To report the Pull Request data to SeaLights, the Task Runner must be installed locally on a machine with network access to the BitBucket server:
- Download the Task Runner from the following link: https://sl-repoagents.s3sealights.amazonaws.comco/sl_task_runner/sl_task_runner-24.10.13682397.zip
- Prepare a configuration file to be used by the Task Runner in JSON format:
The Bitbucket server properties in this configuration file should be defined within json property "
bitbucketServer" as follows:The token to be used should be an Agent token
...
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
java -jar sl-build-scanner.jar -prConfig -appname "MyApp" -latestCommit $BITBUCKET_COMMIT -pullRequestNumber $BITBUCKET_PR_ID -repoUrl $BITBUCKET_REPO_SLUG -targetBranch origin/$BITBUCKET_PR_DESTINATION_BRANCH -tokenfile sl_acc_token.txt -pi "*co.sealights.sample.*" |
| Note |
|---|
The For Java applications, 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
...