Skip to content
CAI
Software that uses CAICheck a score

bensheldon/good_job

42.1

Weak · 5 November 2026

12.6k

lines of production code

Ruby

with JavaScript

4

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Features

Add Batches dashboard views

The dashboard now includes dedicated views for managing job batches. Users can view a paginated list of batches on the index page, inspect batch details and attributes on the show page, and see the individual jobs associated with each batch. The interface supports retrying discarded batches and provides collapsible sections to inspect batch and job parameters.

_app/views/good\job/batches · high confidence

Add Sorbet/Tapioca configuration and pre-require setup

This change introduces the initial configuration for Sorbet and Tapioca static analysis tools. A new \config.yml\ file is added to define gem and DSL generation parameters, including a reference to a prerequire script. The \prerequire.rb\ file is created to ensure Rails is fully loaded before type generation, specifically addressing issues with engine descendants and Capybara integration. Additionally, \require.rb\ is added to explicitly list all necessary library dependencies (such as Active Job, Good Job, Rails, and various concurrent/ruby utilities) that Tapioca needs to analyze for type generation.

sorbet/tapioca · high confidence

Add customizable view extension partials for the GoodJob dashboard

The GoodJob dashboard now supports three new view partials (\_custom\_head, \_custom\_job\_details, and \_custom\_execution\_details) that allow users to inject custom content into the dashboard's head section, job show page, and execution details respectively. These partials provide access to job and execution objects and application helpers, enabling tailored UI extensions without modifying core GoodJob views.

_app/views/good\job · high confidence

Added SHA-512 checksums for good\_job gem releases

The repository now includes SHA-512 checksum files (in addition to existing SHA-256 files) for good\_job gem versions ranging from 2.14.4 through 3.30.1, as well as 4.0.0 through 4.20.0. This allows users to verify the integrity of downloaded gems using the SHA-512 algorithm, providing an additional layer of security and verification options alongside the existing SHA-256 checksums.

checksums · high confidence

Added Sorbet RBI type definitions for Rails and gems

The project now includes generated Sorbet RBI files for core Rails components (ActionMailer, ActionPack, ActionView, ActiveJob, ActiveModel, ActiveRecord, ActiveSupport) and key gems (ActionCable, ActionMailbox, Faraday, GlobalID, Minitest, Railties, Rainbow, Trix). These annotations provide static type signatures for the framework and dependencies, enabling Sorbet to perform type checking on the codebase.

sorbet/rbi/gems · high confidence

Added benchmark scripts for job throughput, advisory locks, and scheduler memory

New scripts have been added to the \scripts/\ directory to help users measure performance characteristics of GoodJob. \benchmark\_job\_throughput.rb\ benchmarks job selection strategies (such as priority, creation order, and queue ordering) using \Benchmark.ips\. \benchmark\_advisory\_locks.rb\ compares the performance of session-level versus transaction-level advisory locks. \benchmark\_scheduler\_memory.rb\ uses \memory\_profiler\ to report memory usage when creating scheduler threads. These tools allow users to profile and optimize their job processing configurations.

scripts · high confidence

Added example startup scripts for FreeBSD and systemd

New example configuration files are now provided to help users run GoodJob as a background service on FreeBSD (rc.d) and Linux (systemd). The FreeBSD script allows enabling and managing the service via /etc/rc.conf, while the systemd unit file supports both user and system services, including automatic restarts and status notifications.

examples · high confidence

GoodJob v4 introduces batch processing, job pausing, and configurable ActiveRecord inheritance

GoodJob has been upgraded to version 4, introducing several significant capabilities and structural changes. Users can now group jobs into Batches with \GoodJob::Batch\ and \GoodJob::BatchRecord\, enabling bulk enqueuing via \enqueue\_all\ and defining callbacks for success, finish, and discard events. The system now supports pausing jobs by queue, class, or label using the new \GoodJob::Setting\ model and \exclude\_paused\ scope. Additionally, the ActiveRecord parent class is now configurable via \GoodJob.active\_record\_parent\_class\, allowing GoodJob models to inherit from a custom base class instead of defaulting to \ActiveRecord::Base\. The \DiscreteExecution\ model is deprecated in favor of \Execution\, and the dashboard now supports dynamic cron enabling/disabling and displays interrupted execution recovery durations.

