Jenkins build is back to normal : beam_SeedJob #2786

See

Build failed in Jenkins: beam_SeedJob #2785

See -- GitHub pull request #6669 of commit 479a343276bd17450fb8468501f8439e723bc6d0, no merge conflicts. Setting status of 479a343276bd17450fb8468501f8439e723bc6d0 to PENDING with url

Re: post-commit failure emails

The email trigger is setup to trigger on the 1st failure (after last green I presume), and to send an email to "suspects" of the first failing build (authors and build triggerers). If a new job's first build is failing it should send an email, but only to suspects.

Re: post-commit failure emails

There are numerous reports on this list of Jenkins emails being spammy on new jobs. The list of emails generated on the first run is everyone who has ever had a commit merged to Beam. I don't suppose that would be a problem if this doesn't get turned on until at least one run has passed on each

post-commit failure emails

Hi, https://github.com/apache/beam/pull/6635 is an attempt to notify commit authors if their commit is suspected to have broken post-commit test. I'd would like to get some feedback about this feature. Is it accurate? Is it spammy? Thanks! smime.p7s Description: S/MIME Cryptographic Signature

Re: [DISCUSS] - Separate JIRA notifications to a new mailing list

+1 -Rui On Thu, Oct 11, 2018 at 12:53 PM Ankur Goenka wrote: > +1 > > On Thu, Oct 11, 2018 at 12:14 PM Suneel Marthi > wrote: > >> +1 >> >> Sent from my iPhone >> >> On Oct 11, 2018, at 8:03 PM, Łukasz Gajowy >> wrote: >> >> This is a good idea. +1 >> >> Łukasz >> >> >> czw., 11 paź 2018,

Re: [Proposal] Add exception handling option to MapElements

The PR (https://github.com/apache/beam/pull/6586) is updated now with a coding solution for Failure. We use AvroCoder for the Exception and inherit whatever the input coder was for values. The unfortunate bit is that users might provide an Exception subclass that doesn't provide a no-argument

Re: [DISCUSS] - Separate JIRA notifications to a new mailing list

+1 On Thu, Oct 11, 2018 at 12:14 PM Suneel Marthi wrote: > +1 > > Sent from my iPhone > > On Oct 11, 2018, at 8:03 PM, Łukasz Gajowy > wrote: > > This is a good idea. +1 > > Łukasz > > > czw., 11 paź 2018, 18:01 użytkownik Udi Meiri napisał: > >> +1 to split JIRA notifications >> >> On Thu,

Re: [DISCUSS] Gradle for the build ?

Hi all! Coming from the Go SDK side, I'm in favour of splitting the repo after the portability APIs have stablized. The reason being that it would be all to easy for changes not be propagated to the SDKs, which would cause painful drift. As for the Go Gradle experience, it agree it leaves much to

Re: Python 3: final step

I cc'ed a few folks who are familiar with Jenkins setup on https://issues.apache.org/jira/browse/BEAM-5663, I think we can continue the discussion there or start a separate thread. On Wed, Oct 10, 2018 at 8:54 PM Manu Zhang wrote: > Does anyone know how to set up python version on Jenkins ?

Re: [DISCUSS] - Separate JIRA notifications to a new mailing list

+1 Sent from my iPhone > On Oct 11, 2018, at 8:03 PM, Łukasz Gajowy wrote: > > This is a good idea. +1 > > Łukasz > > > czw., 11 paź 2018, 18:01 użytkownik Udi Meiri napisał: >> +1 to split JIRA notifications >> >>> On Thu, Oct 11, 2018 at 9:13 AM Kenneth Knowles wrote: >>> On Thu,

Re: [DISCUSS] - Separate JIRA notifications to a new mailing list

This is a good idea. +1 Łukasz czw., 11 paź 2018, 18:01 użytkownik Udi Meiri napisał: > +1 to split JIRA notifications > > On Thu, Oct 11, 2018 at 9:13 AM Kenneth Knowles wrote: > >> >> On Thu, Oct 11, 2018 at 9:10 AM Mikhail Gryzykhin < >> gryzykhin.mikh...@gmail.com> wrote: >> >>> +1. >>>

Re: Jenkins build is back to normal : beam_SeedJob #2781

Sorry for the Jenkins spam; I was testing some changes [1] to fix a bug [2] in the new website pre-commits. It's still unfortunately difficult to work on core Jenkins jobs without effecting the published jobs. [1] https://github.com/apache/beam/pull/6655 [2]

Re: [DISCUSS] Gradle for the build ?

I agree with the points made that our Gradle configuration is too complicated (learning Groovy and BeamModulePlugin come to mind). But I mainly write for Python SDK, and I've done experiments in the past with Bazel builds, which was a much better fit for Python as an incremental and parallel

Re: Java compilation errors

It's being discussed on Slack at the moment, the issue seems to be the new errorprone version which has new checks. On Thu, Oct 11, 2018 at 10:23 AM Mikhail Gryzykhin wrote: > Hi everyone, > > Just a heads up: > > I see that Java builds have compilation failures. Can someone help look > into

Java compilation errors

Hi everyone, Just a heads up: I see that Java builds have compilation failures. Can someone help look into this please? Unfortunately, I don't have time to look into it myself atm. Regards, --Mikhail Have feedback ?

Re: [Proposal] Euphoria DSL - looking for reviewers

I've filed the IP Clearance. I'll report back here. Kenn On Wed, Oct 10, 2018 at 3:33 PM David Morávek wrote: > > > Anton: > All of the points are be correct, with one minor exception. We are > currently moving our production workloads from Euphoria > to

Re: [DISCUSS] - Separate JIRA notifications to a new mailing list

+1 to split JIRA notifications On Thu, Oct 11, 2018 at 9:13 AM Kenneth Knowles wrote: > > On Thu, Oct 11, 2018 at 9:10 AM Mikhail Gryzykhin < > gryzykhin.mikh...@gmail.com> wrote: > >> +1. >> Should we separate Jenkins notifications as well? >> > > I'm worried this question will get buried in

Jenkins build is back to normal : beam_SeedJob #2781

See

Build failed in Jenkins: beam_SeedJob #2780

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

Jenkins build is back to normal : beam_SeedJob #2779

See

Build failed in Jenkins: beam_SeedJob #2778

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

Re: [DISCUSS] - Separate JIRA notifications to a new mailing list

On Thu, Oct 11, 2018 at 9:10 AM Mikhail Gryzykhin < gryzykhin.mikh...@gmail.com> wrote: > +1. > Should we separate Jenkins notifications as well? > I'm worried this question will get buried in the thread. Would you mind separating it into another thread if you would like to discuss? Kenn >

Re: [DISCUSS] - Separate JIRA notifications to a new mailing list

+1. Should we separate Jenkins notifications as well? On Thu, Oct 11, 2018, 08:59 Scott Wegner +1, commits@ is too noisy to be useful currently. > > On Thu, Oct 11, 2018 at 8:04 AM Maximilian Michels wrote: > >> +1 >> >> I guess most people have already filters in place to separate commits >>

Re: [DISCUSS] - Separate JIRA notifications to a new mailing list

+1, commits@ is too noisy to be useful currently. On Thu, Oct 11, 2018 at 8:04 AM Maximilian Michels wrote: > +1 > > I guess most people have already filters in place to separate commits > and JIRA issues. JIRA really has nothing to do in the commits list. > > On 11.10.18 15:53, Kenneth Knowles

Jenkins build is back to normal : beam_SeedJob #2776

See

Build failed in Jenkins: beam_SeedJob #2775

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

Re: [DISCUSS] - Separate JIRA notifications to a new mailing list

+1 I guess most people have already filters in place to separate commits and JIRA issues. JIRA really has nothing to do in the commits list. On 11.10.18 15:53, Kenneth Knowles wrote: +1 I've suggested the same. Canonical. On Thu, Oct 11, 2018, 06:19 Thomas Weise >

Re: [DISCUSS] - Separate JIRA notifications to a new mailing list

+1 I've suggested the same. Canonical. On Thu, Oct 11, 2018, 06:19 Thomas Weise wrote: > +1 > > > On Thu, Oct 11, 2018 at 6:18 AM Etienne Chauchot > wrote: > >> +1 for me also, my gmail filters list is kind of overflowed :) >> >> Etienne >> >> Le jeudi 11 octobre 2018 à 14:44 +0200, Robert

Re: [DISCUSS] - Separate JIRA notifications to a new mailing list

+1 On Thu, Oct 11, 2018 at 6:18 AM Etienne Chauchot wrote: > +1 for me also, my gmail filters list is kind of overflowed :) > > Etienne > > Le jeudi 11 octobre 2018 à 14:44 +0200, Robert Bradshaw a écrit : > > Huge +1 from me too. > > On Thu, Oct 11, 2018 at 2:42 PM Jean-Baptiste Onofré >

Re: [DISCUSS] - Separate JIRA notifications to a new mailing list

+1 for me also, my gmail filters list is kind of overflowed :) Etienne Le jeudi 11 octobre 2018 à 14:44 +0200, Robert Bradshaw a écrit : > Huge +1 from me too.On Thu, Oct 11, 2018 at 2:42 PM Jean-Baptiste Onofré > wrote: > > +1 > We are doing the same in Karaf as well. > RegardsJB > On

Re: [DISCUSS] - Separate JIRA notifications to a new mailing list

Huge +1 from me too. On Thu, Oct 11, 2018 at 2:42 PM Jean-Baptiste Onofré wrote: > > +1 > > We are doing the same in Karaf as well. > > Regards > JB > > On 11/10/2018 14:35, Colm O hEigeartaigh wrote: > > Hi all, > > > > Apologies in advance if this has already been discussed (and rejected). > >

Re: [DISCUSS] - Separate JIRA notifications to a new mailing list

+1 We are doing the same in Karaf as well. Regards JB On 11/10/2018 14:35, Colm O hEigeartaigh wrote: > Hi all, > > Apologies in advance if this has already been discussed (and rejected). > I was wondering if it would be a good idea to create a new mailing list > and divert the JIRA

[DISCUSS] - Separate JIRA notifications to a new mailing list

Hi all, Apologies in advance if this has already been discussed (and rejected). I was wondering if it would be a good idea to create a new mailing list and divert the JIRA notifications to it? Currently "comm...@beam.apache.org" receives both the git and JIRA notifications, and has a huge volume

Re: [PROPOSAL] Move testing utilities to a common place.

> > sdks/java/tests? Assuming this will be Java utility code and Java test >> suites. >> > Yes, I meant "sdks/java/tests". I would prefer a more descriptive name than `common` if you can come up > with something. As much as I usually dislike `util` in this case I would go > with that, only

Re: [DISCUSS] Gradle for the build ?

I agree with all previous points related to Gradle-related problems. Among all others, I’d highlight IDE integration issue since it can have real negative impact on attracting new contributors and, finally, community grow. The more obstacles there are to start code contribution, the more

Re: Java > 8 support

FWIW, the issue regarding java 11 support to gradle might be helpful here [1]. Quoting: "there are only some minor corner cases that don't work. Overall Java 11 support is pretty solid already" but some users reported problems in comments with Checkstyle plugin and MacOS + Gradle4.10.2 (this might