SeaLights build scanner (sl-build-scanner.jar) can be used to update build.gradle script with the changes needed to run your Gradle build using SeaLights Gradle plugin in a similar fashion as for Maven pom integration.

Automatic integration of Sealights settings into your build.gradle script is currently supported only for Groovy language.
If your script is written in Kotlin, please use the method described in the following article: Gradle - Scanning Builds and Tests using Sealights plugin

Configuration file

Create a JSON configuration file with the following parameters in order to provide the necessary configuration fields to the SeaLights Gradle plugin:

token or tokenFile - set with a token or a file containing the token obtained from the SeaLights dashboard
If you create a Build Session ID externally, provide the following fields:
1. buildSessionId or buildSessionIdFile - Set with a build session id or a file containing the build session id created by the config step
2. createBuildSessionId - Set to false
If you want to create a Build Session ID using the SeaLights Gradle plugin, provide the following fields:
1. createBuildSessionId - Set to true
2. appName - Name of the application as you want to see it on the SeaLights dashboard
3. branchName - Name of the branch as you want to see it on the SeaLights dashboard
4. buildName - Name of the build as you want to see it on the SeaLights dashboard
5. packagesIncluded - Comma-separated list of packages to include in scan. Note: This is defining a subset, so it must include the astrix to include all sub packages/classes
executionType - Provide which executions need to handled by the Gradle plugin
1. full - Execute both the build scanner and the test listener
2. testsonly - Execute only the test listener
filesincluded - (Optional) Set to the binary files to scan. Default: *.class
filesexcluded - (Optional) Set to the binary files to excluded from the scan. Default: *test-classes*
workspacepath - Set to the path to the binary files to scan. Default: project.buildDir
recursive - (Optional) Set to true to scan all the subdirectories of workspacepath. Default: true
includeResources - (Optional) Set to include the token and build session ID files in the built resources
testTasksAndStages - (Optional) Mapping of test tasks’s names to test stage names as they will be displayed on the SeaLights dashboard. It should be of the format {"testTask1":"testStage1", "testTask2":"testStage2"}
labId - (Optional) Unique ID for a set of test labs in case multiple labs are running simultaneously
filesStorage - Set to the temp folder for the agent to create temporary files in. For example /tmp
logEnabled - Set to true if you want a log to be created
logLevel - Set the log level to create. For example WARN or INFO
proxy - (Optional) Address of proxy to run connection through
sealightsJvmParams - Entry to provide JVM params to the SeaLights agent. It should be of the format {"key1":"val1", "key2":"val2"}

The values provided for fields can contain interpolated Groovy code, just like for the field appName in the above example: "${System.getenv('JOB_NAME')}" .
It will get resolved during the Gradle build.

Do not call the JSON file 'sealights.json' as the agent uses this file name for override options
For troubleshooting purpose, you can use "buildName":"SL_Timestamp" in your JSON file to have the Sealights Gplugin generating automatically a time stamp (yyyy.MM.dd-hh.mm format) as a default buildname

See 'Java Command Reference - Installing test listener as Java Agent' for more parameter values and information

{
  "tokenFile": "sltoken.txt",
  "createBuildSessionId": true,
  "appName": "${System.getenv('JOB_NAME')}",
  "branchName": "master",
  "buildName": "${System.getenv('BUILD_NUMBER')}",
  "packagesIncluded": "*com.example.*",
  "packagesExcluded": "",
  "filesIncluded": "*.class",
  "filesExcluded": "*test-classes*",
  "recursive": true,
  "includeResources": true,
  "testTasksAndStages": {"test":"Unit Tests", "junitPlatformTest":"Unit Tests", "integrationTest":"Integration Tests"},
  "labId": null,
  "executionType": "full",
  "logEnabled": false,
  "logDestination": "console",
  "logLevel": "off",
  "logFolder": "/tmp",
  "gradleProjectConfig": {
    "excludedProjects": ["subProject1", "subProject2"],
    "repoConfig": "mavenLocal()"
  }
}

Integrating into the Build.gradle script

Before running your Gradle build, you run the build scanner with -gradle flag to integrate the SeaLights Gradle plugin into the build.gradle file. This will create a sealights.gradle script with all the configuration taken from the JSON config file and append a reference to it in build.gradle.

The standard parameters the build scanner receives are:

configfile - The path to the JSON configuration you created with the parameters to be provided to the SeaLights Gradle plugin
workspacepath - The base path to the location of the build.gradle file to update

java -jar sl-build-scanner.jar -gradle -configfile sl-config.json -workspacepath .

At the successful completion of the command, you’ll see the following last line in the console:
[Sealights Build Scanner] - Successfully finished SeaLights integration.

This step will update the root build.gradle file and back it up to build.gradle.slbackcopie in the same directory
If your workspace is not reset for each build, you will need to restore them at the end of the run (see command below).

Next step is to run your regular Gradle build command, e.g. gradle clean build.

Restoring the build.gradle file to its previous state

In case the project is to be restored to its previous state before the SeaLights plugin was applied, use the build scanner with the -restoreGradle flag on the workspace where the gradle.build file is located:

java -jar sl-build-scanner.jar -restoreGradle -workspacepath .

This command will (1) restore gradle.build from backup, (2) delete the backup file, and (3) delete the sealights.gradle file.
Failure at any of these steps won’t prevent the next ones, so that the project is restored as much as possible.

Configuring SCM for Build Scan

SeaLights by default provides all links to the SCM for Github. You can configure SeaLights to prepare the links for Bitbucket and Gitlab as well with the following parameters placed under the sealightsJvmParams section:

sl.scm.provider - set to github, Bitbucket or gitlab
sl.scm.baseUrl - When working with an on-premise installation of your SCM and access from the build machine is different than the one accessed by the users, then you can provide the base URL to use
sl.scm.version - set to the version of the on-premise version you use

"sealightsJvmParams": {
    "sl.scm.provider": "bitbucket",
    "sl.scm.baseUrl": "https://my.bitbucket.com/projects/ABCD/repos/XYZ/browse/A1",
    "sl.scm.version": "4.9.0"
}

Sample shell script

This script is very often added to a new pre-build step in your CI configuration (i.e. Jenkins).

echo "Downloading Sealights Agents..."
wget -nv https://agents.sealights.co/sealights-java/sealights-java-latest.zip
unzip -o sealights-java-latest.zip
echo "Sealights agent version used is:" `cat sealights-java-version.txt`

echo  '{ 
    "tokenFile": "sltoken.txt", 
    "createBuildSessionId": true,
    "appName": "${System.getenv(\"JOB_NAME\")}",   
    "branchName": "${System.getenv(\"GIT_BRANCH\")}",
    "buildName": "${System.getenv(\"BUILD_NUMBER\")}",
    "packagesIncluded": "*com.example.*",   
    "packagesExcluded": "",
    "filesIncluded": "*.class",
    "filesExcluded": "*test-classes*",
    "recursive": true,
    "includeResources": true,
    "testTasksAndStages": {"test": "Unit Tests"},
    "labId": null,
    "executionType": "full",
    "logEnabled": false,
    "logDestination": "console",
    "logLevel": "off",
    "logFolder": "/tmp"
  }' > sl-config.json
 
echo "Updating Build.gradle with Sealights..."
java -jar sl-build-scanner.jar -gradle -configfile sl-config.json -workspacepath .