[
https://issues.apache.org/jira/browse/KAFKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14903124#comment-14903124
]
Ismael Juma commented on KAFKA-2566:
------------------------------------
One open question is whether we want to run run the javadoc tool in the Jenkins
build in order to catch javadoc errors.
> Improve Jenkins set-up
> ----------------------
>
> Key: KAFKA-2566
> URL: https://issues.apache.org/jira/browse/KAFKA-2566
> Project: Kafka
> Issue Type: Task
> Reporter: Ismael Juma
>
> There are currently two Jenkins jobs:
> https://builds.apache.org/job/Kafka-trunk
> https://builds.apache.org/job/kafka-trunk-git-pr
> They both run with Java 7 and execute the following gradle command:
> ./gradlew -PscalaVersion=2.10.1 test
> There are a few issues with this:
> * We don't test Java 8 even though that's the only stable release of the JDK
> that still receives security fixes
> * We are testing with Scala 2.10.1 even though we should be testing with
> Scala 2.10.5
> * We are not testing with Scala 2.11.x
> * We are not doing clean builds
> I suggest the following:
> 1. Change the `kafka-trunk-git-pr` job to use the `./gradlew clean test`
> command.
> 2. Change the `Kafka-trunk` job to use the `./gradlew clean testAll` command.
> 3. Introduce a kafka-trunk-jdk8 job with the command `./gradlew clean testAll`
> This is a compromise that doesn't slow down the PR job (which is executed
> much more often) while still testing trunk in all of our supported JDK and
> Scala versions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
