rake
v13.4.0 open-sourceThe section your link pointed to isn't on rake's page any more, so we've brought you to the top.
Rake is a Ruby-based build automation tool that manages tasks and dependencies using a domain-specific language written in Ruby.
TEST="test/foo_test.rb test/bar_test.rb" rake test
rake -C /path/to/project/asset compile
rule .o => [:src] do |t| \n sh "gcc -c #{t.source} -o #{t.name}" \nend
task :deploy => ['db:migrate'] # 'db:migrate' runs first, but ':deploy' does not depend on its output files.
rake --where my_task
export RAKEOPT='-v'
rake my_task
rake 'task_name[re-run]' # where the Rakefile defines `task :task_name do |t| ... end` and code calls `t.reenable`
rake 'reset_task[force]' # where the Rakefile defines `task :reset_task do |t| t.clear_prerequisites; ... end`
RAKE_COLUMNS=120 rake -T
rake release["0.8.0"]
task :deploy, :region, :env do |t, args|
puts "Deploying to #{args.region} in #{args.env}" if args.env
end
task(:output => Rake::LATE) { sh 'generate_output.sh' }
desc "Dynamic task"; task(:dynamic_task => falsy_value) { sh 'do_something' }
require 'pathname'; desc "Pathname task"; file(Pathname('output.txt') => ['input.txt']) { touch 'output.txt' }
Summary
rake is an open-source, free build automation tool for Ruby projects, run from the command line to resolve tasks and their dependencies through a Ruby DSL. Beyond basic task definitions, it lets rule prerequisites take Pathname objects for richer file-dependency expressions, accepts Ruby pattern matching syntax for task arguments, and can target a subset of test files via the TEST environment variable without editing the Rakefile — handy for CI runs limited to changed specs. It is built for Ruby developers and maintainers who need dependency-aware task automation rather than a general-purpose build system, and it sits in the same category as Make or Rails' own task framework, which it largely superseded within Ruby projects. With 226 contributors and a history back to 2003, it remains active, with 87 commits in the past year and a release 127 days ago.
Rake is a Ruby-based build automation tool that manages tasks and dependencies using a domain-specific language written in Ruby.
How rake helps
Which of my tasks actually need to rerun when I change one file?
resolves each task's declared prerequisites into a dependency graph and only re-executes the tasks whose file or task dependencies are newer, skipping the rest
How do I express a prerequisite that's a file path rather than a task name?
accepts Pathname objects directly in rule prerequisites, so file-dependency rules can be written against real path objects instead of plain strings
Why did a task fail with no useful trace?
falls back to a detailed failure message when the raised exception carries a nil backtrace, instead of surfacing a blank trace
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for rake, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail rake puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
21 entries
No entries match these filters.
- April 20261
- May 20251
- April 20241
- October 20231
- November 202216
- November 20141
Project health
Issue, contributor and maintainer activity in ruby/rake, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 4 −5 vs prior 12 months
- Maintainers 1 +0 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 697 days first maintainer reply 14 hours
- Open backlog 48 of 179 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 48
- Contributors / month 0
- Commits / month 0
- Stars 2,459
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.