MINOR: Add verification step for Streams archetype to Jenkins build#6431
MINOR: Add verification step for Streams archetype to Jenkins build#6431bbejeck merged 4 commits intoapache:trunkfrom
Conversation
|
Retest this please. |
0d080ae to
82cd5ab
Compare
|
Call for review @guozhangwang @bbejeck @vvcephei @ableegoldman (\cc @ijuma) |
There was a problem hiding this comment.
This fix should actually be provided by #6194 -- I included it here to let the build pass.
There was a problem hiding this comment.
The created archetype, only works for Java8 -- we would need to create a different archetype for Java11.
What we could do, is to include the Java11 setting as comments in the archetype (thoughts)?
There was a problem hiding this comment.
We could do that, or we can just publish another archetype for use with Java 11+. Then, when we drop support for Java 8, it's as simple as just deleting the Java 8 archetype.
There was a problem hiding this comment.
Not sure how we could have two archetypes at the same time? I guess we would need to encode the Java version in the archetype name?
-DarchetypeGroupId=org.apache.kafka
-DarchetypeArtifactId=streams-quickstart-java <--- change this to `streams-quickstart-java-8` and `streams-quickstart-java-11` ?
-DarchetypeVersion=$version
There was a problem hiding this comment.
Yep, that would be the way to do it.
There was a problem hiding this comment.
@guozhangwang Can/should we do this in this PR? Or would this need a KIP? Or just create a JIRA for a follow up PR?
There was a problem hiding this comment.
We can create a JIRA ticket for a follow-up PR (this would need a KIP, yes).
There was a problem hiding this comment.
|
Java8 failed as expected: |
There was a problem hiding this comment.
We could do that, or we can just publish another archetype for use with Java 11+. Then, when we drop support for Java 8, it's as simple as just deleting the Java 8 archetype.
guozhangwang
left a comment
There was a problem hiding this comment.
LGTM. Please feel free to merge after jenkins.
There was a problem hiding this comment.
nit: one more indent.
There was a problem hiding this comment.
We can create a JIRA ticket for a follow-up PR (this would need a KIP, yes).
3fd34ea to
7fc213e
Compare
|
Rebased to get the fix from #6194. |
|
Java11 failed with known flaky tests. Java8 failed with (https://builds.apache.org/job/kafka-pr-jdk8-scala2.11/20398/console): Is this an environmental issue or indicates a flaky test? Retest this please. |
|
Java 11 failed. Created ticket. Retest this please. |
|
Merged #6431 into trunk. |
* apache/trunk: (23 commits) KAFKA-7986: Distinguish logging from different ZooKeeperClient instances (apache#6493) KAFKA-8102: Add an interval-based Trogdor transaction generator (apache#6444) MINOR: Fix misspelling in protocol documentation KAFKA-8150: Fix bugs in handling null arrays in generated RPC code (apache#6489) KAFKA-8014: Extend Connect integration tests to add and remove workers dynamically (apache#6342) MINOR: Remove line for testing repartition topic name (apache#6488) MINOR: add MacOS requirement to Streams docs MINOR: fix message protocol help text for ElectPreferredLeadersResult (apache#6479) MINOR: list-topics should not require topic param MINOR: Clean up ThreadCacheTest (apache#6485) MINOR: Avoid unnecessary collection copy in MetadataCache (apache#6397) KAFKA-8142: Fix NPE for nulls in Headers (apache#6484) KAFKA-7243: Add unit integration tests to validate metrics in Kafka Streams (apache#6080) MINOR: Add verification step for Streams archetype to Jenkins build (apache#6431) KAFKA-7819: Improve RoundTripWorker (apache#6187) KAFKA-7989: RequestQuotaTest should wait for quota config change before running tests (apache#6482) KAFKA-8098: Fix Flaky Test testConsumerGroups KAFKA-6958: Add new NamedOperation interface to enforce consistency in naming operations (apache#6409) MINOR: capture result timestamps in Kafka Streams DSL tests (apache#6447) MINOR: updated names for deprecated streams constants (apache#6466) ...
…pache#6431) Updates ./jenkins.sh to build stream archetype and install it in local maven cache. Afterward, archetype is used to create a new maven project and maven project is compiled for verification. Reviewers: Guozhang Wang <wangguoz@gmail.com>, John Roesler <john@confluent.io>, Bill Bejeck <bbejeck@gmail.com>
Updates
./jenkins.shto build stream archetype and install it in local maven cache. Afterward, archetype is used to create a new maven project and maven project is compiled for verification.