Re: Including Apex runner in Beam tutorial at Strata - Singapore

Thanks Thomas for the suggestions. I will work on 2nd and 3rd part. Connecting with Tyler Akidau offline. Regards, Sandeep On Wed, Nov 16, 2016 at 4:40 AM, Thomas Weise wrote: > The runner currently only executes in embedded mode and I'm not sure that > will change prior to

Re: Beam dinner tonight

Cool. Enjoy your time. Yonglong 2016-11-15 15:23 GMT-08:00 Dan Halperin : > Hi Yonglong, > > First, sorry for spamming the dev list. It may not be the best thing to > spam the entire community when 10 of us are at a conference ... but since > Beam is a new project,

Re: Jenkins skipping PreCommit for a PR caused build failures on master.

The command is apache-rat:check, not rat:check. http://creadur.apache.org/rat/apache-rat-plugin/ rat:check is using the (very old) Maven2 plugin for RAT from the now defunct org.codehaus: https://mvnrepository.com/artifact/org.codehaus.mojo/rat-maven-plugin/1.0-alpha-3 Dan On Wed, Nov 16, 2016

Re: Beam dinner tonight

Hi Yonglong, First, sorry for spamming the dev list. It may not be the best thing to spam the entire community when 10 of us are at a conference ... but since Beam is a new project, this conference is the first time we're all meeting each other. Second, no we are not in CA currently -- we are at

Re: Including Apex runner in Beam tutorial at Strata - Singapore

The runner currently only executes in embedded mode and I'm not sure that will change prior to Strata due to dependency on next Apex core release. I would suggest to aim for the following: - Create a sample wordcount project that produces the packaging that is required to launch the

Re: Beam dinner tonight

You guys are enviable. Are you in the CA? Thanks

Re: Build failed in Jenkins: beam_PostCommit_MavenVerify #1827

I opened https://issues.apache.org/jira/browse/BEAM-983 On Tue, Nov 15, 2016 at 10:29 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See MavenVerify/1827/changes> > > Changes: > > [ansela] [BEAM-891] fix build occasionally fails

Re: Including Apex runner in Beam tutorial at Strata - Singapore

Thanks JB. I will get started on this. Regards, Sandeep On 15-Nov-2016 8:34 PM, "Jean-Baptiste Onofré" wrote: > Hi Sandeep, > > Great news ! > > Yes, you can definitely do a demo using the Apex runner. It's what Dan and > I are also planning during ApacheCon this week: same

Re: Configuring Jenkins

This is great; thanks for doing this! On Tue, Nov 15, 2016 at 6:43 AM, Dan Halperin wrote: > Seems phenomenal! > > Reading between the lines of your email, it sounds like changes to Jenkins > configuration will not actually be exercised on the PR that makes them. So,

Re: Including Apex runner in Beam tutorial at Strata - Singapore

Hi Sandeep, Great news ! Yes, you can definitely do a demo using the Apex runner. It's what Dan and I are also planning during ApacheCon this week: same Wordcount example running on different execution engines. Maybe this blog could help you to prepare the demo:

Including Apex runner in Beam tutorial at Strata - Singapore

Dear Beam Community, There is a Beam tutorial in Strata-Singapore. I would like to explore possibility of including the Apex runner as a part of that tutorial. As Apex runner is recently merged into master branch of Beam, it would be of interest to many people. Please let us know if we can do

Re: Configuring Jenkins

Seems phenomenal! Reading between the lines of your email, it sounds like changes to Jenkins configuration will not actually be exercised on the PR that makes them. So, we still need to work out a process of how we test changes that would affect Jenkins config. (That does not take away from the

Re: Configuring Jenkins

This is very cool….. I definitely need to look at this a bit as there a few there projects that would love to have something similar. :) Dan > On Nov 15, 2016, at 4:01 AM, Davor Bonaci wrote: > > Hi everybody, > As I'm sure everybody knows, we use Apache's

Configuring Jenkins

Hi everybody, As I'm sure everybody knows, we use Apache's Jenkins instance for all our testing, including pre-commit, post-commit, nightly snapshot, etc. (Travis CI is a backup system and recommended for individual forks only.) Managing Jenkins projects has been a big pain point so far. Among