I think that's a jenkins thing. Let me poke around.
On Wed, May 29, 2013 at 5:57 PM, Keith Turner <[EMAIL PROTECTED]> wrote:
> On Wed, May 29, 2013 at 2:12 PM, Drew Farris <[EMAIL PROTECTED]> wrote:
> > Looks like this is set up -- anyone want to give it a whirl?
> Its working. See ACCUMULO-1470. Now how do we turn of the jira updates
> from the build server?
> > ---------- Forwarded message ----------
> > From: #asfinfra IRC Bot (JIRA) <[EMAIL PROTECTED]>
> > Date: Wed, May 29, 2013 at 12:12 PM
> > Subject: [jira] [Commented] (INFRA-6321) svngit2jira for Accumulo
> > To: [EMAIL PROTECTED]
> > [
> > ]
> > #asfinfra IRC Bot commented on INFRA-6321:
> > ------------------------------------------
> > <Humbedooh> All set up, please report back whether this works or not, and
> > I'll close the ticket if it does :)
> > > svngit2jira for Accumulo
> > > ------------------------
> > >
> > > Key: INFRA-6321
> > > URL: https://issues.apache.org/jira/browse/INFRA-6321
> > > Project: Infrastructure
> > > Issue Type: Task
> > > Security Level: public(Regular issues)
> > > Components: Subversion, SvnPubSub
> > > Reporter: Drew Farris
> > > Assignee: Daniel Gruno
> > > Priority: Minor
> > >
> > > * Which project is interested in this service
> > > Apache Accumulo
> > > * Is the project in agreement on using this?
> > > Yes, per discussion on dev list - 4 days elapsed, no dissenters.
> > > * What JIRA name does your project use?
> > > ACCUMULO
> > > * Do you use git or subversion;
> > > Subversion currently, although we are discussing moving to Git.
> > > * How would you like commits to trigger an update of a JIRA ticket
> > > Standard ACCUMULO-1234 will be fine.
> > > * If you are using Git, are there any specific branches you'd like the
> > service to ignore
> > > N/A.
> > --
> > This message is automatically generated by JIRA.
> > If you think it was sent incorrectly, please contact your JIRA
> > administrators
> > For more information on JIRA, see: