Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-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 763E37F6E for ; Tue, 4 Oct 2011 20:49:44 +0000 (UTC) Received: (qmail 29841 invoked by uid 500); 4 Oct 2011 20:49:44 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 29767 invoked by uid 500); 4 Oct 2011 20:49:43 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 29758 invoked by uid 99); 4 Oct 2011 20:49:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Oct 2011 20:49:43 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of simone.tripodi@gmail.com designates 209.85.160.171 as permitted sender) Received: from [209.85.160.171] (HELO mail-gy0-f171.google.com) (209.85.160.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Oct 2011 20:49:38 +0000 Received: by gyh3 with SMTP id 3so1672828gyh.30 for ; Tue, 04 Oct 2011 13:49:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=ADUnqxtzstMZIDxW68UKEFK+nM3IY59aPfiUVgvZbCg=; b=PoHBDR5ZbIu+qs+JrwPOUEveErWGP3KT1oXtsX+mBFs1oMN4rUL7MyqIv9FcWQtXGW rJwDrvV6owm5fFr1aFRiEsWiiuHFGPj3/OjBvmUjOKkxNCmv2vrKhF/UwKXWMesYo7GX MSdNQIsG7W1yhMWzIrOyYl+WhFojClbjRCSX4= MIME-Version: 1.0 Received: by 10.150.95.12 with SMTP id s12mr1707943ybb.436.1317761357541; Tue, 04 Oct 2011 13:49:17 -0700 (PDT) Sender: simone.tripodi@gmail.com Received: by 10.151.39.2 with HTTP; Tue, 4 Oct 2011 13:49:17 -0700 (PDT) In-Reply-To: References: Date: Tue, 4 Oct 2011 22:49:17 +0200 X-Google-Sender-Auth: KRVc2SgEjQCQXG1Gb_Pi4OCa-Og Message-ID: Subject: Re: [ALL] Tip for commit comments matching JIRA tickets. From: Simone Tripodi To: Commons Developers List Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org Very nice! I used to add the issue key in the ci comment[1], but didn't notice the activity on Jira before you notified :P For OGNL, we have also the JenkinCI JIRA plugin that, based on getting the issue id between [] in the ci message, adds a comment to the issue, notifying in wich build the commit is integrated. Thanks! Simo [1] https://issues.apache.org/jira/browse/CHAIN-60 http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Oct 4, 2011 at 10:36 PM, Gary Gregory wrote: > Hi All: > > If you include the JIRA [issue] in your commit comment, for example > "[IO-284] super duper", you will see it in JIRA under the tab "Subversion > Commits". > > For example: > https://issues.apache.org/jira/browse/IO-284?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel#issue-tabs > > This is a super duper feature. > > -- > E-Mail: garydgregory@gmail.com | ggregory@apache.org > JUnit in Action, 2nd Ed: http://bit.ly/ECvg0 > Spring Batch in Action: http://bit.ly/bqpbCK > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org