Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5FF0B2009E2 for ; Wed, 1 Jun 2016 17:23:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5E37E160A4C; Wed, 1 Jun 2016 15:23:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CC7BE160A45 for ; Wed, 1 Jun 2016 17:23:07 +0200 (CEST) Received: (qmail 68783 invoked by uid 500); 1 Jun 2016 15:23:06 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 68771 invoked by uid 99); 1 Jun 2016 15:23:06 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jun 2016 15:23:06 +0000 Received: from dhcp-202.private.iobm.com (nat.iobm.com [64.142.69.92]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 3C0D71A0175; Wed, 1 Jun 2016 15:23:06 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: [DISCUSS] Replacing the automatic Jenkins jobs with Apache Yetus qbt From: Allen Wittenauer In-Reply-To: Date: Wed, 1 Jun 2016 08:23:05 -0700 Cc: Hadoop Common Content-Transfer-Encoding: quoted-printable Message-Id: References: <93F843D2-EAEA-492B-9180-4F2ACCCEC5F2@apache.org> To: Andrew Wang X-Mailer: Apple Mail (2.3124) archived-at: Wed, 01 Jun 2016 15:23:08 -0000 > On May 31, 2016, at 8:53 PM, Andrew Wang = wrote: >=20 > I'm in favor of something that helps unify the current mess of Jenkins > jobs. We do something similar for our internal Hadoop repo: each = branch has > a "build.sh" and "test.sh" script that builds and then runs the tests. = This > predates Yetus, else we'd probably have used that. So +1 from me. >=20 > One thing I also find really helpful is riding over flaky tests, = perhaps > via: >=20 > = http://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-fail= ing-tests.html >=20 > This would be great for precommit too, since right now someone has to = run > the failed tests locally to confirm they're flakes. >=20 > Even better is then feeding the success/failure into a DB so you can = track > flaky rates over time, which helps you prioritize which flaky to fix = first, > and helps you find the change which caused the flakiness. Appy over in HBase-land has added flaky detection and the = ability to track and ignore them to their Yetus personality. At some = point, I=E2=80=99m sure we=E2=80=99ll see that code float upstream in a = more generalized manner as they get more experience with it.=20= --------------------------------------------------------------------- To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-dev-help@hadoop.apache.org