You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by Christopher <ct...@apache.org> on 2020/03/18 21:25:34 UTC
[PROPOSAL] Send build notifications to notifications list
Hi ZK Devs,
I have been trying to watch the ZooKeeper developer list lately, to
stay on top of latest issues, and to contribute in whatever small way
I can. However, I noticed the list gets a lot of spam from automated
notifications (especially Jenkins).
This has the effect of drowning out conversation between actual
humans, and can discourage participation, because it requires new
subscribers to set up a bunch of filters to suppress these, if they
don't want to see them (and they may unintentionally suppress human
conversation, if they don't set up their filters perfectly).
What do the ZK committers/PMC members think about having Jenkins send
build notifications to the notifications@ list instead of dev@?
Thanks,
Christopher
Re: [PROPOSAL] Send build notifications to notifications list
Posted by Christopher <ct...@apache.org>.
Okay, I cleaned up the views. They are now under the "Z" top-level group
at: https://builds.apache.org/view/Z/view/ZooKeeper/
(I'm probably going to try to help other projects organize theirs under
their corresponding top-level single-character groups as well, but that
will take time)
I updated the destination email for all the jobs to go to the notifications
list now. It may be necessary for a moderator to whitelist Jenkins there.
I'm not sure.
The following jobs did not have email notifications set up, so I left them
alone:
PreCommit-ZOOKEEPER-github-pr-build (might be a duplicate of
PreCommit-ZOOKEEPER-github-pr-build-maven ?)
ZooKeeper-Find-Flaky-Tests
Additionally, I think the JDK testing can be limited to just the JDK for
the target version (8), the latest (14), and the intermediate LTS ones
(11). I don't think 9, 10, 12, and 13 need to be tested as well. I'm not
trying to argue for *less* testing; rather, I'm trying to argue for more
*strategic* testing that 1) better utilizes the shared build server
resources, and 2) to increase the signal-to-noise ratio for developers
trying to pay attention to the test results.
Another way to increase the signal-to-noise ratio around testing is to
avoid duplication of effort between Travis CI and Jenkins, but I haven't
looked into this much yet.
On Fri, Mar 20, 2020 at 10:05 AM Andor Molnar <an...@apache.org> wrote:
> Hi Christopher,
>
> I’m happy to use the new, top-level view from now. Additionally I deleted
> all the disabled projects, as you said, we don’t need them anymore. I’m not
> sure about the rest, need to take a closer look.
>
> Thanks for your efforts.
>
> Andor
>
>
>
>
> > On 2020. Mar 19., at 19:50, Christopher <ct...@apache.org> wrote:
> >
> > That view only shows 23 of ZK's total jobs. I think that view should also
> > be deleted in favor of the one at
> > https://builds.apache.org/view/Z/view/ZooKeeper/
> > Part of the impetus for creating individual tabs, one for each letter, is
> > for stability, because when we group letters into groups, people feel the
> > need to adjust them when one group gets bigger than others. This happened
> > twice, and broke links. Having the top-level views of a single letter,
> and
> > subviews under that creates stable, predictable links to job views.
> >
> > On Thu, Mar 19, 2020 at 2:38 PM Patrick Hunt <ph...@apache.org> wrote:
> >
> >> afaik this is the view (at least the one I use):
> >> https://builds.apache.org/view/S-Z/view/ZooKeeper/
> >> it's curated to maintain the current/active jobs for the current/active
> >> branches and smattering of jdks for coverage.
> >>
> >> Patrick
> >>
> >> On Thu, Mar 19, 2020 at 11:30 AM Christopher <ct...@apache.org>
> wrote:
> >>
> >>> It sounds like there's at least the beginnings of consensus here.
> >>>
> >>> So, I took a look at how ZK's jobs are configured in builds.apache.org
> ,
> >> in
> >>> order to prepare to help make the change, and saw some stuff that was
> >>> slightly upsetting (🙂), or at least daunting for whoever makes the
> >> change:
> >>>
> >>> 1. There are 45 Jenkins jobs for ZK. That seems insane to me. Is there
> >> any
> >>> old ones that can be removed? I'm not sure which the community finds
> >>> valuable and which are excess, but all the disabled ones should
> probably
> >> be
> >>> deleted, because they are definitely not in use. It would be best if a
> >>> committer could identify and delete the ones that aren't needed. That
> >> will
> >>> save some time in editing the configs to change the target email.
> >>>
> >>> 2. I also noticed there's a top-level view at
> >>> https://builds.apache.org/view/ZK%20All/ ; several years ago, I tried
> to
> >>> get people to do a better job of keeping Jenkins views organized, so I
> >>> created a new tab for each letter of the Latin alphabet to encourage
> >>> projects to create subviews under that. ZooKeeper didn't have one, and
> >> had
> >>> the top-level view instead. So, I went ahead and created a new view at
> >>> https://builds.apache.org/view/Z/view/ZooKeeper/ ; I think the
> top-level
> >>> view at https://builds.apache.org/view/ZK%20All/should be deleted.
> >>>
> >>> Once the extras repos are deleted, I'd be happy to be the one to
> >> tediously
> >>> update each job to point to the notifications list, but a moderator
> might
> >>> need to approve the Jenkins sender. 🙂
> >>>
> >>>
> >>> On Thu, Mar 19, 2020 at 11:18 AM Szalay-Bekő Máté <
> >>> szalay.beko.mate@gmail.com> wrote:
> >>>
> >>>> I also like it! It will make it easier for new community members to
> >> joint
> >>>> to discussions.
> >>>>
> >>>> although it also means I will have to setup new filters now for
> >>>> the notifications@ list ;)
> >>>>
> >>>> On Thu, Mar 19, 2020 at 1:52 PM RABI K.C. <ra...@gmail.com> wrote:
> >>>>
> >>>>> Hi Christopher,
> >>>>>
> >>>>> I am +1 on this.
> >>>>>
> >>>>> Regards,
> >>>>> Rabi Kumar K C
> >>>>>
> >>>>> On Wed, Mar 18, 2020 at 10:25 PM Christopher <ct...@apache.org>
> >>>> wrote:
> >>>>>
> >>>>>> Hi ZK Devs,
> >>>>>>
> >>>>>> I have been trying to watch the ZooKeeper developer list lately, to
> >>>>>> stay on top of latest issues, and to contribute in whatever small
> >> way
> >>>>>> I can. However, I noticed the list gets a lot of spam from
> >> automated
> >>>>>> notifications (especially Jenkins).
> >>>>>>
> >>>>>> This has the effect of drowning out conversation between actual
> >>>>>> humans, and can discourage participation, because it requires new
> >>>>>> subscribers to set up a bunch of filters to suppress these, if they
> >>>>>> don't want to see them (and they may unintentionally suppress human
> >>>>>> conversation, if they don't set up their filters perfectly).
> >>>>>>
> >>>>>> What do the ZK committers/PMC members think about having Jenkins
> >> send
> >>>>>> build notifications to the notifications@ list instead of dev@?
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Christopher
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
>
>
Re: [PROPOSAL] Send build notifications to notifications list
Posted by Andor Molnar <an...@apache.org>.
Hi Christopher,
I’m happy to use the new, top-level view from now. Additionally I deleted all the disabled projects, as you said, we don’t need them anymore. I’m not sure about the rest, need to take a closer look.
Thanks for your efforts.
Andor
> On 2020. Mar 19., at 19:50, Christopher <ct...@apache.org> wrote:
>
> That view only shows 23 of ZK's total jobs. I think that view should also
> be deleted in favor of the one at
> https://builds.apache.org/view/Z/view/ZooKeeper/
> Part of the impetus for creating individual tabs, one for each letter, is
> for stability, because when we group letters into groups, people feel the
> need to adjust them when one group gets bigger than others. This happened
> twice, and broke links. Having the top-level views of a single letter, and
> subviews under that creates stable, predictable links to job views.
>
> On Thu, Mar 19, 2020 at 2:38 PM Patrick Hunt <ph...@apache.org> wrote:
>
>> afaik this is the view (at least the one I use):
>> https://builds.apache.org/view/S-Z/view/ZooKeeper/
>> it's curated to maintain the current/active jobs for the current/active
>> branches and smattering of jdks for coverage.
>>
>> Patrick
>>
>> On Thu, Mar 19, 2020 at 11:30 AM Christopher <ct...@apache.org> wrote:
>>
>>> It sounds like there's at least the beginnings of consensus here.
>>>
>>> So, I took a look at how ZK's jobs are configured in builds.apache.org,
>> in
>>> order to prepare to help make the change, and saw some stuff that was
>>> slightly upsetting (🙂), or at least daunting for whoever makes the
>> change:
>>>
>>> 1. There are 45 Jenkins jobs for ZK. That seems insane to me. Is there
>> any
>>> old ones that can be removed? I'm not sure which the community finds
>>> valuable and which are excess, but all the disabled ones should probably
>> be
>>> deleted, because they are definitely not in use. It would be best if a
>>> committer could identify and delete the ones that aren't needed. That
>> will
>>> save some time in editing the configs to change the target email.
>>>
>>> 2. I also noticed there's a top-level view at
>>> https://builds.apache.org/view/ZK%20All/ ; several years ago, I tried to
>>> get people to do a better job of keeping Jenkins views organized, so I
>>> created a new tab for each letter of the Latin alphabet to encourage
>>> projects to create subviews under that. ZooKeeper didn't have one, and
>> had
>>> the top-level view instead. So, I went ahead and created a new view at
>>> https://builds.apache.org/view/Z/view/ZooKeeper/ ; I think the top-level
>>> view at https://builds.apache.org/view/ZK%20All/should be deleted.
>>>
>>> Once the extras repos are deleted, I'd be happy to be the one to
>> tediously
>>> update each job to point to the notifications list, but a moderator might
>>> need to approve the Jenkins sender. 🙂
>>>
>>>
>>> On Thu, Mar 19, 2020 at 11:18 AM Szalay-Bekő Máté <
>>> szalay.beko.mate@gmail.com> wrote:
>>>
>>>> I also like it! It will make it easier for new community members to
>> joint
>>>> to discussions.
>>>>
>>>> although it also means I will have to setup new filters now for
>>>> the notifications@ list ;)
>>>>
>>>> On Thu, Mar 19, 2020 at 1:52 PM RABI K.C. <ra...@gmail.com> wrote:
>>>>
>>>>> Hi Christopher,
>>>>>
>>>>> I am +1 on this.
>>>>>
>>>>> Regards,
>>>>> Rabi Kumar K C
>>>>>
>>>>> On Wed, Mar 18, 2020 at 10:25 PM Christopher <ct...@apache.org>
>>>> wrote:
>>>>>
>>>>>> Hi ZK Devs,
>>>>>>
>>>>>> I have been trying to watch the ZooKeeper developer list lately, to
>>>>>> stay on top of latest issues, and to contribute in whatever small
>> way
>>>>>> I can. However, I noticed the list gets a lot of spam from
>> automated
>>>>>> notifications (especially Jenkins).
>>>>>>
>>>>>> This has the effect of drowning out conversation between actual
>>>>>> humans, and can discourage participation, because it requires new
>>>>>> subscribers to set up a bunch of filters to suppress these, if they
>>>>>> don't want to see them (and they may unintentionally suppress human
>>>>>> conversation, if they don't set up their filters perfectly).
>>>>>>
>>>>>> What do the ZK committers/PMC members think about having Jenkins
>> send
>>>>>> build notifications to the notifications@ list instead of dev@?
>>>>>>
>>>>>> Thanks,
>>>>>> Christopher
>>>>>>
>>>>>
>>>>
>>>
>>
Re: [PROPOSAL] Send build notifications to notifications list
Posted by Christopher <ct...@apache.org>.
That view only shows 23 of ZK's total jobs. I think that view should also
be deleted in favor of the one at
https://builds.apache.org/view/Z/view/ZooKeeper/
Part of the impetus for creating individual tabs, one for each letter, is
for stability, because when we group letters into groups, people feel the
need to adjust them when one group gets bigger than others. This happened
twice, and broke links. Having the top-level views of a single letter, and
subviews under that creates stable, predictable links to job views.
On Thu, Mar 19, 2020 at 2:38 PM Patrick Hunt <ph...@apache.org> wrote:
> afaik this is the view (at least the one I use):
> https://builds.apache.org/view/S-Z/view/ZooKeeper/
> it's curated to maintain the current/active jobs for the current/active
> branches and smattering of jdks for coverage.
>
> Patrick
>
> On Thu, Mar 19, 2020 at 11:30 AM Christopher <ct...@apache.org> wrote:
>
> > It sounds like there's at least the beginnings of consensus here.
> >
> > So, I took a look at how ZK's jobs are configured in builds.apache.org,
> in
> > order to prepare to help make the change, and saw some stuff that was
> > slightly upsetting (🙂), or at least daunting for whoever makes the
> change:
> >
> > 1. There are 45 Jenkins jobs for ZK. That seems insane to me. Is there
> any
> > old ones that can be removed? I'm not sure which the community finds
> > valuable and which are excess, but all the disabled ones should probably
> be
> > deleted, because they are definitely not in use. It would be best if a
> > committer could identify and delete the ones that aren't needed. That
> will
> > save some time in editing the configs to change the target email.
> >
> > 2. I also noticed there's a top-level view at
> > https://builds.apache.org/view/ZK%20All/ ; several years ago, I tried to
> > get people to do a better job of keeping Jenkins views organized, so I
> > created a new tab for each letter of the Latin alphabet to encourage
> > projects to create subviews under that. ZooKeeper didn't have one, and
> had
> > the top-level view instead. So, I went ahead and created a new view at
> > https://builds.apache.org/view/Z/view/ZooKeeper/ ; I think the top-level
> > view at https://builds.apache.org/view/ZK%20All/should be deleted.
> >
> > Once the extras repos are deleted, I'd be happy to be the one to
> tediously
> > update each job to point to the notifications list, but a moderator might
> > need to approve the Jenkins sender. 🙂
> >
> >
> > On Thu, Mar 19, 2020 at 11:18 AM Szalay-Bekő Máté <
> > szalay.beko.mate@gmail.com> wrote:
> >
> > > I also like it! It will make it easier for new community members to
> joint
> > > to discussions.
> > >
> > > although it also means I will have to setup new filters now for
> > > the notifications@ list ;)
> > >
> > > On Thu, Mar 19, 2020 at 1:52 PM RABI K.C. <ra...@gmail.com> wrote:
> > >
> > > > Hi Christopher,
> > > >
> > > > I am +1 on this.
> > > >
> > > > Regards,
> > > > Rabi Kumar K C
> > > >
> > > > On Wed, Mar 18, 2020 at 10:25 PM Christopher <ct...@apache.org>
> > > wrote:
> > > >
> > > > > Hi ZK Devs,
> > > > >
> > > > > I have been trying to watch the ZooKeeper developer list lately, to
> > > > > stay on top of latest issues, and to contribute in whatever small
> way
> > > > > I can. However, I noticed the list gets a lot of spam from
> automated
> > > > > notifications (especially Jenkins).
> > > > >
> > > > > This has the effect of drowning out conversation between actual
> > > > > humans, and can discourage participation, because it requires new
> > > > > subscribers to set up a bunch of filters to suppress these, if they
> > > > > don't want to see them (and they may unintentionally suppress human
> > > > > conversation, if they don't set up their filters perfectly).
> > > > >
> > > > > What do the ZK committers/PMC members think about having Jenkins
> send
> > > > > build notifications to the notifications@ list instead of dev@?
> > > > >
> > > > > Thanks,
> > > > > Christopher
> > > > >
> > > >
> > >
> >
>
Re: [PROPOSAL] Send build notifications to notifications list
Posted by Patrick Hunt <ph...@apache.org>.
afaik this is the view (at least the one I use):
https://builds.apache.org/view/S-Z/view/ZooKeeper/
it's curated to maintain the current/active jobs for the current/active
branches and smattering of jdks for coverage.
Patrick
On Thu, Mar 19, 2020 at 11:30 AM Christopher <ct...@apache.org> wrote:
> It sounds like there's at least the beginnings of consensus here.
>
> So, I took a look at how ZK's jobs are configured in builds.apache.org, in
> order to prepare to help make the change, and saw some stuff that was
> slightly upsetting (🙂), or at least daunting for whoever makes the change:
>
> 1. There are 45 Jenkins jobs for ZK. That seems insane to me. Is there any
> old ones that can be removed? I'm not sure which the community finds
> valuable and which are excess, but all the disabled ones should probably be
> deleted, because they are definitely not in use. It would be best if a
> committer could identify and delete the ones that aren't needed. That will
> save some time in editing the configs to change the target email.
>
> 2. I also noticed there's a top-level view at
> https://builds.apache.org/view/ZK%20All/ ; several years ago, I tried to
> get people to do a better job of keeping Jenkins views organized, so I
> created a new tab for each letter of the Latin alphabet to encourage
> projects to create subviews under that. ZooKeeper didn't have one, and had
> the top-level view instead. So, I went ahead and created a new view at
> https://builds.apache.org/view/Z/view/ZooKeeper/ ; I think the top-level
> view at https://builds.apache.org/view/ZK%20All/should be deleted.
>
> Once the extras repos are deleted, I'd be happy to be the one to tediously
> update each job to point to the notifications list, but a moderator might
> need to approve the Jenkins sender. 🙂
>
>
> On Thu, Mar 19, 2020 at 11:18 AM Szalay-Bekő Máté <
> szalay.beko.mate@gmail.com> wrote:
>
> > I also like it! It will make it easier for new community members to joint
> > to discussions.
> >
> > although it also means I will have to setup new filters now for
> > the notifications@ list ;)
> >
> > On Thu, Mar 19, 2020 at 1:52 PM RABI K.C. <ra...@gmail.com> wrote:
> >
> > > Hi Christopher,
> > >
> > > I am +1 on this.
> > >
> > > Regards,
> > > Rabi Kumar K C
> > >
> > > On Wed, Mar 18, 2020 at 10:25 PM Christopher <ct...@apache.org>
> > wrote:
> > >
> > > > Hi ZK Devs,
> > > >
> > > > I have been trying to watch the ZooKeeper developer list lately, to
> > > > stay on top of latest issues, and to contribute in whatever small way
> > > > I can. However, I noticed the list gets a lot of spam from automated
> > > > notifications (especially Jenkins).
> > > >
> > > > This has the effect of drowning out conversation between actual
> > > > humans, and can discourage participation, because it requires new
> > > > subscribers to set up a bunch of filters to suppress these, if they
> > > > don't want to see them (and they may unintentionally suppress human
> > > > conversation, if they don't set up their filters perfectly).
> > > >
> > > > What do the ZK committers/PMC members think about having Jenkins send
> > > > build notifications to the notifications@ list instead of dev@?
> > > >
> > > > Thanks,
> > > > Christopher
> > > >
> > >
> >
>
Re: [PROPOSAL] Send build notifications to notifications list
Posted by Christopher <ct...@apache.org>.
It sounds like there's at least the beginnings of consensus here.
So, I took a look at how ZK's jobs are configured in builds.apache.org, in
order to prepare to help make the change, and saw some stuff that was
slightly upsetting (🙂), or at least daunting for whoever makes the change:
1. There are 45 Jenkins jobs for ZK. That seems insane to me. Is there any
old ones that can be removed? I'm not sure which the community finds
valuable and which are excess, but all the disabled ones should probably be
deleted, because they are definitely not in use. It would be best if a
committer could identify and delete the ones that aren't needed. That will
save some time in editing the configs to change the target email.
2. I also noticed there's a top-level view at
https://builds.apache.org/view/ZK%20All/ ; several years ago, I tried to
get people to do a better job of keeping Jenkins views organized, so I
created a new tab for each letter of the Latin alphabet to encourage
projects to create subviews under that. ZooKeeper didn't have one, and had
the top-level view instead. So, I went ahead and created a new view at
https://builds.apache.org/view/Z/view/ZooKeeper/ ; I think the top-level
view at https://builds.apache.org/view/ZK%20All/should be deleted.
Once the extras repos are deleted, I'd be happy to be the one to tediously
update each job to point to the notifications list, but a moderator might
need to approve the Jenkins sender. 🙂
On Thu, Mar 19, 2020 at 11:18 AM Szalay-Bekő Máté <
szalay.beko.mate@gmail.com> wrote:
> I also like it! It will make it easier for new community members to joint
> to discussions.
>
> although it also means I will have to setup new filters now for
> the notifications@ list ;)
>
> On Thu, Mar 19, 2020 at 1:52 PM RABI K.C. <ra...@gmail.com> wrote:
>
> > Hi Christopher,
> >
> > I am +1 on this.
> >
> > Regards,
> > Rabi Kumar K C
> >
> > On Wed, Mar 18, 2020 at 10:25 PM Christopher <ct...@apache.org>
> wrote:
> >
> > > Hi ZK Devs,
> > >
> > > I have been trying to watch the ZooKeeper developer list lately, to
> > > stay on top of latest issues, and to contribute in whatever small way
> > > I can. However, I noticed the list gets a lot of spam from automated
> > > notifications (especially Jenkins).
> > >
> > > This has the effect of drowning out conversation between actual
> > > humans, and can discourage participation, because it requires new
> > > subscribers to set up a bunch of filters to suppress these, if they
> > > don't want to see them (and they may unintentionally suppress human
> > > conversation, if they don't set up their filters perfectly).
> > >
> > > What do the ZK committers/PMC members think about having Jenkins send
> > > build notifications to the notifications@ list instead of dev@?
> > >
> > > Thanks,
> > > Christopher
> > >
> >
>
Re: [PROPOSAL] Send build notifications to notifications list
Posted by Szalay-Bekő Máté <sz...@gmail.com>.
I also like it! It will make it easier for new community members to joint
to discussions.
although it also means I will have to setup new filters now for
the notifications@ list ;)
On Thu, Mar 19, 2020 at 1:52 PM RABI K.C. <ra...@gmail.com> wrote:
> Hi Christopher,
>
> I am +1 on this.
>
> Regards,
> Rabi Kumar K C
>
> On Wed, Mar 18, 2020 at 10:25 PM Christopher <ct...@apache.org> wrote:
>
> > Hi ZK Devs,
> >
> > I have been trying to watch the ZooKeeper developer list lately, to
> > stay on top of latest issues, and to contribute in whatever small way
> > I can. However, I noticed the list gets a lot of spam from automated
> > notifications (especially Jenkins).
> >
> > This has the effect of drowning out conversation between actual
> > humans, and can discourage participation, because it requires new
> > subscribers to set up a bunch of filters to suppress these, if they
> > don't want to see them (and they may unintentionally suppress human
> > conversation, if they don't set up their filters perfectly).
> >
> > What do the ZK committers/PMC members think about having Jenkins send
> > build notifications to the notifications@ list instead of dev@?
> >
> > Thanks,
> > Christopher
> >
>
Re: [PROPOSAL] Send build notifications to notifications list
Posted by "RABI K.C." <ra...@gmail.com>.
Hi Christopher,
I am +1 on this.
Regards,
Rabi Kumar K C
On Wed, Mar 18, 2020 at 10:25 PM Christopher <ct...@apache.org> wrote:
> Hi ZK Devs,
>
> I have been trying to watch the ZooKeeper developer list lately, to
> stay on top of latest issues, and to contribute in whatever small way
> I can. However, I noticed the list gets a lot of spam from automated
> notifications (especially Jenkins).
>
> This has the effect of drowning out conversation between actual
> humans, and can discourage participation, because it requires new
> subscribers to set up a bunch of filters to suppress these, if they
> don't want to see them (and they may unintentionally suppress human
> conversation, if they don't set up their filters perfectly).
>
> What do the ZK committers/PMC members think about having Jenkins send
> build notifications to the notifications@ list instead of dev@?
>
> Thanks,
> Christopher
>
Re: [PROPOSAL] Send build notifications to notifications list
Posted by Enrico Olivelli <eo...@gmail.com>.
Christopher,
Il giorno mer 18 mar 2020 alle ore 22:25 Christopher
<ct...@apache.org> ha scritto:
>
> Hi ZK Devs,
>
> I have been trying to watch the ZooKeeper developer list lately, to
> stay on top of latest issues, and to contribute in whatever small way
> I can. However, I noticed the list gets a lot of spam from automated
> notifications (especially Jenkins).
>
> This has the effect of drowning out conversation between actual
> humans, and can discourage participation, because it requires new
> subscribers to set up a bunch of filters to suppress these, if they
> don't want to see them (and they may unintentionally suppress human
> conversation, if they don't set up their filters perfectly).
>
> What do the ZK committers/PMC members think about having Jenkins send
> build notifications to the notifications@ list instead of dev@?
I think it is a very good idea
Enrico
>
> Thanks,
> Christopher