The ProcessExecuter Gem

Gem Version
Build Status
Maintainability
Test Coverage

Features

This gem contains the following features:

ProcessExecuter::MonitoredPipe

ProcessExecuter::MonitoredPipe streams data sent through a pipe to one or more writers.

When a new MonitoredPipe is created, an pipe is created (via IO.pipe) and
a thread is created which reads data as it is written written to the pipe.

Data that is read from the pipe is written one or more writers passed to
MonitoredPipe#initialize.

This is useful for streaming process output (stdout and/or stderr) to anything that has a
#write method: a string buffer, a file, or stdout/stderr as seen in the following example:

require 'stringio'
require 'process_executer'

output_buffer = StringIO.new
out_pipe = ProcessExecuter::MonitoredPipe.new(output_buffer)
pid, status = Process.wait2(Process.spawn('echo "Hello World"', out: out_pipe))
output_buffer.string #=> "Hello World\n"

MonitoredPipe#initialize can take more than one writer so that pipe output can be
streamed (or teed) to multiple writers at the same time:

require 'stringio'
require 'process_executer'

output_buffer = StringIO.new
output_file = File.open('process.out', 'w')
out_pipe = ProcessExecuter::MonitoredPipe.new(output_buffer, output_file)
pid, status = Process.wait2(Process.spawn('echo "Hello World"', out: out_pipe))
output_file.close
output_buffer.string #=> "Hello World\n"
File.read('process.out') #=> "Hello World\n"

Since the data is streamed, any object that implements #write can be used. For insance,
you can use it to parse process output as a stream which might be useful for long XML
or JSON output.

ProcessExecuter.spawn

ProcessExecuter.spawn has the same interface as Process.spawn but has two
important behaviorial differences:

  1. It blocks until the subprocess finishes
  2. A timeout can be specified using the :timeout option

If the command does not terminate before the timeout, the process is killed by
sending it the SIGKILL signal.

Installation

Install the gem and add to the application’s Gemfile by executing:

bundle add process_executer

If bundler is not being used to manage dependencies, install the gem by executing:

gem install process_executer

Usage

See the examples in the project’s YARD documentation.

Development

After checking out the repo, run bin/setup to install dependencies. Then, run
rake spec to run the tests. You can also run bin/console for an interactive
prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To
release a new version, update the version number in version.rb, and then run
bundle exec rake release, which will create a git tag for the version, push git
commits and the created tag, and push the .gem file to
rubygems.org.

Contributing

Bug reports and pull requests are welcome on our
GitHub issue tracker

License

The gem is available as open source under the terms of the MIT License.