Seems like that could potentially be a lot of data in the job body (e.g. a large build.xml file). What about just storing an ID of some kind to the build name - the worker pulls out the build name/ID and then retrieves the actual build.xml from some other shared location. Maybe its stored as a BLOB in a database?
I guess what I am getting at is this: from my perspective I prefer to not treat Beanstalk as a database / datastore - I store just enough information in it that so that my workers know how to process a job and they can retrieve any needed resources on their own. As opposed to chucking the kitchen sink into a Beanstalk body. /Cody On Sat, Jan 9, 2010 at 11:18 AM, Michael <[email protected]> wrote: > My company is trying to determine the best way to store jobs in > beanstalk. Has anyone ever used Phing or Apache Ant to define and > execute jobs? We are considering placing an XML build file in the > body of each job. One caveat could be that a job could have quite a > bit of text for more complex jobs, but we could benefit from using a > pre-built framework for defining and executing tasks. By creating > custom task tags for our application specific jobs, we were hoping to > be able to create highly customizable and succinct job queue messages. > > Does anyone see a drawback to using an Apache Ant / Phing build.xml > type schema for storing jobs in beanstalk? > > -- > You received this message because you are subscribed to the Google Groups > "beanstalk-talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/beanstalk-talk?hl=en. > > > >
-- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
