Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-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 85E32D76D for ; Fri, 8 Mar 2013 14:33:28 +0000 (UTC) Received: (qmail 11171 invoked by uid 500); 8 Mar 2013 14:33:28 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 11069 invoked by uid 500); 8 Mar 2013 14:33:27 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 11058 invoked by uid 99); 8 Mar 2013 14:33:27 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Mar 2013 14:33:27 +0000 Received: from localhost (HELO mail-ie0-f182.google.com) (127.0.0.1) (smtp-auth username nslater, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Mar 2013 14:33:26 +0000 Received: by mail-ie0-f182.google.com with SMTP id k14so2074998iea.41 for ; Fri, 08 Mar 2013 06:33:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:content-type:x-gm-message-state; bh=osafUWB+V+dZdYkGEX8cOrATHxNXgFfX0y1CON8mVBA=; b=c8P2/LpO0bk57FeBCZDXzBadcyTIl3HtSJQAF5M4jtDuS2IaQ9TLCFo4Hdmvqf/00Z zhNxhKAb8f6Osbr+1eTU6PPfxClZMC+eOGSG5agM0SWm+Wry9PM6o/jic/zJOFyPOLg4 VOhVuITi7rHu+nZ2p3TmSFrvGNqLrwNJ+c9mHx9DD2G9OthtsvdukxYgWHnPeD4xue4I 5w4aAoxrsJPKHEG9u1BtCqDPPNW/gK7E1VaX2ubfWnttokrLUSrnlDZHhdnvtOzLlses WTaLHCOScP8Mk2FqfbFM5gUR+T77USGOoHpCM/DnP5upp2sqnc8LbRgliNXx0pJCmy8P RGog== MIME-Version: 1.0 X-Received: by 10.50.40.162 with SMTP id y2mr1789985igk.65.1362753206055; Fri, 08 Mar 2013 06:33:26 -0800 (PST) Received: by 10.50.188.202 with HTTP; Fri, 8 Mar 2013 06:33:25 -0800 (PST) X-Originating-IP: [178.250.115.206] In-Reply-To: References: <-5967924796032764696@unknownmsgid> <4050D7A2-9975-41D5-99D5-95FC38823693@gmail.com> Date: Fri, 8 Mar 2013 14:33:25 +0000 Message-ID: Subject: Re: GIT & JIRA integration! From: Noah Slater To: "cloudstack-dev@incubator.apache.org" Content-Type: multipart/alternative; boundary=14dae9341283c396e104d76ab4eb X-Gm-Message-State: ALoCoQm1oF6wMrmb/UWKXVwod2JcrVINeoQcKeK/++8UBwYMayaJaXPC0WIuENiWaf1+0ttk5Vhb --14dae9341283c396e104d76ab4eb Content-Type: text/plain; charset=ISO-8859-1 Sebastien, I am not sure. I would suggest you post an email to infrastructure@apache.org about it. Alex, I would be very cautious about doing that. Infra have certain rules about the types of automated services which can interact with things like the mailing list and JIRA. I would post a proposal to infrastructure@apache.org before you do anything. On 8 March 2013 05:49, Alex Huang wrote: > Here's my suggestion on doing something like this. > > Basically, everything that happens on the mailing list and we have pretty > good conventions. We can do the following things. > > - Setup an mta. > - Register an email with mailing list, jira, review board, and maybe even > wiki. > - upon receiving emails, the mta agent sends it to scripts that parse out > the necessary information and call the appropriate apis on jira, review > board to record the information. > > With this no hooks at all. We can circumvent the reliance on asking > apache infra on doing this work. All they really need to do is give us a > vm with a public ip address. > > Anyone good with setting up an mta without call outs to do this? > > --Alex > > > -----Original Message----- > > From: Sebastien Goasguen [mailto:runseb@gmail.com] > > Sent: Thursday, March 7, 2013 1:50 AM > > To: cloudstack-dev@incubator.apache.org > > Subject: Re: GIT & JIRA integration! > > > > Is it possible to integrate with review board as well. > > > > When a patch is applied, comments gets in JIRA and review gets shipped > and > > submitted ? > > > > > > On Mar 6, 2013, at 6:07 PM, Noah Slater wrote: > > > > > Nope! I meant this for CloudStack. I just used a CouchDB ticket as a > demo! > > > > > > I think this may be old news for you guys though... > > > > > > > > > On 6 March 2013 22:59, Chip Childers > wrote: > > > > > >> Did you mean this for couchdb? > > >> > > >> On Mar 6, 2013, at 5:32 PM, Noah Slater wrote: > > >> > > >>> Devs, > > >>> > > >>> We have GIT & JIRA integration. > > >>> > > >>> When making a checkin, simply mention any tickets by ticket number. > > >>> The checking will generate a comment on the tickets you mention. > > >>> > > >>> Here's an example: > > >>> > > >>> https://issues.apache.org/jira/browse/COUCHDB-1418 > > >>> > > >>> I'm going to ask Infra if they can let us close tickets, etc, from > > >>> commit messages. If you have any requests, let me know here, and I > > >>> will gather them up. > > >>> > > >>> Thanks, > > >>> > > >>> -- > > >>> NS > > >> > > > > > > > > > > > > -- > > > NS > > -- NS --14dae9341283c396e104d76ab4eb--