_app/models/good\job · high confidence

Initial GitHub Codespaces and devcontainer configuration

Added a complete development container setup for GitHub Codespaces, including a Dockerfile based on the Ruby image with Node.js, PostgreSQL client, and Chromium/Chromium-driver installed, a docker-compose configuration linking the app to a Postgres database, and a devcontainer.json defining port forwarding and the setup command.

.devcontainer · high confidence

Initial project scaffolding and development tooling

The repository has been initialized with essential configuration files for development and release workflows. This includes an EditorConfig for consistent code formatting, RuboCop and ERB Lint configurations for static analysis, and a Markdown style guide. Development tooling is established via RSpec, YARD support for GFM-rendered documentation, and a comprehensive Rakefile that automates version bumping, changelog generation, checksum creation, and git tagging for releases. Additionally, a Heroku demo application configuration (app.json, Procfile) and a Code of Conduct are added to support community engagement and testing.

(repo-wide) · high confidence

Integrate Brakeman security scanner and define GoodJob engine routes

This change introduces a Brakeman security scanner configuration (\config/brakeman.ignore\) to suppress specific false-positive warnings for SQL injection, command injection, and dynamic evaluation within GoodJob's internal implementation, ensuring the security audit passes without noise. Simultaneously, it establishes the core routing structure for the GoodJob engine, defining RESTful endpoints for managing jobs, batches, cron entries, processes, and performance metrics, along with specific actions for discarding, retrying, and rescheduling jobs, and serving frontend assets.

config · high confidence

Introduce GoodJob executable script

A new executable script at exe/good\_job has been added, allowing users to run GoodJob directly from the command line. The script sets the CLI context to indicate it is running within the executable environment and then starts the CLI with the provided arguments.

exe · high confidence

Introduce inline job buffering for transactional safety

GoodJob now includes an InlineBuffer mechanism that allows jobs enqueued within a database transaction to be deferred until after the transaction commits. This ensures that jobs do not execute while the transaction is still open, preventing issues with uncommitted data or lock contention. Users benefit from more reliable job execution when using inline or synchronous job patterns, as jobs are now safely persisted and executed only upon successful transaction completion.

lib · high confidence

New ActiveJob extensions for concurrency, labels, batches, and notification control

GoodJob introduces several new ActiveJob extensions that enhance job control and observability. The Concurrency extension allows users to define rules for limiting concurrent executions via enqueue/perform limits and throttles, supporting dynamic keys and labels, while suppressing backtraces for concurrency errors. The Labels extension enables attaching and persisting custom labels on job instances for better filtering and tracking. The Batches extension provides context awareness for jobs enqueued within batch or bulk capture blocks, including debug logging when jobs are not using the GoodJob adapter. Finally, the NotifyOptions extension allows users to disable PostgreSQL NOTIFY events on enqueue for specific jobs or classes, reducing database noise.

_lib/good\_job/active\_job\extensions · high confidence

New Cron Entries dashboard for managing scheduled jobs

The GoodJob dashboard now includes a dedicated Cron Entries section, allowing users to view, inspect, and manage cron schedules directly from the UI. The new index page displays a table of all configured cron jobs, showing their key, job class, schedule, next scheduled run time, last run time, and current status (active or paused). Users can toggle the enabled state of individual cron entries to temporarily disable or re-enable them, enqueue a specific cron job manually, and inspect the full JSON properties of each schedule. A separate show page provides a detailed view of a specific cron entry's associated job history.

_app/views/good\_job/cron\entries · high confidence

New GoodJob performance and scheduling charts

The GoodJob dashboard now includes new visualizations for monitoring job performance and scheduling. A performance index chart displays total execution duration over time, broken down by individual job class, with configurable time ranges (1h, 6h, 24h, 7d) and a vertical legend. A performance show chart provides a histogram of execution durations for specific job classes, helping identify slow jobs. Additionally, a scheduled-by-queue chart tracks the number of scheduled jobs per queue over hourly intervals, allowing users to monitor queue load and scheduling patterns.

_app/charts/good\job · high confidence

New dashboard pages for job pauses and discarded job cleanup

