Daniel Gruno wrote on Fri, Jan 25, 2013 at 15:52:17 +0100:
> On 01/25/2013 03:40 PM, Andrew Stitcher wrote:
> > On Fri, 2013-01-25 at 07:20 +, Tony Stevenson wrote:
> >> Andrew,
> >>
> >> The reason the SVN integration was dropped was because the code that runs
> >> that module was extremely i
On Fri, Jan 25, 2013 at 6:52 AM, Daniel Gruno wrote:
> 4) Use JIRA's REST API to post a comment in the appropriate JIRA ticket.
Will adding to the comment load like this speed the day when the ASF's
gigantic monolithic JIRA instance topples over from sheer size?
(The "JIRApocalypse"?)
Marvin H
Andrew,
The reason the SVN integration was dropped was because the code that runs that
module was extremely inefficient.
We submitted a patch to Atlassian, which to my knowledge still has yet to be
applied, and until it is we cannot run it as the current code cannot cope with
a repo of >=1.4m
On 24.01.2013 22:04, Andrew Stitcher wrote:
Last July (2012) The Jira subversion integration was disabled.
Speaking personally (and I expect for a good number of members of the
qpid team) I'm finding it much harder to follow jiras into the changes
that relate to them.
Indeed, previously Qpid pu
if you are using Jenkins, you can activate the jira plugin.
This will add comment to your jira entry as this sample:
https://issues.apache.org/jira/browse/MTOMCAT-185?focusedCommentId=13497111&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13497111
note you must add
On 01/25/2013 03:40 PM, Andrew Stitcher wrote:
> On Fri, 2013-01-25 at 07:20 +, Tony Stevenson wrote:
>> Andrew,
>>
>> The reason the SVN integration was dropped was because the code that runs
>> that module was extremely inefficient.
>> We submitted a patch to Atlassian, which to my knowledg
On Fri, 2013-01-25 at 07:20 +, Tony Stevenson wrote:
> Andrew,
>
> The reason the SVN integration was dropped was because the code that runs
> that module was extremely inefficient.
> We submitted a patch to Atlassian, which to my knowledge still has yet to be
> applied, and until it is we
Last July (2012) The Jira subversion integration was disabled.
Speaking personally (and I expect for a good number of members of the
qpid team) I'm finding it much harder to follow jiras into the changes
that relate to them.
Indeed, previously Qpid put in place a policy that led to most Qpid
chec
