[1/3] kudu git commit: [build] Fix build jar verification

Repository: kudu Updated Branches: refs/heads/master 264b5b20f -> be360bf01 [build] Fix build jar verification - Adjusts the verify_jars.pl script to ignore jars in build/jars path. This is where all the dependency jars are staged for dist-tests. They are not included in the distribution. -

[3/3] kudu git commit: Add support for Java dist-tests on Jenkins

Add support for Java dist-tests on Jenkins Enables running the Java dist-tests on Jenkins when ENABLE_DIST_TEST=1 and BUILD_GRADLE=1. It requires BUILD_GRADLE=1 because the Maven build doesn’t support dist-tests. Change-Id: I20105d3f12fd8c3f95d9fe30fe1b63138614041a Reviewed-on:

[2/3] kudu git commit: TestSecurity: remove errant Precondition

TestSecurity: remove errant Precondition Its presence makes it impossible to retry the tests in this class. An alternative would be to null out miniCluster in tearDown(), but I don't think that should be necessary for creating a new cluster. Change-Id: I0ba826d3ec722cb20b35d4c34817d30ab9782976

kudu git commit: authz: clear up some role terminology

Repository: kudu Updated Branches: refs/heads/master 2c572cbd4 -> 264b5b20f authz: clear up some role terminology The service user was being referred to as "ServiceUser" in the tserver and "Service" in the master. I found this confusing so I renamed it, and did a little extra cleanup while I

kudu git commit: Add unstable client APIs to fetch HMS integration configuration status

Repository: kudu Updated Branches: refs/heads/master a8d088e11 -> 2c572cbd4 Add unstable client APIs to fetch HMS integration configuration status The Impala/Kudu integration must know whether the Kudu cluster is configured with the HMS integration enabled. This commit adds an unstable API to

kudu git commit: [build] Move default sanitizer options into build from shell scripts

Repository: kudu Updated Branches: refs/heads/master d3ef58b71 -> a8d088e11 [build] Move default sanitizer options into build from shell scripts This moves the sanitizer options and suppressions from the build scripts using TSAN_OPTIONS/LSAN_OPTIONS/etc into the build and linked at build

kudu-site git commit: Publish commit(s) from site source repo: e86c4bda6 [site] Replace checksum links to sha512 in releases 96ecb8ed9 [site] KUDU-1951 Exclude dirs from site_tool proof

Repository: kudu-site Updated Branches: refs/heads/asf-site b1cb26053 -> 23296c046 Publish commit(s) from site source repo: e86c4bda6 [site] Replace checksum links to sha512 in releases 96ecb8ed9 [site] KUDU-1951 Exclude dirs from site_tool proof Site-Repo-Commit:

[3/3] kudu git commit: [cmake] add OpenSSL include path into -isystem

[cmake] add OpenSSL include path into -isystem Prior to this change, when OpenSSL package is installed under the same prefix as boost package (e.g. /opt/local on OS X if using MacPorts), running cmake will choose the thirdparty-built boost, but due to the intermix of '-isystem' and '-I' options,

kudu git commit: [site] Replace checksum links to sha512 in releases

Repository: kudu Updated Branches: refs/heads/gh-pages 96ecb8ed9 -> e86c4bda6 [site] Replace checksum links to sha512 in releases Change-Id: Ie1d679eb9af6955b666493c3f49d43cf71848474 Reviewed-on: http://gerrit.cloudera.org:8080/11294 Reviewed-by: Grant Henke Tested-by: Grant Henke