The GoodJob dashboard now includes dedicated pages for managing paused jobs and reviewing discarded jobs. The Pauses page allows users to pause and unpause jobs by queue, job class, or label (when enabled via configuration), while the Cleaner page provides a summary of discarded jobs grouped by class and exception, with time-based filtering. These views introduce new UI components for pause management and job cleanup statistics.

_app/views/good\job/shared · high confidence

New install and update generators for GoodJob migrations

GoodJob now provides dedicated Rails generators (\good\_job:install\ and \good\_job:update\) to manage database schema changes. The install generator creates a single monolithic migration file for initial setup, while the update generator produces idempotent incremental migration files (adding columns like \active\_job\_id\, \concurrency\_key\, and \cron\_key\) that safely handle schema evolution without overwriting existing migrations. Both generators support a \--database\ option to target specific database connections.

_lib/generators/good\job · high confidence

New performance dashboard for monitoring job execution metrics

A new performance dashboard has been added to the Good Job interface, allowing users to monitor job execution statistics over time. The dashboard features a time-range selector with preset options and custom date pickers, along with a timezone indicator. It displays aggregated metrics including total executions, average duration, minimum duration, and maximum duration, broken down by both individual job classes and queues. This provides a centralized view for tracking job performance trends and identifying potential bottlenecks.

_app/views/good\job/performance · high confidence

New processes dashboard view with detailed process information

The GoodJob dashboard now includes a dedicated processes index page that displays a list of active processes. For each process, users can see the basename, PID, hostname, and memory usage (in MB). The view also shows scheduler details including queues and max\_threads, whether cron is enabled, and timestamps for when the process started and was last updated. Users can inspect the full process state by clicking an info button, which reveals a collapsible section with the raw process state JSON.

_app/views/good\job/processes · high confidence

Removals

Removal of Good Job Rake tasks

The Good Job Rake tasks have been removed from the application. This eliminates the previously defined (though commented out) rake task structure for Good Job, simplifying the task namespace and removing unused code from the lib/tasks directory.

lib/tasks · high confidence

Behavioural changes

2 commits (0 fixes) modifying sorbet/rbi/dsl

A change to existing behaviour in sorbet/rbi/dsl — 2 commits, 16 files: “Update development dependencies and light Rubocop'ing (\#1136)”; “Restructure code so it type-checks under Sorbet without runtime assertions (\#1899)” (refs \#1136, \#1899).

sorbet/rbi/dsl · medium confidence · unverified

4 commits (0 fixes) modifying sorbet

