The project is in a healthy, maintained state
A Resque gem for executing batches of jobs in stages. All jobs in a stage must complete before any job in the next stage is started allowing you to be sure that jobs are not executed out of sequence.
 Project Readme


A Resque plugin for executing jobs in stages. Groups are created each with multiple stages. Each stage contains a number of Jobs. All jobs within a stage must complete before the next stage is executed. What makes this gem special is that it will wait for jobs to Retry before they are considered complete and the next stage will be executed.

Once all jobs in all stages are complete, the stages and jobs are all deleted - cleaning up after itself.


Add this line to your application's Gemfile:

gem 'resque-stages'

And then execute:

$ bundle install

Or install it yourself as:

$ gem install resque-stages


###Basic Usage

Include the stages plugin in all jobs that will be enqueued as a part of a Stage. Do not worry, you will not have to enqueue the job only as part of a stage. You will be able to use the job inside of or outside of a stage.

This gem will enqueue a job with extra paramters when it is enqueued as a part of a stage. To support this, the perform_job method is added to your class and it will return an object which will have the un-altered arguments for the job - whether or not the job is called with the extra parameters.

class MyJob
  extend Resque::Plugins::Retry
  include Resque::Plugins::Stages
  def perform(*args)
    job = perform_job(*args)

  # The "old" perform function can be called here as-is because the
  # perform_job will always ensure that the original parameters are called
  def real_perform(my_param_1, my_param_2)

To create a grouping of stages and execute the jobs, you then create a group and the stages you need in it:

def enqueue_stages
  Resque::Plugins::Stages::StagedGroup.within_a_grouping do |grouping|
    stage = grouping.stage(1)
    12.times do |index|
      stage.enqueue MyJob, index, "parameter"

    stage = grouping.stage(2)
    stage.enqueue MyJob, -1, "summary"

within_a_grouping will initiate the first stage when it completes. This will cause all jobs in stage 1 to complete before stage 2 executes.

NOTE: All jobs and stages in a grouping are kept until the last job in the last stage completes so that you can query the jobs to find out which ones completed successfully and which ones failed.

To aid in querying information about the jobs in a stage, each job includes a single string value status_message which can be set at any time and will be available until all jobs are completed.

###Compatibility with other Resque Plugins

In general, this plugin should be compatible with other gems. Some special notations on specific compatibility should be made.

resque-compressible - Special code has been added to ensure compatibility with this gem and compressed jobs. The only condition for this to work properly is that the Resque::Plugins::Stages gem must be included AFTER the Resque::Plugins::Compressible gem is extended so that the code knows that it needs to accomidate resque-compressible.

resque-retry - Special code has been added to ensure compatibility with this gem and Retryable jobs. When a job is retried, we know it and mark the status of the job with a special status indicating that the job is pending being retried. When enqueued, if the job is pending a retry, the pending job is enqueued, not a new copy of the job. The only condition for this to work properly is that the Resque::Plugins::Stages gem must be included AFTER the Resque::Plugins::Retry gem is extended so that the code knows that it needs to accomidate resque-retry.

resque-job_history - No special code has been added for this gem, but this gem and gems like it (resque-cleaner, resque-history, etc.) which record the parameters for a job and allow it to be re-enqueued all have the same/similar potential problem of enqueueing a job with outdated job IDs because we include the job ID in the enqueued job. If this happens and you use the perform_job method as described, there will be no problem. A temporary job with a nil staged_group_stage will be created and the params will be available as always.

resque - Enqueuing jobs directly. If you enque a job that is staged through Resque itself, the job will still work as designed if you properly use the perform_job method as described. It will recognize that there is no actual job and create a temporary one with the right parameters for you to use.


StagedJob - A job that is a part of a Stage

The Staged Job is the job which has been enqueued and using the perform_job will be available to you within your perform method.

job = perform_job(*args)

job.args               # The original args to the job
job.blank?             # true if there is no job or stage/grouping etc.
job.staged_group_stage # The stage that the job is a part of.
job.status             # The status of the job
                       # Valid statuses:
                       #    :pending
                       #    :queued
                       #    :running
                       #    :pending_re_run
                       #    :failed
                       #    :successful
job.status_message     # A message that you can set on the job
job.class_name         # The name of the jobs class
job.queue_time         # The time that the job was initially enqueued
job.delete             # Delete the job.  It may remain in the Resque queue
job.enqueue_job        # Enque the job (Will enqueue from the delay queue if retrying)
job.completed?         # True if the job is :failed or :successful
job.queued?            # True if the job has been queued to Resque
job.pending?           # True if the job is :pending or :pending_re_run

# To get the group so you can see other stages: 

StagedGroupStage - A Stage that is a part of a Group (contains Jobs)

job = perform_job(*args)
stage = job.staged_group_stage

## OR
stage = group.stage(1)

stage.enqueue                 # Add a job to a stage
stage.enqueue_to              #   If a stage is running, then
stage.enqueue_at              #   the job is enqueued immediately
stage.enqueue_at_with_queue   #   using the enqueue method specified
stage.enqueue_in              #   otherwise it is simply enqueued
stage.enqueue_in_with_queue   #   when the stage is initiated
stage.status                  # The status of the stage
                              #   Valid statuses:
                              #     :pending
                              #     :running
                              #     :complete
stage.number                  # The stages number
stage.staged_group            # The group the stage belongs to
stage.jobs                    # The jobs for the stage in the order they
                              #   were enqueued
stage.num_jobs                # The number of jobs in the stage
stage.delete                  # Delete the stage
stage.initiate                # Enqueue all jobs in the stage.
                              #   Once all jobs compelte, the next stage
                              #   will be initiated.
stage.blank?                  # Returns true if the stage does not really exist.

StagedGroup - A group of stages

Resque::Plugins::Stages::StagedGroup.within_a_grouping("description") do |group|
  group.initiate      # Find the next stage that is not complete and initiate it
  group.description   # The description that was provided for the group
  group.created_at    # The date/time that the group was created.
  group.current_stage # The first non-complete stage.
  group.stage(number) # The indicated stage.  Will create a stage if none found.
  group.stages        # A hash of all of the stages.  The stage numbers
                      #   will be the key values.
  group.delete        # Delete the group and all stages and jobs.
  group.blank?        # Returns true if the group is not saved

Cleaner - A cleaner utility class for fixing up mixed up jobs

Resque::Plugins::Stages::Cleaner.purge_all    # delete all values from Redis
Resque::Plugins::Stages::Cleaner.cleanup_jobs # Create any stages or groups
                                              #  needed for orphaned jobs.



Pending Job Details


Pending Job Details


Pending Job Details


Pending Job Details


After checking out the repo, run bin/setup to install dependencies. Then, run rake spec to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.


Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/resque-stages. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.


The gem is available as open source under the terms of the MIT License.

Code of Conduct

Everyone interacting in the Resque::Stages project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.