From owner-freebsd-testing@FreeBSD.ORG Thu May 21 06:34:57 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 33C8F363; Thu, 21 May 2015 06:34:57 +0000 (UTC) Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) (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 DF32516D4; Thu, 21 May 2015 06:34:56 +0000 (UTC) Received: by ieczm2 with SMTP id zm2so1420074iec.1; Wed, 20 May 2015 23:34:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=5tBrjP/jUajyWqoTbFdo0d06KUcjHGkGahtR7ryBovw=; b=w/3gofwv9gVjxJsnwpPECd/2JztVbcUFN9pZxWHMaTX2AhWaxhG3BJ/OLWXTRzTnnL 3d63UdHlaX19obAL8XtteRFNNdhk1bwK3sPWmGWninN41+7ivjBgMjZk+ba5WdKOfIWr fVl9pXWuSgnH3fainhWmcm/6//sj8xdesqdVKEOjfBJXYQuCyyXocrqdEKEn8Kq9IKLC hgc0f+FuicEJNOT20wYl3IR1xWW65Lq1JwKPaOais9ZmNIZyJNiHSsunxs0qHZS/dlxj r7FYWmJttbf2Xg+dlLo/r0e1eLjiOplGZlR5g78xX7JcuVAk74szD2McWx+tQ4ukgfAo m5ug== X-Received: by 10.107.165.206 with SMTP id o197mr1420121ioe.56.1432190095934; Wed, 20 May 2015 23:34:55 -0700 (PDT) Received: from ?IPv6:2601:8:ab80:7d6:d5de:dc48:8df9:aa7e? ([2601:8:ab80:7d6:d5de:dc48:8df9:aa7e]) by mx.google.com with ESMTPSA id o15sm501057igw.11.2015.05.20.23.34.53 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 20 May 2015 23:34:55 -0700 (PDT) Subject: Re: Create freebsd-testing-results@ list for Jenkins results? Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_0AE6A284-F859-4544-8E4E-F4BBDB8AE04E"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b6 From: Garrett Cooper In-Reply-To: Date: Wed, 20 May 2015 23:34:50 -0700 Cc: "freebsd-testing@freebsd.org" , "jenkins-admin@freebsd.org" Message-Id: References: <56800B8F-E49D-4B8E-B975-EB16299C0028@gmail.com> To: Craig Rodrigues X-Mailer: Apple Mail (2.1878.6) 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 06:34:57 -0000 --Apple-Mail=_0AE6A284-F859-4544-8E4E-F4BBDB8AE04E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On May 20, 2015, at 23:32, Craig Rodrigues wrote: > Hi, >=20 > Yes, I am opposed to this. >=20 > 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. >=20 > 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. >=20 > At this link: > https://www.freebsd.org/doc/en/books/handbook/current-stable.html >=20 > 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. >=20 > 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. >=20 > So freebsd-current@ is used to notifiy committers *and* non-committers > about the > state of the branch. >=20 > 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. >=20 > So Jenkins is doing its job, even if it annoys some people and makes = some > people > like Steve Kargl unhappy. >=20 > 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. >=20 > No matter what, you can't make everyone happy with build break = e-mails. >=20 > However, pushing them off to the side is not the direction we should = be > going in. Right. The only thing is that it=92s a bit easier to parse out = test break emails if they all went to a single email list. I=92d love to = do this personally, but I see pros and cons for this approach. Thanks :)! -NGie --Apple-Mail=_0AE6A284-F859-4544-8E4E-F4BBDB8AE04E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJVXXyLAAoJEMZr5QU6S73enlEH/imFdjeEdfcTbADTm0o6wkdW Zk9kKf+e6r4LRm8zhF+PhIqCPQtH9+BFjBwyamRBAbKRJR/MSeVUIvv4SIxn1jsv WWcr20bhWwRzk5YEjVdFTPfCoCRPHOAO2uDeuGIHRr3YaU2GtSvtpR/uyOuppgGj Jz+KH98nYHJ4X1EuSL8+q1+DNvVtIM4YUL5PFjXFlIL2S+knIpZHn3IHMu7h8D3I XZIrAQNqntDd/fRnXxP2QLr578bJfSA6Y5q/PpGyXrt2IWbFD2AWM+yn7gBI8nAV Ze3sOtKiD7YJa9A9wANTAUMlfxd3zvyXfqqpQ8PZEIqOfixHH6jMGNFsqP/O+e0= =KIrH -----END PGP SIGNATURE----- --Apple-Mail=_0AE6A284-F859-4544-8E4E-F4BBDB8AE04E--