Ah, that makes sense, thanks for finding that. We could alternatively use
build/** to avoid everything under build, or include a more complete list
via .gitignore instead (although that would have to be done carefully since
the pattern matching works differently). Unfortunately grgit is required
See https://builds.apache.org/job/KafkaPreCommit/138/changes
Changes:
[junrao] kafka-1367; Broker topic metadata not kept in sync with ZooKeeper;
patched by Ashish Singh; reviewed by Jun Rao
[joe.stein] KAFKA-2304 Supported enabling JMX in Kafka Vagrantfile patch by
Stevo Slavic reviewed by
Is there a way to run the Jenkins build with more detailed output, e.g.
with one of gradle's debug flags? It looks like in the Jenkins environment
the exclude rules (which should be ignoring the build/ directory) aren't
working like they did for me and the reviewers, but there's not enough
useful
Ewen,
We did have at least one successful run (
https://builds.apache.org/job/Kafka-trunk/526/console) after the rat patch.
Perhaps you can file an Apache infra ticket to figure out why other runs
fail?
Thanks,
Jun
On Tue, Jul 7, 2015 at 11:16 AM, Ewen Cheslack-Postava e...@confluent.io
wrote:
You can reproduce the rat failure by running: ./gradlew clean
gradlew test
If you run gradlew test again it does not report any error.
build.gradle uses Grgit to expand the gitignore files to exclude. For
a clean build, the build directory does not exist (yet). So it is not
excluded by rat.
explicitly specify an exclude for build/rat/rat-report.xml
(btw, I went ahead with a trivial commit for the above - let me know
if there are any concerns)
On Tue, Jul 07, 2015 at 09:44:27PM -0700, Joel Koshy wrote:
You can reproduce the rat failure by running: ./gradlew clean
gradlew test
