Sidekiq v3.1.0 Release Notes

    • New remote control feature: you can remotely trigger Sidekiq to quiet or terminate via API, without signals. This is most useful on JRuby or Heroku which does not support the USR1 'quiet' signal. Now you can run a rake task like this at the start of your deploy to quiet your set of Sidekiq processes. [#1703] ruby namespace :sidekiq do task :quiet => :environment do Sidekiq::ProcessSet.new.each(&:quiet!) end end
    • ๐Ÿ’ป The Web UI can use the API to quiet or stop all processes via the Busy page.
    • ๐Ÿ’ป The Web UI understands and hides the Sidekiq::Extensions::Delay* classes, instead showing Class.method as the Job. [#1718]
    • ๐Ÿ’… Polish the Dashboard graphs a bit, update Rickshaw [brandonhilkert, #1725]
    • ๐Ÿ”ง The poll interval is now configurable in the Web UI [madebydna, #1713]
    • ๐Ÿšš Delay extensions can be removed so they don't conflict with DelayedJob: put Sidekiq.remove_delay! in your initializer. [devaroop, #1674]