Return-Path: X-Original-To: apmail-streams-dev-archive@minotaur.apache.org Delivered-To: apmail-streams-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 08FC810AE1 for ; Mon, 24 Feb 2014 17:37:32 +0000 (UTC) Received: (qmail 73314 invoked by uid 500); 24 Feb 2014 17:37:31 -0000 Delivered-To: apmail-streams-dev-archive@streams.apache.org Received: (qmail 73264 invoked by uid 500); 24 Feb 2014 17:37:31 -0000 Mailing-List: contact dev-help@streams.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@streams.incubator.apache.org Delivered-To: mailing list dev@streams.incubator.apache.org Received: (qmail 73256 invoked by uid 99); 24 Feb 2014 17:37:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Feb 2014 17:37:31 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 24 Feb 2014 17:37:25 +0000 Received: (qmail 73134 invoked by uid 99); 24 Feb 2014 17:37:05 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Feb 2014 17:37:05 +0000 Received: from localhost (HELO mail-ve0-f182.google.com) (127.0.0.1) (smtp-auth username sblackmon, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Feb 2014 17:37:05 +0000 Received: by mail-ve0-f182.google.com with SMTP id jy13so6256793veb.27 for ; Mon, 24 Feb 2014 09:37:04 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=nrC9MdCDkG8PMmuWX7adwKQ06BR+3GOBtvTJUic4Mwc=; b=YUvTCqfqestV20CdJyDIbv9E+1a2U/1WUIgL3cnrH2bJgI/fXosl67bOZJYmWb3rww ltE8OFTcadtgXtc4lGKH3TaM8igtc/FxCogeG1QDMkXpUC18N04jR86jYzf0VUOESi41 JK6sHUtDuZJXGj1NPD1rERjurNRnl3ylOt56BVCvo6L525SXi+VgoAQohTHWz8WzBeyC /iP/jAHFt9Y9Qv+oWDZe487OaXyELzbD4PeZ9ReombgCSUUu3g/ORI+LUJD6hZOHB9Wv DiNjaqO40oNLtntFlufpj9aJJypgQ/d1T1Vp9XCwRwYk5Tis63HIFD9ylmRT8ILMihu1 p4UA== X-Gm-Message-State: ALoCoQmp4E7bLqpF+AbXUSvne3cdgCalCLSOYTJadtZRgfZOxkaguKkPZlmCnmow5PGot5qzEguq MIME-Version: 1.0 X-Received: by 10.52.189.33 with SMTP id gf1mr11460653vdc.26.1393263424045; Mon, 24 Feb 2014 09:37:04 -0800 (PST) Received: by 10.220.107.75 with HTTP; Mon, 24 Feb 2014 09:37:03 -0800 (PST) X-Originating-IP: [204.57.79.12] In-Reply-To: References: Date: Mon, 24 Feb 2014 11:37:03 -0600 Message-ID: Subject: Re: Build failures From: Steve Blackmon To: dev@streams.incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org It would be nice to have a way to place feature branches we are planning to merge under automated build as well, not to publish any artifacts necessarily, just to identify any breaking changes and track how many and which modules and tests are active/passing. STREAMS-26 is a good example we could use to test this process out. Steve On Mon, Feb 24, 2014 at 11:03 AM, Stanton Sievers wrote: > Can you help set that up? I've never setup snapshots in the builds.a.o > environment before. Certainly willing to learn. :) > > > On Mon, Feb 24, 2014 at 11:49 AM, Matt Franklin wrote: > >> On Mon, Feb 24, 2014 at 10:46 AM, Stanton Sievers > >wrote: >> >> > A new job [1] has been created on builds.a.o for Streams trunk. It will >> > build using JDK 1.7 and the latest maven (currently 3.0.5). Once I've >> > verified it builds successfully, I'll set the job to e-mail this list >> when >> > builds fail. >> > >> > We can setup snapshot deploys and other CI functionality as we see fit. >> > >> >> Let's setup snapshots now. >> >> >> > >> > [1] https://builds.apache.org/job/Streams%20Trunk/ >> > >> > >> > On Mon, Feb 24, 2014 at 11:39 AM, Matt Franklin < >> m.ben.franklin@gmail.com >> > >wrote: >> > >> > > > >> > > > If we can revert trunk to revision 1569602, it should build again >> with >> > > >> all modules in the build plan. >> > > >> >> > > > >> > > > I will revert the code. >> > > > >> > > >> > > This is done. >> > > >> > >>