Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Jan 7, 2015
Commits on Dec 23, 2014
  1. @jzaleski
  2. @jzaleski
  3. @jzaleski
  4. @jzaleski

    Upgrade [some] development gem versions

    jzaleski authored
    * Upgrade `mocha` to '~> 1.1'
    * Upgrade `rake` to '~> 10.3'
    * Upgrade `simplecov` to '~> 0.9'
  5. @jzaleski
Commits on Oct 31, 2014
  1. @jzaleski

    Merge pull request #110 from mindware/patch-1

    jzaleski authored
    Update README.md
Commits on Oct 9, 2014
Commits on Oct 4, 2014
  1. @mindware

    Update README.md

    mindware authored
    Removed the '.rb' from the require in the "Configuring and running the Resque-Web Interface".
Commits on Aug 26, 2014
  1. @mindware

    Update README.md

    mindware authored
    Updating README so that resque-web example also includes comments on where to require worker and application code.
  2. @mindware

    Update README.md

    mindware authored
    Explicitly displaying that user must require his application code when using config.ru.
Commits on Aug 25, 2014
  1. @mindware

    Update README.md

    mindware authored
    Replacing the step-by-step example for using resque-web, to something simpler (while avoiding markdown craziness).
  2. @mindware

    Update README.md

    mindware authored
    Removing breaklines from step-by-step resque-web example
  3. @mindware

    Update README.md

    mindware authored
    Updating the README section on resque-web: rackup example is now mentioned first, and includes a simple example of how to run the server with rackup (with and without bundler). Updated description and tried to clean up the markup for the resque-web section.
  4. @mindware

    Update README.md

    mindware authored
    Improved README.md to explain the steps needed to start the 'resque-web' server interface properly with the 'resque-retry' features. 
    
    The problems as I identified them essentially were: 
    A. The README proposed a rack configuration, but didn't include an example command for a user to start the server. Solution: Added a simple example on how to start the server with bundler by loading the proposed rack configuration. 
    B. The README didn't include the alternate option of starting the resque-web interface using the built-in 'resque-web' command. Solution: Included a simple 3 step explanation on how to use the resque-web command by sending it a configuration file as a parameter
Commits on Aug 22, 2014
  1. Merge pull request #109 from michaelglass/fix_constantize

    authored
    `#constantize` is on `Job`
  2. @michaelglass
Commits on Aug 13, 2014
Commits on Aug 12, 2014
  1. Merge pull request #61 from dylanahsmith/dirty-exit-retry-attempt

    authored
    Get the retry_attempt for DirtyExit failures, where perform isn't called.
  2. @dylanahsmith
  3. @dylanahsmith

    Get the retry_attempt for DirtyExit failures, where perform isn't cal…

    dylanahsmith authored
    …led.
    
    @retry_attempt depends on perform being called, but perform will be called
    after forking and set in the child job process. If there is a crash that
    prevents the job from notifying the failure hooks itself, then a DirtyExit
    exception will be given to the on_failure hooks from a worker processes,
    where @retry_attempt will not have been set.
    
    The @on_failure_retry_hook_already_called variable also needs to be
    ignored, because this is set to false in the before_perform hook.
Commits on Jul 25, 2014
  1. Typo fixes and re-adjusted version.

    authored
    Adjusted version number after discussion with @jzaleski, he caught my failure! :)
  2. Prepare for new gem release.

    authored
Commits on Jul 4, 2014
  1. Merge pull request #108 from jzaleski/jwz-upgrade-resque-scheduler-gem

    authored
    Upgrade "resque-scheduler" to "3.0.0"
Commits on Jun 30, 2014
  1. @jzaleski

    Upgrade "resque-scheduler" to "3.0.0"

    jzaleski authored
    * Upgrade "resque-scheduler" gem
    * Reference "resque/scheduler/tasks" instead of "resque_scheduler/tasks"
    * Update "README.md" to reflect new requirement
  2. @jzaleski
Commits on Jun 27, 2014
  1. @jzaleski
  2. @jzaleski

    Deprecate "args_for_retry" instead of removing it

    jzaleski authored
    Preserve backwards compatibility for gem-users that have overridden the
    "args_for_retry" method.
    
    Also, ensure that the tests for "args_for_retry", "retry_args" and
    "retry_args_for_exception" are not overcomplicated, all we care about is
    that they are hit.
Commits on Jun 26, 2014
  1. @jzaleski

    Rename "args_for_retry" to "retry_args"

    jzaleski authored
    Done for consistency w/ the addition of the "retry_args_for_exception"
    method
  2. @jzaleski

    Merge pull request #106 from jonp/custom-args

    jzaleski authored
    Added the ability to change the retry-args based on the exception
  3. @jonp
Commits on Jun 25, 2014
  1. @jzaleski

    Apply reformatting suggestions to merged PR

    jzaleski authored
    Rather than holding up the proposed change, PR-105 was merged. This
    commit applies the suggested code-changes (all formatting/style)
    
    Thanks again @orenmazor!
  2. @jzaleski

    Merge pull request #105 from orenmazor/expiry_retry_key_after_use_bac…

    jzaleski authored
    …koff_values
    
    allow setting the expire_retry_key_after value on the fly
Commits on Jun 20, 2014
  1. @jzaleski

    Merge pull request #104 from greysteil/update-travis

    jzaleski authored
    Add Ruby 2.1.2 to Travis build matrix
  2. @orenmazor

    allow setting the expire_retry_key_after value on the fly. this is es…

    orenmazor authored
    …pecially useful for situations where you retry a job multiple times and the backoff period for a given run is likely to be longer than the default expire_time that was set
Something went wrong with that request. Please try again.