From owner-freebsd-testing@FreeBSD.ORG Thu May 21 14:46:18 2015 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 09EB4D96; Thu, 21 May 2015 14:46:18 +0000 (UTC) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C27FE16DE; Thu, 21 May 2015 14:46:17 +0000 (UTC) Received: by oihd6 with SMTP id d6so19152622oih.2; Thu, 21 May 2015 07:46:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=zBj5Pidb0fLhDks4utAFUN0cwTUPSYuL4lwEB5HR4bI=; b=ppkEYHftIYDiU630PsyvYK/hRw24tvnIycnquv/n9Jme6LXUjz2C938ll7GZkCeZFN GUB/wKsHvXdfXvzgRkuLy4/dOURmOG7ewYJTF/k+qzof7kxELuy9XDb7heh+MBm4q9QV 02wLkPhy21k1zzvSKpfWuYqA4KANERJNTWddIxhNPGK29g7F9VerxqaFBYr9QNuGVJkc lzOgBi2MYjv/BwaoQpbHDxFc7gCVCWnvGb72oEGuIZFPIHyW7q9u/Kf/KhtezBd5F/X7 Qfgb4WtCehuJJMoMlbBJecaSzhVKXluLdvvNU/U+4wQfGWNFo1L1LB+VThpexAl7qpOI m9Qw== MIME-Version: 1.0 X-Received: by 10.60.81.98 with SMTP id z2mr2611477oex.37.1432219577140; Thu, 21 May 2015 07:46:17 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.173.204 with HTTP; Thu, 21 May 2015 07:46:17 -0700 (PDT) In-Reply-To: References: <56800B8F-E49D-4B8E-B975-EB16299C0028@gmail.com> Date: Thu, 21 May 2015 08:46:17 -0600 X-Google-Sender-Auth: 1rAcZJkS-1vWnW8UOxSoIgGircY Message-ID: Subject: Re: Create freebsd-testing-results@ list for Jenkins results? From: Alan Somers To: Craig Rodrigues Cc: "freebsd-testing@freebsd.org" , "jenkins-admin@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2015 14:46:18 -0000 I completely agree with Craig. Please do keep annoying people on the freebsd-current list. But also please snip the messages down to a shorter length. -Alan On Thu, May 21, 2015 at 12:32 AM, Craig Rodrigues wrote: > Hi, > > Yes, I am opposed to this. > > The minute you push these email notifications to a separate list, > then the whole utility of Jenkins goes down, because most people won't > be subscribe to the list. > > The whole point of running a CI system like Jenkins is to unfortunately be > a bit annoying > and "in your face". FreeBSD doesn't have a QA department to triage > failures and notify > developers, so sending e-mails to > targeted lists is important. As it is, FreeBSD people don't subscribe to > all the same lists, so no matter what, > you can't make everyone happy. > > At this link: > https://www.freebsd.org/doc/en/books/handbook/current-stable.html > > it mentions that bulletins about the state of the FreeBSD-CURRENT branch > go to the freebsd-current@ list. So that's why it is OK for e-mail > notifications > from the old Tinderbox or Jenkins to go to that list. > > I have received e-mails privately thanking me for setting this stuff up. > Some folks (who are not FreeBSD committers) monitor lists like > freebsd-current@, > and when they see Jenkins failure e-mails > on the list, that gives them a clue that they should hold off on updating > the tree. > > So freebsd-current@ is used to notifiy committers *and* non-committers > about the > state of the branch. > > jenkins is already configured to send e-mails to several lists, such as > freebsd-current, freebsd-stable, freebsd-doc, freebsd-i386, depending on > the build job, > so we don't send every e-mail to freebsd-current for all the builds that we > do. > > So Jenkins is doing its job, even if it annoys some people and makes some > people > like Steve Kargl unhappy. > > What we can consider doing is reducing the number of lines in the e-mall > notification, > to prevent very large e-mails from being sent to the list. There may be > tunables > in Jenkins that we can look at for this. That is worth exploring. > > No matter what, you can't make everyone happy with build break e-mails. > > However, pushing them off to the side is not the direction we should be > going in. > > -- > Craig > > > On Wed, May 20, 2015 at 10:46 PM, Garrett Cooper > wrote: > >> Hi all, >> As some know who are subscribed to freebsd-current, the list gets >> spammed a lot with test results (pass/fail transitions mostly) for the >> Build_Image_and_Run_Tests_in_Bhyve_HEAD job. I was wondering if anyone >> would be opposed to creating another list to capture the results, e.g. >> freebsd-testing-results@FreeBSD.org, and if so, would you subscribe to >> the list? >> Thanks! >> -NGie >> > _______________________________________________ > freebsd-testing@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-testing > To unsubscribe, send any mail to "freebsd-testing-unsubscribe@freebsd.org"