resque-pagerduty provides a Resque failure backend that triggers a Pagerduty incident when an exception is raised by a job.

Adds persistence to Resque jobs, and retry properties

Resque worker that evaluates queues and chooses which one to pull jobs from

Process Manager For Resque

Adds live GUI queue/worker management to resque-pool

quickly and easily fork a pool of resque workers, saving memory (w/REE) and monitoring their uptime

resque plugin to have priority in the queue

Enable ActiveRecord query cache for Resque jobs

An Active Record model can be defined as 'queueable'. That adds extensions to add any method to the queue that exists on the method instance.

Track jobs processed by queue, longest queue time

Resque Plugin adding simple queue statuses.

The railtie for setup resque. It provides an initializer and rake tasks.

Rake tasks and such for Resque

Super fast evented daemon to process resque jobs, some built in job metrics too, just cause your app might not be on 1.9.1, your bot might be able to

Adds ratchetio as a resque failure backend

A Resque plugin which allows you to create dedicated queues for jobs that use rate-limited APIs. These queues will pause when one of the jobs hits a rate limit, and unpause after a suitable time period. The rate-limited queue can be used directly, and just requires catching the rate limit exception and pausing the queue. There are also additional queues provided that already include the pause/retry logic for Twitter, AngelList and Evernote; these allow you to support rate-limited APIs with minimal changes.

The plugin is designed for sequential running of different jobs in the same queue across multiple queues. Specifically meant for running a variety of long-running background tasks scheduled ahead of time using something like reque-scheduler. May not be suitable for large scale operations.

Allowing Resque to handle queues accross multiple Redis instances

resque plugin that allows you to attach information when a job is put in redis, and to do whatever you want with the information when it is popped off the resque queue

Remotely enqueueing and dequeueing jobs across Redis namespaces should be simpler. BJ Neilsen laid a solid foundation for this gem, which is forked off of his gem resque-remote. That said, these two gems provide a different set of methods for remote enqueueing and dequeueing. If all you need is remote enqueueing within the same namespace, use resque-remote.