Project

angry_batch

0.0
The project is in a healthy, maintained state
angry_batchrstankov/angrybatchHomepageDocumentationSource CodeBug TrackerWiki
AngryBatch allows you to group ActiveJobs into batches and define jobs to run once all batch jobs are completed.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
 Popularity
Downloads
76
Stars
3
Forks
0
Watchers
0
 Releases
Current version
1.0.0
Total releases
1
First release
2025-07-20
Latest release
2025-07-20
 Development
Primary Language
Ruby
Licenses
MIT
Average date of last 50 commits
2025-07-20
Reverse Dependencies
0

 Dependencies

Development

factory_bot
>= 0
factory_bot_rails
>= 0
rake
>= 0
rspec
>= 0
rspec-rails
>= 0
rubocop
>= 0
rubocop-factory_bot
>= 0
rubocop-performance
>= 0
rubocop-rails
>= 0
rubocop-rake
>= 0
rubocop-rspec
>= 0
rubocop-rspec_rails
>= 0
sqlite3
>= 0

Runtime

activejob
>= 7.1
activerecord
>= 7.1
railties
>= 7.1
 Project Readme

AngryBatch

Build Status Gem Version

AngryBatch is a batching utility for ActiveJob that lets you group multiple jobs into a batch and trigger follow-up jobs when all jobs in the batch are done.

Installation

Add this line to your application's Gemfile:

gem 'angry_batch'

And then execute:

bundle

Or install it yourself as:

gem install angry_batch

Then, from your Rails app directory, create the angry tables:

rails generate angry_batch:install
rails db:migrate

Usage

# Step 1: Allow the job to be batchable
class SomeJob
  include AngryBatch::Batchable
end

# Step 2: Create new batch queue
queue = AngryBatch.new(label: 'Debug label')

# Step 3: Add completion handler
#   `on_complete` job will be called when all other queue jobs have completed
#   (more than one handlers are supported)
queue.on_complete ToBeCalledWhenAllOtherJobsAreCompletedJob, argument

# Step 3.1: Add error handler
queue.on_failure HandleFailureJob, argument

# Step 4: Enqueue varios jobs
queue.enqueue SomeJob, argument1
queue.enqueue SomeJob, argument2
queue.enqueue SomeJob, argument3

# Step 5: Trigger all jobs in the queue
in the queue.perform_later

Cleaning completed jobs

AngryBatch stores jobs in the database. You have to run AngryBatch::CleanupCronJob in a cron to clean the records.

AngryBatch::CleanupCronJob.perform

Example

Example 1

# You have a building with tenants.
# Every month, you must generate rent payments for them and notify them accordingly.

def generate_rent(building, period)
  queue = AngryBatch.new
  queue.on_complete GenerateBudgetSnapshotJob, building
  queue.on_complete NotifyBuildingOwnerJob, building

  building.tenants.each do |tenant|
    queue.enqueue GenerateTenantRentJob, tenant, period
  end

  queue.perform_later
end

Example 2

# You have an account with many projects.
# For each project, you want to export its data individually.
# After all exports are done, you want to archive them into a zip file.

def export_account_information(account)
  queue = AngryBatch.new(label: "Export Projects for #{account.id}")
  queue.on_complete Export::ZipJob, account

  account.projects.find_each do |project|
    queue.enqueue Export::ProjectFilesJob, project
  end

  queue.perform_later
end

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Run the tests (bundle exec rspec)
  6. Create new Pull Request

Authors

License

MIT License