Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
printablefalse

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.

Note

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

...

Note
  • 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

...

The Gradle plugin downloads the recommended agent at the beginning of the run. If you want to pre-download them and provide them to the plugin, you can do so with the flags scannerJar & listenerJarflags scannerJarlistenerJar.

Info

The agents referred here should be downloaded either with the latest agent or the recommended one as stated in Downloading the java agent files and made available prior to the Gradle execution.

Code Block
"scannerJar": "./sl-build-scanner.jar"
"listenerJar": "./sl-test-listener.jar"

...

Sample shell script 

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

...

Page Properties
hiddentrue


Related issues