So I have been using Jenkins for a couple of years to periodically run
some etl/batch jobs. Most of the jobs are simple enough that I just
need a groovy script or two to take care business. So anyway, I am
starting to get requests to start dealing with real time data from
JMS. The data processing is fairly simple, and Jenkins has been a
life saver for notification, logging and its restful api. If I were
to do what I need to consume and process data from a message queue, I
basically would be creating a crappy version of Jenkins. So I
thought, why not extend Jenkins? So here's my proposed use case...
please tell me if this is insane. I was thinking I could make a JMS
trigger that can fire off a job if messages are in a queue; the job
would run until all messages have been consumed. I haven't seen
anyone do this so I wonder if this is beyond the scope of
Jenkins.
