Rake is invoked from the command line using:
% rake [options ...] [VAR=VALUE ...] [targets ...]
Set the environment variable name to value during the execution of the rake command. You can access the value by using ENV.
Used in combination with the -T and -D options, will force those options to show all the tasks, even the ones without comments.
Enable a full backtrace (i.e. like –trace, but without the task tracing
details). The output parameter is optional, but if specified it
controls where the backtrace output is sent. If output is
stdout, then backtrace output is directed to stardard output.
If output is
stderr, or if it is missing, then the
backtrace output is sent to standard error.
Used in combination with the -W options to force the output to contain
commented options only. This is the reverse of
Describe the tasks (matching optional PATTERN), then exit.
Do a dry run. Print the tasks invoked and executed, but do not actually execute any of the actions.
Execute some Ruby code and exit.
Execute some Ruby code, print the result, and exit.
Execute some Ruby code, then continue with normal task processing.
Display some help text and exit.
Specifies the maximun number of concurrent threads allowed. Rake will allocate threads as needed up to this maximum number.
If omitted, Rake will attempt to estimate the number of CPUs on the system and add 4 to that number.
The concurrent threads are used to execute the
prerequisites. Also see the
-m option which turns all tasks
(no -j) : Allow up to (# of CPUs + 4) number of threads --jobs : Allow unlimited number of threads --jobs=1 : Allow only one thread (the main thread) --jobs=16 : Allow up to 16 concurrent threads
Display job statistics at the completion of the run. By default, this will display the requested number of active threads (from the -j options) and the maximum number of threads in play at any given time.
If the optional level is
history, then a complete
trace of task history will be displayed on standard output.
Add directory to the list of directories searched for require.
Treat all tasks as multitasks. ('make/drake' semantics)
Do not search for a Rakefile in parent directories.
Display a list of all tasks and their immediate prerequisites.
Do not echo commands from FileUtils.
Use filename as the name of the rakefile. The default rakefile
rakefile taking precedence). If the rakefile is not found in
the current directory,
rake will search parent directories for
a match. The directory where the Rakefile is found will become the current
directory for the actions executed in the Rakefile.
Auto-import any .rake files in RAKELIBDIR. (default is 'rakelib')
Require name before executing the Rakefile.
Trace the rules resolution.
Like –quiet, but also suppresses the 'in directory' announcement.
Line matching the regular expression pattern will be removed from the backtrace output. Note that the –backtrace option is the full backtrace without these lines suppressed.
Use the system wide (global) rakefiles. The project Rakefile is ignored. By default, the system wide rakefiles are used only if no project Rakefile is found. On Unix-like system, the system wide rake files are located in $HOME/.rake. On a windows system they are stored in $APPDATA/Rake.
Use the project level Rakefile, ignoring the system-wide (global) rakefiles.
Display a list of the major tasks and their comments. Comments are defined using the “desc” command. If a pattern is given, then only tasks matching the pattern are displayed.
Turn on invoke/execute tracing. Also enable full backtrace on errors. The
output parameter is optional, but if specified it controls where
the trace output is sent. If output is
trace output is directed to stardard output. If output is
stderr, or if it is missing, then trace output is sent to
Echo the Sys commands to standard output.
Display the program version and exit.
Display tasks that match pattern and the file and line number where the task is defined. By default this option will display all tasks, not just the tasks that have descriptions.
Do not display the deprecation warnings.
In addition, any command line option of the form
VAR=VALUE will be added to the environment hash
ENV and may be tested in the Rakefile.