Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 53AC317FE3 for ; Tue, 9 Jun 2015 14:33:03 +0000 (UTC) Received: (qmail 53245 invoked by uid 500); 9 Jun 2015 14:33:03 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 53129 invoked by uid 500); 9 Jun 2015 14:33:03 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 52504 invoked by uid 99); 9 Jun 2015 14:33:02 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jun 2015 14:33:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 1C26EC095F for ; Tue, 9 Jun 2015 14:33:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.901 X-Spam-Level: X-Spam-Status: No, score=0.901 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, KAM_LIVE=1, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id CNf8UiWWHK-H for ; Tue, 9 Jun 2015 14:32:53 +0000 (UTC) Received: from mail-la0-f47.google.com (mail-la0-f47.google.com [209.85.215.47]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 3F8D242AD6 for ; Tue, 9 Jun 2015 14:32:53 +0000 (UTC) Received: by labko7 with SMTP id ko7so13823912lab.2 for ; Tue, 09 Jun 2015 07:32:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=t/6963YO8Q0QtHrsU/GcNFRNr3hl6cfn4LgXrxV6DkY=; b=lIXK6lGs6zf9NEKEbpR7GIKtIIJmK4JRNXmhPlZ3j1Xb7G+a0VgrRdiP9Y++Yyx48y G0YngOGktjy/p6aGMkd01K1mBD1UcUcUJbS4jhmcQy2X/5sKX3W782e+PoFkMXXQl6qm 1RodyQ7YXA9BvUsc6sy6iBTrxMeVe4/br5TOCfuAR42PkJ3mNIBbq1407FIy2kEdigMT MoZZGi1lXsyV2kED8UE8YvDO7RXFZaMud4E14WyJ55aGykfSfpUX32423uswTj42xN7o RsD+kBrX8f1UnszYKzSrD6SyMdh/iYjYkspiaR7hF1pBXkOIJl4hQX9lTvcgO9cXPe5a t2wg== MIME-Version: 1.0 X-Received: by 10.152.19.8 with SMTP id a8mr22797126lae.121.1433860327225; Tue, 09 Jun 2015 07:32:07 -0700 (PDT) Received: by 10.25.24.88 with HTTP; Tue, 9 Jun 2015 07:32:07 -0700 (PDT) In-Reply-To: References: <1811551184.15128779.1433770531217.JavaMail.zimbra@redhat.com> <6DAB46EB-91E0-45AE-AA4D-DBC7D4466794@apache.org> <2079974312.15145151.1433771649474.JavaMail.zimbra@redhat.com> <5575C09E.3040000@gmail.com> <506E747B-88D3-4E65-97BB-DD05D9D8B62D@apache.org> <83FD022B-E8AC-47CC-83E4-25516EC24E02@apache.org> Date: Tue, 9 Jun 2015 10:32:07 -0400 Message-ID: Subject: Re: Git workflow for committers From: Clebert Suconic To: "dev@activemq.apache.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > It turns out we didn=E2=80=99t have a build setup for that. We do now. The build I sent you before was a PR build from my own PR. Unless you set it up somewhere. Did you set up a new build for that? On Tue, Jun 9, 2015 at 10:29 AM, Clebert Suconic wrote: >> Well, I fixed that situation this morning. I *THOUGHT* we had a CI bu= ild that was running on master on all commits. That was the expectation a= nd if something broke I would have gotten a =E2=80=9Cthis is broken=E2=80= =9D email within 15 minutes or so. It turns out we didn=E2=80=99t have a = build setup for that. We do now. >> > > I was not being specific about the situation itself.. just finding it > as an example on where the CI build would been useful. > > We have a CI build that run on every Pull Request, not on every commit. > > We have a daily build but they are not as fast on catching issues. > > >>> I'm asking if you could at least send a PR and wait for the build to fi= nish. >> >> How do I do a pull request that doesn=E2=80=99t involve github? I=E2= =80=99m not using github for development. >> > > You really need github for that. You would need a github account > associated with your apache email and send send the PR. > > You don't want to use github at all? If you don't want to use github, > then you certainly won't be able to use these tools. > > Do you have any issues on using github? --=20 Clebert Suconic http://community.jboss.org/people/clebert.suconic@jboss.com http://clebertsuconic.blogspot.com