A change to existing behaviour in sorbet — 4 commits, 1 file: “Add Sorbet to linter (\#760)”; “Introduce advisory lock key customization support methods (\#1722)”; “Upgrade dev environment: Ruby 4.0.7, Bundler 4.0.22, and gems (\#1859)”; and 1 more (refs \#760, \#1722, \#1859, \#1899).

sorbet · medium confidence · unverified

4 commits (2 fixes) modifying app/models/good\_job/job

A change to existing behaviour in app/models/good\_job/job — 4 commits (2 fixs), 1 file: “Release abandoned job claims after database failures (\#1887)”; “Fix advisory lock leak and refactor advisory lock lifecycle (\#1735)”; “Fix PG::AmbiguousColumn in skiplocked/hybrid claim with ordered queues + concurrency rules (\#1768)”; and 1 more (refs \#1887, \#1735, \#1768, \#1899).

_app/models/good\job/job · medium confidence · unverified

7 commits (2 fixes) modifying lib/good\_job/probe\_server

A change to existing behaviour in lib/good\_job/probe\_server — 7 commits (2 fixs), 5 files: “Require the concurrent-ruby classes GoodJob uses (\#1885)”; “fix: require rack/handler for rack \>= 3.1.x (\#1383)”; “Add multi-process cluster mode (\#1803)”; and 4 more (refs \#1885, \#1383, \#1803, \#1902, \#1079, …).

_lib/good\_job/probe\server · medium confidence · unverified

Added Sorbet RBI shims for Ractor support and Rack/Rackup compatibility

New type-shim files have been added to the Sorbet RBI shims directory to support static analysis of newer Ruby and Rails features. The \active\_support\_ractors.rbi\ shim defines the \ActiveSupport::Ractors\ module and \Ractor::IsolationError\ class, enabling type checking for code that enqueues jobs from non-main Ractors. The \rack\_handler.rb\ shim provides type definitions for \Rack::Handler\ and \Rackup::Handler\, addressing compatibility issues between Rack 2.0 and Rack 3.0/Rackup. Additionally, \concurrent\_ruby.rb\ adds shims for \Set::SubclassCompatible\ modules required by the concurrent-ruby library.

sorbet/rbi/shims · high confidence

Dashboard display improvements and icon refactoring

The dashboard now truncates long strings in job parameters to prevent page stalls, formats durations and performance buckets using localized strings, and displays job status badges with SVG icons. Additionally, a new IconsHelper uses SVG \\<use\>\ elements for rendering icons, and translation helpers ensure missing keys return empty hashes rather than causing errors.

app/helpers · high confidence

Demo app harness moved to dedicated directory with new configuration and tooling

The Rails demo application has been relocated from \test/dummy\ to \demo\, bringing with it a suite of new initializers that enhance observability and stability. GoodJob is now configured with experimental job pausing, cron scheduling for example jobs, and environment-specific execution modes. Database interactions are hardened by disallowing permanent connection checkouts and adding an \explain\_force\_index\ helper for query analysis. The demo is protected against crawler-induced timeouts via Rack::Attack rules, while development logging now captures Postgres notices. Additional tooling includes rbtrace for heap dumps, Skylight sampling, and Rack::MiniProfiler exclusions.

demo/config/initializers · high confidence

Demo app relocated and restructured with new job examples

The Rails demo application has been moved from \spec/test\_app\ to \demo/app\, renaming the app title from 'Dummy' to 'TestApp' and updating asset paths to reflect the new location. This relocation includes new job classes (\ExampleJob\, \ConfigurableQueueJob\, \FragileJob\, \PgHeroMaintenanceJob\) that demonstrate GoodJob features like concurrency control, labels, and batch processing, as well as custom view partials for the GoodJob dashboard to showcase extensibility.

demo/app · high confidence

Demo app restructured with performance and concurrency improvements

The demo application has been moved from the test harness to the \demo/\ directory and reconfigured for better performance and concurrent testing. Key changes include enabling Puma worker clustering with preloading and a warmup phase to optimize memory usage, integrating PgHero for database monitoring, and configuring the database to support parallel test execution via Git worktree-aware naming. The application now uses GoodJob as the default Active Job adapter, loads only necessary Rails frameworks to reduce memory footprint, and includes a custom thread-name logger for easier debugging.

demo/config · high confidence

GoodJob dashboard controllers restructured and enhanced with new capabilities

The GoodJob dashboard controllers have been reorganized into a modular structure under \app/controllers/good\_job/\, introducing a base \ApplicationController\ that enforces strict Content Security Policy (CSP) headers and isolates GoodJob's I18n configuration to prevent locale conflicts. This change adds new controllers for managing batches (\BatchesController\), cleaning discarded jobs (\CleanerController\), and monitoring performance metrics (\PerformanceController\), while significantly expanding job management in \JobsController\ with force-discard and mass-action capabilities. Additionally, \CronEntriesController\ now supports enabling and disabling cron schedules, and \PausesController\ allows pausing jobs by queue, class, or label, providing finer operational control over the background job system.

app/controllers · high confidence

GoodJob database schema and index overhaul in demo app

The demo application's database migrations have been significantly updated to support the latest GoodJob features and performance optimizations. New tables and columns have been added, including \good\_job\_processes\, \good\_job\_settings\, \good\_job\_batches\, and \good\_job\_executions\, along with fields like \active\_job\_id\, \concurrency\_key\, \cron\_key\, \labels\, \error\_backtrace\, and \duration\. The schema now includes conditional indexes for cron jobs, concurrency locking, and batch operations, as well as new indexes on \queue\_name\, \created\_at\, and \finished\_at\ to improve query performance. Additionally, the \pg\_stat\_statements\ extension is enabled for query monitoring via PGHero, and the \uuid-ossp\ extension is now required.

demo/db/migrate · high confidence

Introduce GoodJob v4 core architecture and configuration system

GoodJob has been upgraded to version 4, introducing a new internal architecture centered around the \GoodJob::Capsule\ to manage schedulers, pollers, and cron managers, and the \GoodJob::Configuration\ class to centralize settings (replacing direct adapter instantiation). This release adds multi-process cluster mode support via the \subprocesses\ CLI option, a new \GoodJob::Bulk\ API for batch-enqueueing jobs, and a new \GoodJob::Callable\ module for duck-typing. It also introduces \GoodJob::CurrentThread\ for thread-local execution state, \GoodJob::InterruptError\ for handling interrupted jobs, and a new \GoodJob::JobPerformer\ for job execution. The CLI now uses Thor and supports options like \--idle-timeout\ and \--daemonize\. The \ActiveJob::QueueAdapters::GoodJobAdapter\ is now a thin wrapper around the new \GoodJob::Adapter\.

_lib/good\job · high confidence

Migrate frontend JavaScript to Stimulus controllers

The dashboard's frontend JavaScript has been refactored from generic modules into a set of Stimulus controllers (including async\_values, chart, live\_poll, performance\_range, theme, and others). This change introduces structured, component-based behavior for key dashboard features: asynchronous loading of navbar values, interactive time-series charts with range selection, live polling with tab preservation, performance range form enhancements, and dark mode theme switching.

_app/frontend/good\job/modules · high confidence

Migrate frontend to Stimulus and Turbo with new dashboard UI components

The Good Job frontend has been refactored to use Stimulus controllers for interactivity and Turbo for navigation, replacing the previous JavaScript approach. This change introduces a new dark mode theme, asynchronous loading for top navigation metrics, and enhanced dashboard features including time-range controls for time-series charts, a vertical legend, and split badges for cron schedules. Additionally, SVG icons are now managed via a centralized sprite file for better performance and consistency.

_app/frontend/good\job · high confidence

New daemonization, multi-scheduler, and execution result tracking components

This change introduces three new internal components to the GoodJob library. The \GoodJob::Daemon\ class now manages process daemonization, including pidfile creation, validation, and cleanup, ensuring the daemon does not change the working directory. The \GoodJob::MultiScheduler\ class allows the system to delegate job scheduling across multiple \Scheduler\ instances, enabling support for multiple queues and improved metrics aggregation. Additionally, the \GoodJob::ExecutionResult\ model provides a structured way to store job execution outcomes, including success status, errors, and retry context, replacing ad-hoc result handling.

_good\job · high confidence

New dashboard layout with dark mode, Turbo, and modern asset loading

The Good Job dashboard now uses a new application layout that supports dark mode via Bootstrap's color scheme, integrates Turbo for navigation, and loads assets using modern import maps and module preloading. The layout includes a favicon, a custom head partial for extensibility, and renders the navbar, secondary navbar, alerts, and footer within a flex-column structure.

app/views/layouts · high confidence

New development tooling and demo app binstubs

The repository now includes a comprehensive set of binstubs in the \bin/\ directory to streamline local development and testing. A new \bin/lint\ script unifies multiple linters (Sorbet, Rubocop, YARD, Herb, ERB Lint, Markdown Lint, i18n-tasks, and Brakeman) into a single command. Development workflows are supported by \bin/rails\ and \bin/test\_app\_rake\ which point to a new \demo\ application directory (replacing the previous \test/dummy\ structure), along with \bin/setup\ for environment initialization. Additional binstubs for \rspec\, \srb\, \tapioca\, and \docserver\ are provided, while the legacy \bin/test\ file has been removed.

bin · high confidence

Process heartbeat mechanism for job execution reliability

The notifier now includes a process heartbeat feature that automatically registers, refreshes, and deregisters the current process in the database during job execution. This ensures that process records are always up-to-date, improving reliability by preventing stale process states and handling connection changes gracefully through advisory locks and Rails executor wrapping.

_lib/good\job/notifier · high confidence

Rails demo application moved to dedicated directory with schema sanitization and server loading

The Rails demo application has been relocated from the test harness directory to a standalone \demo\ folder, serving both as a standalone demonstration of the library and as the test harness environment. To ensure stability across different Rails versions and CI environments, the demo's Rakefile now automatically sanitizes \db/schema.rb\ by stripping the specific ActiveRecord version number and removing the \pg\_catalog\ namespace from extension declarations. Additionally, the application's Rack configuration (\config.ru\) has been updated to explicitly call \Rails.application.load\_server\, which suppresses Puma web-concurrency warnings during execution.

demo · high confidence

Rails demo environment configuration restructured and enhanced

The Rails application harness has been moved from the test directory to the demo folder, introducing a dedicated demo environment that inherits from production settings. The development environment now includes specific support for GitHub Codespaces, automatically configuring host allowances and Action Cable origins when the relevant environment variables are present. In production, SSL enforcement is now controlled via the FORCE\_SSL environment variable, logging to STDOUT is enabled by default, and the Active Job queue name prefix has been updated to 'test\_app\_production'.

demo/config/environments · high confidence

Redesigned Jobs Dashboard with Execution Details and Error Context

The GoodJob dashboard views have been rewritten to provide a more detailed and interactive experience for monitoring jobs. The new Jobs index and show pages feature a responsive table layout that displays job metadata (queue, priority, labels, attempts) and supports bulk actions (reschedule, retry, discard, destroy) filtered by job state. A key addition is the dedicated executions list on the job show page, which displays individual execution metrics such as queue and runtime latency, interrupted recovery duration, and status. For failed jobs, the UI now presents the error message and offers tabbed views to inspect either the filtered application backtrace or the full execution backtrace. Additionally, job parameters are now collapsible and truncated for readability, and the dashboard supports custom extension partials for further UI customization.

_app/views/good\job/jobs · high confidence

Refactored dashboard filtering into a modular BaseFilter architecture

The dashboard filtering logic has been restructured into a new \BaseFilter\ class with specialized subclasses (\JobsFilter\, \BatchesFilter\), replacing the previous monolithic implementation. This change introduces a standardized interface for pagination (using \after\_id\/\after\_at\ cursors), state counting, and parameter handling. For users, this ensures consistent filtering behavior across jobs and batches, supports filtering by job labels and cron keys, and improves performance for counting succeeded jobs by using a complement subtraction strategy. The \JobsFilter\ specifically handles state-based ordering (e.g., scheduled jobs ordered by \scheduled\_at\) and optimized UUID-based job ID searches.

app/filters · high confidence

Refined job status logic and new advisory locking and error tracking concerns

This change introduces several new concerns in app/models/concerns/good\_job that refine how jobs are locked, tracked, and reported. The new AdvisoryLockable concern replaces the previous Lockable module, introducing transaction-level advisory locks, customizable lock keys, and robust connection-leasing to prevent lock leaks and handle phantom locks in CTE queries. The Reportable concern updates the job status logic, renaming the 'finished' state to 'succeeded' (where 'finished' now implies either succeeded or discarded) and introducing a 'running' state for actively executing jobs. Additionally, the ErrorEvents concern adds an error\_event enum to track specific error contexts (e.g., interrupted, unhandled, handled, retried, retry\_stopped, discarded), and the Filterable concern improves search performance and correctness by bounding tsvector sizes to prevent PostgreSQL limits and enhancing text search to include identifier-like strings.

app/models/concerns · high confidence

Updated GoodJob database migration templates for v4

The update migration templates for GoodJob have been replaced with a comprehensive set of 20 incremental migrations. These templates now include the full v4 schema (good\_jobs, good\_job\_batches, good\_job\_executions, good\_job\_processes, good\_job\_settings) and apply numerous performance optimizations, such as adding specific indexes for concurrency keys, job classes, scheduled times, and batch operations, while removing redundant indexes and reordering the cron index to support efficient job dequeueing and cleanup.

_lib/generators/good\job/templates/update · high confidence

Updated GoodJob installation migration with new schema and indexes

The \rails g good\_job:install\ generator now produces a migration that creates the full current GoodJob schema, including the \good\_job\_executions\ table for tracking discrete job executions, the \good\_job\_batches\ table for batch processing, and the \good\_job\_processes\ table for process tracking. The \good\_jobs\ table schema has been expanded with new columns such as \active\_job\_id\, \concurrency\_key\, \cron\_key\, \batch\_id\, \error\_event\, \labels\, and \locked\_by\_id\. Additionally, the generated migration includes a comprehensive set of conditional and composite indexes optimized for job dequeueing, cron scheduling, batch management, and error tracking.

_lib/generators/good\job/templates/install · high confidence

Updated demo app database schema and seed data

The demo application now uses a refreshed database schema that includes new columns such as \duration\ and \error\_backtrace\ on executions, alongside numerous performance-oriented indexes on the \good\_jobs\ and \good\_job\_batches\ tables. Seed data has been updated to populate these structures with realistic job and batch records, ensuring the demo environment accurately reflects the current state of the background job processing system.

demo/db · high confidence

Test coverage

2 commits adding/updating tests in spec/app/models/good\_job/job; 5 commits adding/updating tests in spec/app/charts/good\_job; Added comprehensive test coverage for GoodJob core components; Added controller and helper tests for GoodJob dashboard features; Added integration tests for GoodJob core components; Added request specs for GoodJob dashboard controllers; Added system tests for GoodJob dashboard features; Added test coverage for Active Job extensions; Added test coverage for GoodJob core models; Added test coverage for GoodJob filter components; Added tests for AdvisoryLockable and Filterable concerns; Added tests for ExampleJob execution behaviors; Added tests for GoodJob core lifecycle and cleanup behaviors; Added tests for GoodJob cron configuration validation; Added tests for GoodJob install and update generators; Added tests for demo Rack::Attack rules; Added tests for helper methods formatting performance buckets and truncating display values; Added tests for inline adapter deferred execution and lock strategy behavior; Initialize RSpec test configuration for the Rails application; Introduce comprehensive RSpec test support infrastructure; Removal of legacy test infrastructure and minitest files.

Dependencies

Add Appraisal configurations for Rails 6.1 through 8.1

The gemfiles directory now includes dedicated Appraisal configuration files for Rails versions 6.1, 7.0, 7.1, 7.2, 8.0, 8.1, and the Rails HEAD branch. These files allow the library to be tested against a broader range of Rails versions, ensuring compatibility as new releases are introduced.

gemfiles · high confidence

Added Sorbet RBI stubs for unresolved constants

The \sorbet/rbi/todo.rbi\ file was added to provide type definitions for unresolved constants within the GoodJob codebase. This file, which is auto-generated and should not be edited manually, declares empty modules for various job classes (such as \TestJob\, \ErrorJob\, \SimpleJob\), error types, and internal constants (like \ACTIVE\_EVENT\, \LATCH\, \RESULTS\). This change supports the integration of Sorbet static type checking by resolving references to these constants, ensuring that the type checker can properly analyze the code without errors related to missing definitions.

sorbet/rbi · high confidence

GoodJob 4.20.0 release with Rails 8.1 support and dependency updates

This release updates the GoodJob gem to version 4.20.0, adding support for Rails 8.1 in the development and test environment while maintaining compatibility with Rails 6.1 through 8.0. The gemspec has been updated to require Ruby 3.0.0 or higher and declares explicit runtime dependencies on activejob, activerecord, concurrent-ruby, fugit, railties, and thor. Development dependencies have been reorganized, adding support for JRuby via activerecord-jdbcpostgresql-adapter and rbs, and introducing new linting tools such as herb, i18n-tasks, and sorbet. The lockfile reflects these changes, including updates to nokogiri, capybara, and cuprite.

(dependencies) · high confidence

Upgrade Bootstrap to v5.3.1

The frontend vendor library has been updated to Bootstrap v5.3.1. This upgrade brings the latest component implementations and bug fixes for UI elements such as dropdowns, modals, carousels, and tooltips, ensuring better compatibility with modern browser standards and improved accessibility features.

_app/frontend/good\job/vendor · high confidence

Housekeeping

Added placeholder file in tmp directory

A new .keep file has been added to the tmp directory to ensure the directory is tracked by version control.

tmp · high confidence

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

How this codebase got here

Score

  • CAI 41 → 42 (+1.3)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 32 → 39 (+6.6)
  • Architecture 87 → 86 (-1.4)
  • Maturity 62 → 69 (+7.5)
  • Readiness 62 → 62 (-0.1)
  • Security 36 → 33 (-3.3)
  • Domain Modelling 100 → 100 (+0.0)
  • Accessibility 44 → 44 (+0.0)
  • Performance 97 → 97 (+0.0)

Resolved (8)

  • Ambiguous naming convention. shutdown implies an action (imperative), while shutdown? implies a state check (predicate). However, in many Ruby libraries, shutdown is often used for the action and shutdown? for the status. The inconsistency here is subtle but worth noting if shutdown? is intended to be a simple boolean check while shutdown is the blocking action. More critically, if shutdown? is meant to check if the system is currently shutting down or has been shut down, the naming is acceptable. However, if shutdown? is meant to be a non-blocking check for readiness, it conflicts with the imperative shutdown. A clearer distinction would be shutdown (action) and shutting_down? (state) or shutdown_complete?.
  • Confusingly similar names for distinct operations. GoodJob.perform_inline is a high-level API for executing jobs synchronously, while Job.perform is a low-level instance method for executing a specific job record. The name perform_inline suggests it's a variant of perform, but it operates on a class/module level with different semantics (queue/limit) than the instance method. This can mislead developers into thinking perform_inline is just another way to call perform.
  • Duplicate intent across GoodJob and Setting modules. The GoodJob module exposes pause/unpause/paused? methods that appear to delegate to or duplicate the functionality of Setting. This creates two entry points for the same configuration state, violating the principle of least surprise and potentially causing confusion about which module owns the pause state.
  • Off-boarding risk: anonymized user #1
  • Orphaned file (lib/good_job/systemd_service.rb)
  • Outdated: herb
  • Outdated: rubocop-capybara
  • SimpleHandler.handle_connections (cognitive 19) (lib/good_job/probe_server/simple_handler.rb)

New (9)

  • Hotspot: app/models/good_job/job.rb (app/models/good_job/job.rb)
  • Hotspot: lib/good_job/adapter.rb (lib/good_job/adapter.rb)
  • Off-boarding risk: anonymized user #1
  • Orphaned file (app/charts/good_job/performance_range.rb)
  • Outdated: activejob
  • Outdated: activerecord
  • Outdated: parallel_tests
  • Outdated: rails
  • Outdated: railties

Changes since last survey

  • 25 commits — 23 feature/other, 2 fixes

By area

  • (root) — 6 commits
  • lib/good_job — 5 commits
  • .github/workflows — 2 commits
  • app/models — 2 commits
  • app/charts — 1 commit
  • app/controllers — 1 commit
  • app/filters — 1 commit
  • demo/config — 1 commit
  • lib/generators — 1 commit
  • lib/good_job.rb — 1 commit
  • sorbet/rbi — 1 commit
  • spec/app — 1 commit
  • spec/integration — 1 commit
  • spec/lib — 1 commit

Notable commits

  • fix: Fix flaky JRuby FrozenError by preloading record schemas in specs (#1896)
  • fix: Make integration specs robust under database load and fix mixed lock strategy specs (#1890)
  • change: Add a separate retention period for discarded jobs (#1897)
  • change: Add index_good_job_executions_on_created_at (#1884)
  • change: Bump github/codeql-action from 4.38.2 to 4.39.1 (#1907)
  • change: Demo: shorten database connection lifetimes (#1895)
  • change: Document expected duplicate key errors from cron in Postgres logs (#1908)
  • change: Don't retain or report schedulers replaced by a capsule restart (#1894)
  • change: Downgrade lock_type before releasing advisory lock (#1883)
  • change: Filter sensitive job arguments in the Dashboard (#1881)
  • change: Keep JRuby platform in Gemfile.lock when Bundler re-resolves (#1893)
  • change: Pin CI test runners to ubuntu-24.04 (#1888)
  • change: Prevent idle or malformed connections from stalling or stopping the probe server (#1902)
  • change: Read cron settings once instead of once per entry in the primary nav (#1906)
  • change: Release abandoned job claims after database failures (#1887)
  • change: Release good_job v4.23.0
  • change: Release good_job v4.23.1
  • change: Release good_job v4.24.0
  • change: Release good_job v4.24.1
  • change: Require the concurrent-ruby classes GoodJob uses (#1885)
  • …and 5 more

Architecture

  • Unchanged — 0 containers · 1 contexts · 0 edges

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

Survey your own repository

bensheldon/good_job was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.

About this page

  • The score is its most recent published measurement, taken on 5 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit e15ee796276a7856ff106b1764d40370d5d9f920 — the exact code this score is about.
  • Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
  • Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.2+preprod-5c4e66d9318b.