From owner-freebsd-testing@FreeBSD.ORG  Sun Mar 30 01:17:34 2014
Return-Path: <owner-freebsd-testing@FreeBSD.ORG>
Delivered-To: freebsd-testing@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 796B2CE6
 for <freebsd-testing@freebsd.org>; Sun, 30 Mar 2014 01:17:34 +0000 (UTC)
Received: from mail-vc0-x22e.google.com (mail-vc0-x22e.google.com
 [IPv6:2607:f8b0:400c:c03::22e])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 3B026FFF
 for <freebsd-testing@freebsd.org>; Sun, 30 Mar 2014 01:17:34 +0000 (UTC)
Received: by mail-vc0-f174.google.com with SMTP id ld13so7246474vcb.33
 for <freebsd-testing@freebsd.org>; Sat, 29 Mar 2014 18:17:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=Dn8QLer5pf4ttw3FgUlHS/64IMibkQ7Hu+zIgfol7+A=;
 b=vJq7ATTd+njOXf23SGG4iZ03Jxrq9mPjbCJi7QfGa4vhPsq48agHuSecElGpI1+TI6
 XSp2n96X13lsMvgvtV40gWyHbgW+bC1EI0uUYX252ckS8jqIKDeFdfchzbfN8pDwS79D
 ADTk3dqu72H000uWDiBLg0iMv8X3BSSeFPXh1TG9IDKE0L1k/2ocA8yTYfUqSiG60Jaj
 Jp+FwT11k5MkbwnDlKMom/jjy468yjJFGBhcFuJdhl0hbuF8tiqVs5aJfPwCZAn3Ylan
 EmApbKPJAzvLH/aQdAJX0AhkYmBvXzj5k3dT2eOLEO9BW2lwsGbgXCHl9EfeUYXGRck2
 6aUQ==
MIME-Version: 1.0
X-Received: by 10.52.241.106 with SMTP id wh10mr12683518vdc.16.1396142253250; 
 Sat, 29 Mar 2014 18:17:33 -0700 (PDT)
Received: by 10.220.239.84 with HTTP; Sat, 29 Mar 2014 18:17:33 -0700 (PDT)
Date: Sat, 29 Mar 2014 21:17:33 -0400
Message-ID: <CAB7-odksLQRnma-Bs5zMdZLK-Lu0c8PxBJsyWAQGh3d4qegzrQ@mail.gmail.com>
Subject: Jenkins Dashboard
From: Thomas Hoffmann <trh411@gmail.com>
To: freebsd-testing@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.17
X-BeenThere: freebsd-testing@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Testing on FreeBSD <freebsd-testing.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-testing>, 
 <mailto:freebsd-testing-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-testing/>
List-Post: <mailto:freebsd-testing@freebsd.org>
List-Help: <mailto:freebsd-testing-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-testing>, 
 <mailto:freebsd-testing-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Mar 2014 01:17:34 -0000

Just wanted to say what a great resource the Jenkins Dashboard is for me. I
do near-nightly builds of -CURRENT and having a resource that I can use to
virtually eliminate build false starts is priceless. Today's experience
provides a good example. Just as I was planning for my nightly build, I
noticed that FreeBSD_HEAD #370 failed. Looked in the log to see the error
and offending item. Waited for the item to be fixed (committed to svn).
Waited for build #371 to complete successfully. Proceeded with my nightly
build.

So, I was able to avoid a failed build (false start), avoid needless posts
to the developer on the mailing lists, and avoid opening a needless PR, all
because I knew exactly what was going on.

Had I decided to build anyway. I could have easily checked out up to the
revision causing the problem because I knew which commit caused the build
fail.

One question: are all the FreeBSD_HEAD builds for amd64?

Thanks for this great resource.

-Tom