chaps-io/gush
63.0
Adequate · 6 November 2026
1.1k
lines of production code
Ruby
primary language
4
measurements over time
What this system is
Gush is a Ruby-based workflow engine that manages job execution and dependency graphs using ActiveJob for backend abstraction and Redis for state persistence. It provides a command-line interface for defining, monitoring, and controlling workflows, replacing its previous Sidekiq and Goliath-based architecture. The system supports complex job chaining, retry logic, and payload passing, with a focus on CLI-driven management rather than a web interface.
Features
New CLI overview command displays detailed workflow and job status
The CLI now includes a dedicated overview feature that presents a structured table of workflow details, including ID, name, job counts (failed, succeeded, enqueued, running, remaining), and the start time. It provides a clear status indicator (ready, running, stopped, finished, or failed) and lists individual jobs with their current state, helping users monitor workflow progress directly from the command line.
lib/gush/cli · high confidence
Removals
Removal of legacy Gush server configuration
The legacy server configuration file (gush\_server.rb) has been removed. This file previously defined the template engine (Slim), Redis connection settings, and an EventMachine-based pub/sub listener for job status updates. Users relying on this specific server-side configuration setup will need to migrate to the current architecture.
lib/gush/config · high confidence
Removal of legacy WebSocket-based frontend assets
The server no longer serves the legacy JavaScript files (\controls.js\ and \jquery.min.js\) that powered the previous WebSocket-based web interface. This change removes the client-side code responsible for connecting to \ws://localhost:9000/ws\ and rendering workflow/job lists, indicating a shift away from the in-browser real-time UI towards the new CLI and Sidekiq-based workflow management.
lib/gush/server · high confidence
Behavioural changes
Adopts ActiveJob for job scheduling and execution
Gush now uses ActiveJob for scheduling and executing jobs instead of the previous Sidekiq-based implementation, providing a more standard and abstracted interface for job definitions. The configuration file has been renamed from Gushfile.rb to Gushfile, and the README has been updated to reflect the new API, installation steps, and examples using the ActiveJob integration.
(repo-wide) · high confidence
CLI commands now handled by Gush::CLI with Bundler integration
The bin/gush entry point has been refactored to delegate all command-line logic to the Gush::CLI class, replacing the previous inline handling of subcommands like 'server', 'create', 'start', 'list', 'redis', and 'worker'. This change introduces Bundler for dependency management and adds specific error handling for workflow-related issues, such as missing workflows or dependency cycles, providing clearer feedback to users when these errors occur.
bin · high confidence
Gush 5.0: Migration to ActiveJob and redesigned workflow execution model
Gush has been upgraded to version 5.0.0, replacing the Sidekiq backend with ActiveJob to provide a more flexible job execution abstraction. The internal data model has been significantly restructured: jobs and workflows no longer inherit from Tree nodes, instead using explicit \incoming\ and \outgoing\ arrays to manage dependencies. State tracking has shifted from boolean flags to timestamp-based attributes (e.g., \started\_at\, \finished\_at\), and the CLI now uses Thor for command handling. Additionally, the library introduces a migration system for storage schema updates and removes the legacy Goliath server and ConcurrentWorkflow classes.
lib/gush · high confidence
Introduce workflow persistence migration and restructure core library loading
This change adds a database migration (version 1) that persists workflow data to Redis, ensuring workflows survive restarts or clears, and restructures the main library entry point to explicitly load new components like the JSON handler, CLI, graph logic, client, and configuration, while removing the previous inline tree-building and workflow-starting logic that is now handled by the new client and migration infrastructure.
lib · high confidence
Test coverage
Added comprehensive test suite for Gush core components; Added test infrastructure and specs for Gush core; Integration tests for workflow execution, retry logic, and payload passing; Removed obsolete specs for Gush::Job and Gush::Workflow.
Dependencies
Migrate from Sidekiq to ActiveJob and update dependencies
Gush now uses ActiveJob (\>= 7.0.0, \< 9) instead of Sidekiq for job execution, allowing it to work with any ActiveJob adapter. The gem has updated its dependency list to include concurrent-ruby, multi\_json, redis-mutex, hiredis, graphviz, terminal-table, paint, thor, and launchy, while removing older dependencies like rubytree and sidekiq. Development dependencies have also been updated to include rubocop and its related gems for code style consistency.
(dependencies) · 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 63 → 63 (-0.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 75 → 75 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 54 → 54 (+0.0)
- Readiness 67 → 67 (+0.0)
- Security 99 → 98 (-0.7)
Resolved (4)
- CLI offers a combined 'create_and_start' operation, while the Client API requires two separate calls (create_workflow then start_workflow). This inconsistency forces CLI users to have a simpler workflow than programmatic users.
- Four different methods for listing/retrieving workflows with inconsistent parameter names and return types. CLI.list returns display data, Client.workflow_ids returns IDs, Client.workflows returns objects, and Workflow.page is a class method. The parameter 'start/stop' vs 'order' vs 'kwargs' is inconsistent.
- Three distinct entry points for creating a workflow exist with different signatures and responsibilities. CLI.create is a high-level CLI command, Client.create_workflow is a client-side API call, and Workflow.create is a model-level factory. This forces users to choose the correct layer without a clear unified entry point.
- Three methods for retrieving a workflow by ID. CLI.show is for display, Client.find_workflow is for client retrieval, and Workflow.find is a model lookup. This duplication creates confusion about which method to use for programmatic access.
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
chaps-io/gush 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 6 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 d5180baf21bde13bb1c2c74d7d25e3d41be514ea — 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.3+preprod-60d1b390edf0.