Corporte Gadfly

@deblaci 👍 Thanks for the kind words. You can increase verbosity by running `gradle` with INFO logging level on the command line: ``` ./gradlew test --info ``` Does that make...

I found another implementation of testing via `jenkins-spock` and `gradle` in [sdp-libraries](https://github.com/boozallen/sdp-libraries/).

Perhaps @ernestojeda could chime in on his [experience](https://github.com/edgexfoundry/edgex-global-pipelines) using `jenkins-spock` and `gradle` as well.

@shadycuz Hard to comment without looking at a minimal, but complete, example. If your `build.gradle` is identical to the ones from my [pull request](https://github.com/corporate-gadfly/jenkins-spock), then, typically, the `setup()` looks like:...

gradle version upped to 6.6.1 in #67.

Thanks for the comment @mlasevich . In all of the sample projects, I have a section as follows: ``` testImplementation 'org.jenkins-ci.main:jenkins-core:2.190.2', { exclude group: 'com.ibm.icu', module: 'icu4j' } ``` Hope...

I appreciate your comments @ernestojeda and @mlasevich . From my experience, with gradle 6.6.1: ``` ./gradlew --version ------------------------------------------------------------ Gradle 6.6.1 ------------------------------------------------------------ Build time: 2020-08-25 16:29:12 UTC Revision: f2d1fb54a951d8b11d25748e4711bec8d128d7e3 Kotlin: 1.3.72...

gradle version bump to 6.7 in #67 .

Not sure if your schedule has eased up or if you have had a chance to further pursue this pull request.

@reinholdfuereder : I could never get the Gradle tests to work in IntelliJ, so I cheated and *manually* created jUnit tests