From owner-freebsd-testing@freebsd.org Mon Jul 6 02:49:22 2015 Return-Path: Delivered-To: freebsd-testing@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B70C298E737 for ; Mon, 6 Jul 2015 02:49:22 +0000 (UTC) (envelope-from xmj@freebsd.org) Received: from dd16522.kasserver.com (dd16522.kasserver.com [85.13.137.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7E5A91F12; Mon, 6 Jul 2015 02:49:22 +0000 (UTC) (envelope-from xmj@freebsd.org) Received: from mx12.chaot.net (82.131.84.115.cable.starman.ee [82.131.84.115]) by dd16522.kasserver.com (Postfix) with ESMTPSA id C647F456019; Mon, 6 Jul 2015 04:49:17 +0200 (CEST) Received: from mx12.chaot.net (localhost [127.0.0.1]); by mx12.chaot.net (OpenSMTPD) with ESMTP id 664ce7e8; Mon, 6 Jul 2015 05:49:16 +0300 (EEST) Message-ID: <5599ECAC.5000809@FreeBSD.org> Date: Mon, 06 Jul 2015 05:49:16 +0300 From: Johannes Jost Meixner Reply-To: xmj@chaot.net User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Craig Rodrigues CC: "freebsd-testing@freebsd.org" Subject: FreeBSD Jenkins build Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit 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: Mon, 06 Jul 2015 02:49:22 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Craig, Mark Linimon said you'd be the person to contact to, in this case, so here goes! I'm still trying to find a way how I could contribute best to the FreeBSD testing team. I'm subscribed to the testing@ list, so I see all the errors passing through, and people getting annoyed that they do receive error mails for things they break... ;-) and I can't quite figure out what's actually left to do, or what's on the roadmap for testing, or what's planned. Starting with the easy things: I've done ok with Jenkins in the past, and will get around to setting up and re-configuring a few instances for my clients. How do I help with the FreeBSD Jenkins instance? Do we have documentation on how it's set up? I'm not only talking Configuration management script - that would be very useful, too. I'm mainly talking about a page (wiki entry, etc) that we can list TODO items, ideas, already implemented things, etc. Best Johannes - -- Johannes Meixner | FreeBSD Committer xmj@FreeBSD.org | http://people.freebsd.org/~xmj -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVmeykAAoJEPyeKTcbGw0Lj7cH/0bmWdLX9yf747YuSTztQt4D 4YZApK/CtmhA9gmoMlUKj6IftQhyYS++HPgptBQ2ZOeAma5LZ9YSN73yTggt6/CX K4u6H7AQYfD9pWEVoLiCKF0Q8mahF0QKiFbCzsPn3mmd7Fj/5A2ANFdbs6S/CAU5 R3P8oxsrB1f4Z9gAlUt70Vg8Gm5kXoTtOCSulLB/JbSDCz4uuwH/TzrpliOTvA9q F5+Iz0TRv0NDc2rQpZTPWW5iRIHdI7Z1hlQPElNgTRd+PzGAyyYUXFcLV7AAw4Ma BOE1Tvm5+VsVzwv2IPKmBKRCgy2F+WGAuIS5q1qVrAvEGqH8oH34W1AS2uVP0hk= =7gAQ -----END PGP SIGNATURE-----