streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Blackmon <>
Subject Re: DISCUSS: Consolidate Example modules with Project Repo
Date Tue, 09 Jan 2018 17:13:15 GMT
 I think we would compile examples with every pull request and merge to
master, and run examples integration tests along with the rest of the ITs
in the streams-project-verify jenkins job (and as a step in the release
process like you mentioned.)

We’re now at the point where we need to start categorizing our integration
tests more finely and giving the developer more control over which run -
this is because some integration tests require credentials with special
permissions that not every developer will have access to.  I think we can
fit the examples into that scheme however is appropriate, while also making
their execution conditional on a separate profile disabled by default.


Sent from Astro <> for Mac

On Jan 9, 2018 at 10:24 AM, Joey Frazee <> wrote:


Is the plan to have them be part of every build or to use an optional build
profile? I’m partial to the latter; that said, I could see the argument
wanting whatever the clean install is to be how we build and test for an
Apache release since we will now need those to be voted on for every


On Jan 8, 2018, 1:44 PM -0700, Trevor Grant <>,


On Mon, Jan 8, 2018 at 2:27 PM, Suneel Marthi <> wrote:


On Mon, Jan 8, 2018 at 3:26 PM, Steve Blackmon <

I’d like to discuss consolidating apache/streams-examples into
apache/streams under a new top-level module ‘examples’.

We had some good reasons for keeping them isolated during incubation, but
I’ve come around to the perspective that the significant simplification


our setup, test, CI, website publish, and release processes we would get


merging them in would outweigh all of the benefits of keeping them apart.

Also I think the negatives of having the examples reside inside the


can largely be mitigated by adding a new profile that shades and
integration tests the examples but is disabled by default.

Lastly, given that Flink, Kafka, and Spark are all getting by with their
examples hosted inside their primary SCM, I see no reason Streams


do the same

Any +1 or alternative perspectives on the matter?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message