[Hawkular-dev] Automagic Jira state transitioning (for HAWKULAR-* )

[Heiko W.Rupp]

Last week we were talking about auto-actions in Jira.

This has now been implemented for HAWKULAR-* on all github.com/hawkular 
repos.

See below for a transition that happened when a PR was sent.

I think for this to work, the JIRA state has to be in "Coding in 
progress" already.

   Heiko


Forwarded message:

> From: Anonymous (JIRA) <issues at jboss.org>
> To: hrupp at redhat.com
> Subject: [JBoss JIRA] (HAWKULAR-175) Include bus sample using ActiveMQ 
> virtual topics
> Date: Fri, 8 May 2015 11:26:46 -0400 (EDT)
>
>
>   [ 
> https://issues.jboss.org/browse/HAWKULAR-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel 
> ]
>
> Issue was automatically transitioned when Gary Brown created pull 
> request #17 in GitHub
> ---------------------------------------------------------------------------------------
>  Status: Pull Request Sent  (was: Open)
>
>
>> Include bus sample using ActiveMQ virtual topics
>> ------------------------------------------------
>>
>>              Key: HAWKULAR-175
>>              URL: https://issues.jboss.org/browse/HAWKULAR-175
>>          Project: Hawkular
>>       Issue Type: Task
>>       Components: Bus
>>         Reporter: Gary Brown
>>         Assignee: Gary Brown
>>
>> In standard JMS, for a consuming application to operate in a cluster 
>> to support load balancing and fail over it needs to consume from a 
>> queue.
>> However in some situations, the information being published to that 
>> queue would also be of use for other applications. In this scenario, 
>> it would either be necessary for the producer to know about the 
>> number of consuming apps, and send the message to an individual queue 
>> per app (which makes it difficult to dynamically add further 
>> consuming apps), or switch to using a topic, so the publisher is 
>> independent of the number of consumers (which loses the benefit of 
>> load balanced consumers, as each clustered instance of the app would 
>> perform duplicate processing of the messages).
>> ActiveMQ provides a solution using "virtual topics" where producers 
>> simply publish to a topic (and therefore don't care about the number 
>> of consumers), but the consumers use queues scoped to the application 
>> name - and therefore multiple independent apps can receive the same 
>> message, and also have multiple load balanced instances of the app on 
>> different servers in a cluster.
>> A modified version of the simple MDB sample should be provided to 
>> demonstrate use of this "virtual topic" capability using the standard 
>> JMS APIs.
>> See http://activemq.apache.org/virtual-destinations.html for further 
>> details.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.15#6346)