-
Runtime
-
Java 8+
-
-
Build time
-
Java 8+
-
-
Test time
-
Built Kudu Binaries
-
MIT Kerberos (krb5)
-
$ ./gradlew :kudu-client:assemble
The client jar can then be found at kudu-client/build/libs
.
The tests may locate the master and tablet server
binaries by looking in build/latest/bin
from the root of
the git repository. If you have recently built the C++ code
for Kudu, those should be present already.
If for some reason the binaries aren’t in the expected location
as shown above, you can pass
-DkuduBinDir=/path/to/directory
.
Once everything is setup correctly, run:
$ ./gradlew test
If you would like to force tests that were already run to re-run
you can pass -PrerunTests
.
If you would like to run a subset of the tests or a single test
you can pass the Gradle --tests <pattern>
argument to filter
the tests ran.
See here
for detailed documentation of all pattern options.
Single Test Class Example:
$ ./gradlew :kudu-client:test --tests org.apache.kudu.TestColumnSchema
Single Test Method Example:
$ ./gradlew :kudu-client:test --tests org.apache.kudu.TestColumnSchema.testEquals
Pattern Example:
$ ./gradlew test --tests *IT*
$ ./gradlew clean
Note: You generally don’t need to run this task, but it can be useful to rule out any build issues.
./gradlew dependencyUpdates
Note
|
Additional Gradle command line flag options can be found here. |