[
https://issues.apache.org/jira/browse/KAFKA-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599771#comment-14599771
]
Ewen Cheslack-Postava commented on KAFKA-2203:
----------------------------------------------
[~gwenshap] Agreed that precommit is the ideal solution. Not sure that the
setup in KAFKA-1856 works for this though -- can we get all the configurations
we'd want, i.e. does a single jenkins job have access to all the jdk versions
we'd need here?
Also, if the entire test matrix was run, at current rates it'd take something
like 20min * 2 JDK versions (min and max versions, at a minimum) * 4 scala
versions = 2.66 hrs minimum for feedback since I don't think we can parallelize
those unless we spread across multiple jenkins jobs? Or maybe it just requires
a more complex Jenkins job to parameterize? Long turn around time is bad for
submitters too...
For the precommit stuff, if we're switching to Github PRs, we could also
possibly use Travis, which ASF supports in some fashion since they pay for
capacity instead of relying on the "fair use" servers. Not sure how that
integrates with JIRA though.
> Get gradle build to work with Java 8
> ------------------------------------
>
> Key: KAFKA-2203
> URL: https://issues.apache.org/jira/browse/KAFKA-2203
> Project: Kafka
> Issue Type: Bug
> Components: build
> Affects Versions: 0.8.1.1
> Reporter: Gaju Bhat
> Priority: Minor
> Fix For: 0.8.1.2
>
> Attachments: 0001-Special-case-java-8-and-javadoc-handling.patch
>
>
> The gradle build halts because javadoc in java 8 is a lot stricter about
> valid html.
> It might be worthwhile to special case java 8 as described
> [here|http://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
