Jenkins build is back to normal : beam_SeedJob_Standalone #800

See

Build failed in Jenkins: beam_SeedJob #1432

See -- GitHub pull request #5010 of commit 84a491eac0685746c47dea98f3f1ae5009454b9f, no merge conflicts. [EnvInject] - Loading node environment variables. Building remotely on beam5 (beam)

Jenkins build is back to normal : beam_SeedJob #1433

See

Build failed in Jenkins: beam_Release_NightlySnapshot #735

See -- [...truncated 1.85 MB...] 2018-04-04T23:12:46.936 [INFO]

Re: Gradle migration fixit: April 3

Hi guys, Anyone has global a view of where we are? When I left yesterday we were far to be consummable by maven users and my diff was not that useful yet but saw JB was on it. Do we make any progress on that in the night? Concrete question is: when can we drop maven as the primarly build tool

Re: How can runners make use of sink parallelism?

Thanks for the explanation! Shen On Wed, Apr 4, 2018 at 12:38 AM, Eugene Kirpichov wrote: > Hi Shen, > > There is no "IO connector API" in Beam (not counting the deprecated Source > API), IO is merely an informal term for a PTransform that interacts in some > way with

Re: Gradle migration fixit: April 3

Thanks for the update Reuven. No problem at all, I think we did good progress anyway. Let's continue the best effort from the community to move forward on this topic. Regards JB On 04/04/2018 05:32 PM, Reuven Lax wrote: > Yesterday we made progress migrating Python to Gradle. We had PRs (some

Re: Gradle migration fixit: April 3

Sounds good. I have less than expected time these days but happy to help doing the artifact diff when the build will have moved enough, just shout here when needed ;) Le 4 avr. 2018 17:33, "Reuven Lax" a écrit : > Yesterday we made progress migrating Python to Gradle. We had

Re: Gradle migration fixit: April 3

Hi, I second Romain here. What I saw this morning is that we have huge gap between gradle and maven, and some areas are still not clear to me (build stability, build time gain, ...). Do we need additional days to fixit ? Does it worth the effort vs the gain ? Regards JB On 04/04/2018 02:51

Re: Gradle migration fixit: April 3

Yesterday we made progress migrating Python to Gradle. We had PRs (some still pending) from people around the world (from the US to France to Poland) helping out. Unfortunately many of the participants yesterday were unfamiliar with any of the infrastructure, and needed to be taught how Jenkins,

Re: Gradle migration fixit: April 3

Of course - thanks for your help yesterday! I also know some others in the community weren't able to help because they were busy preparing for the FlinkForward conference that is next week. Reuven On Wed, Apr 4, 2018 at 8:35 AM Romain Manni-Bucau wrote: > Sounds good. >

Build failed in Jenkins: beam_SeedJob #1423

See Changes: [rmannibucau] [BEAM-3993] read gitignore and add it in rat exclusions [lcwik] [BEAM-3993] Remove duplicate definitions between .gitignore and [herohde] [BEAM-3982] Register transform types and

Re: Python postcommit and precommit

Was this resolved off list? I think it makes sense to have a dependency-driven build tool as the entry point to these processes. So in our case, Gradle. If setting it up in Gradle/Groovy is a pain, having it shell out seems fine as an implementation detail, but you need to set up inputs/outputs of

Build failed in Jenkins: beam_SeedJob #1424

See -- GitHub pull request #5010 of commit 84a491eac0685746c47dea98f3f1ae5009454b9f, no merge conflicts. Setting status of 84a491eac0685746c47dea98f3f1ae5009454b9f to PENDING with url

Build failed in Jenkins: beam_SeedJob #1425

See -- Started by timer [EnvInject] - Loading node environment variables. Building remotely on beam2 (beam) in workspace > git rev-parse

Updated [Proposal] Apache Beam Fn API : Defining and adding SDK Metrics

Hello beam community, Thank you everyone for your initial feedback on this proposal so far. I have made some revisions based on the feedback. There were some larger questions asking about alternatives. For each of these I have added a section tagged with [Alternatives] and discussed my

Re: Updated [Proposal] Apache Beam Fn API : Defining and adding SDK Metrics

Thanks for the nice writeup. I added some comments. On Wed, Apr 4, 2018 at 1:53 PM Alex Amato wrote: > Hello beam community, > > Thank you everyone for your initial feedback on this proposal so far. I > have made some revisions based on the feedback. There were some larger >

Build failed in Jenkins: beam_SeedJob #1416

See -- GitHub pull request #5012 of commit f5b3445342f75cd0074fc8230534340b9b25a246, no merge conflicts. Setting status of f5b3445342f75cd0074fc8230534340b9b25a246 to PENDING with url

Jenkins build is back to normal : beam_SeedJob #1417

See

Build failed in Jenkins: beam_Release_NightlySnapshot #734

See Changes: [ankurgoenka] Support multiple SDKHarness and SdkWorkerId in RunnerHarness [ccy] Use utcnow() in determining credential refresh time [chamikara] Revert "[BEAM-2264] Credentials were not