jhuckaby/Cronicle

A simple, distributed task scheduler and runner with a web based UI.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 10 minutes ago
Added to GitGenius on September 11th, 2026
Created on January 8th, 2016
Open Issues & Pull Requests: 333 (+0)
GitHub issues: Enabled
Number of forks: 504
Total Stargazers: 5,830 (+1)
Total Subscribers: 66 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.6 hours
Mean response time: 46.7 days
90th percentile: 4.7 days
Tracked items: 153

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 8% of issues opened in the past year have been closed. Three people close 64% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 72
New in 7 days: 1
Closed in 7 days: 2
Avg open age: 1,022 days
Stale 30+ days: 70
Stale 90+ days: 68

Recent activity

Opened in 7 days: 0
Closed in 7 days: 2
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (49)
  • enhancement (46)
  • not planned (3)
  • v2 (3)
  • duplicate (2)
  • need info (1)
  • question (1)
  • security (1)

Detailed Description

Cronicle is a distributed task scheduler and runner with a web-based UI that replaces traditional cron for multi-server environments.

The tool addresses the limitations of standard cron by enabling job scheduling and execution across multiple servers with centralized management. It handles scheduled, repeating, and on-demand jobs while providing real-time status monitoring and live log viewing. Jobs can be defined as simple shell commands or as plugins written in virtually any language, with the scheduler automatically discovering nearby servers and performing failover to backups when needed.

Cronicle suits teams running distributed systems who need visibility into job execution across multiple machines. It works well for environments where traditional cron's single-server model becomes unwieldy, particularly when you need historical performance data, timezone-aware scheduling, or the ability to queue long-running tasks. The web UI and REST API make it accessible to operators without deep command-line expertise, and the plugin system allows integration with custom logic. The project's README indicates that a spiritual successor called xyOps is now available, though Cronicle will continue to receive maintenance for bug fixes and security patches.

Almost all open issues are raised by outside users rather than the core team, reflecting a substantial base of adopters using the tool in production. Maintainers typically respond to new issues and pull requests within hours.