taskinator 0.0.9 → 0.0.10

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 75ca53362ea028543eae463a901056c08049ecd7
-  data.tar.gz: 7971999d4c6c962c057329ba215394af3830ac5f
+  metadata.gz: 620c8ca7a67e65cbefa9afdcbda7b5f0d1488dbf
+  data.tar.gz: 2afa5217745d65926c9ec9c301bdb307d54b8a38
 SHA512:
-  metadata.gz: ae31ec1d8ce1ca9c16aa38425150525c3b7c9e51cc2991935ea42522e63f05e217b3e179403eebcd9fc2d48d8c512375074dc53fd3ee2c262aeb19effd146179
-  data.tar.gz: aa3e70be0f952329ce8857d1e74aac32395f27c72848af95aad81a61e6adbd8098933d8ee38ec6b9e8f792e5f82684c02afddf9a51b91ffcc63b2408f64b1783
+  metadata.gz: 3e175cd7c5836e8a20f4d03fe7c57acfa098388edeff543e184d000181f3e1df36fd5083f6b5968ebd7977daa91a8e41d1664758caf559db49c1d328b0fb3e58
+  data.tar.gz: 954389c2d44e70db697b7d81b1ef2bd2e337a227669009083278da063369bfeca0c3d2bb6eef920759a66cc3f91cb961db3a18c74e7f8531b82a6e6f8910c769

data/Gemfile.lock

@@ -8,7 +8,7 @@ GIT
 PATH
   remote: .
   specs:
-    taskinator (0.0.9)
+    taskinator (0.0.10)
       connection_pool (>= 2.0.0)
       json (>= 1.8.1)
       redis (>= 3.0.6)
@@ -17,39 +17,40 @@ PATH
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (4.1.7)
-      i18n (~> 0.6, >= 0.6.9)
+    activesupport (4.2.0)
+      i18n (~> 0.7)
       json (~> 1.7, >= 1.7.7)
       minitest (~> 5.1)
-      thread_safe (~> 0.1)
+      thread_safe (~> 0.3, >= 0.3.4)
       tzinfo (~> 1.1)
     byebug (2.7.0)
       columnize (~> 0.3)
       debugger-linecache (~> 1.2)
-    celluloid (0.15.2)
-      timers (~> 1.1.0)
+    celluloid (0.16.0)
+      timers (~> 4.0.0)
     coderay (1.1.0)
-    columnize (0.8.9)
-    connection_pool (2.0.0)
-    coveralls (0.7.1)
-      multi_json (~> 1.3)
-      rest-client
-      simplecov (>= 0.7)
-      term-ansicolor
-      thor
+    columnize (0.9.0)
+    connection_pool (2.1.1)
+    coveralls (0.7.11)
+      multi_json (~> 1.10)
+      rest-client (>= 1.6.8, < 2)
+      simplecov (~> 0.9.1)
+      term-ansicolor (~> 1.3)
+      thor (~> 0.19.1)
     debugger-linecache (1.2.0)
-    delayed_job (4.0.4)
-      activesupport (>= 3.0, < 4.2)
+    delayed_job (4.0.6)
+      activesupport (>= 3.0, < 5.0)
     diff-lcs (1.2.5)
     docile (1.1.5)
-    i18n (0.6.11)
-    json (1.8.1)
+    hitimes (1.2.2)
+    i18n (0.7.0)
+    json (1.8.2)
     method_source (0.8.2)
     mime-types (2.4.3)
-    minitest (5.4.2)
+    minitest (5.5.1)
     mono_logger (1.1.0)
     multi_json (1.10.1)
-    netrc (0.8.0)
+    netrc (0.10.3)
     pry (0.9.12.6)
       coderay (~> 1.0)
       method_source (~> 0.8)
@@ -57,11 +58,11 @@ GEM
     pry-byebug (1.3.2)
       byebug (~> 2.7)
       pry (~> 0.9.12)
-    rack (1.5.2)
+    rack (1.6.0)
     rack-protection (1.5.3)
       rack
     rake (10.3.2)
-    redis (3.1.0)
+    redis (3.2.1)
     redis-namespace (1.5.1)
       redis (~> 3.0, >= 3.0.4)
     resque (1.25.2)
@@ -75,32 +76,33 @@ GEM
       rspec-core (>= 3.0.0)
       rspec-expectations (>= 3.0.0)
       rspec-mocks (>= 3.0.0)
-    rest-client (1.7.2)
+    rest-client (1.7.3)
       mime-types (>= 1.16, < 3.0)
       netrc (~> 0.7)
-    rspec (3.1.0)
-      rspec-core (~> 3.1.0)
-      rspec-expectations (~> 3.1.0)
-      rspec-mocks (~> 3.1.0)
-    rspec-core (3.1.7)
-      rspec-support (~> 3.1.0)
-    rspec-expectations (3.1.2)
+    rspec (3.2.0)
+      rspec-core (~> 3.2.0)
+      rspec-expectations (~> 3.2.0)
+      rspec-mocks (~> 3.2.0)
+    rspec-core (3.2.1)
+      rspec-support (~> 3.2.0)
+    rspec-expectations (3.2.0)
       diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.1.0)
-    rspec-mocks (3.1.3)
-      rspec-support (~> 3.1.0)
-    rspec-support (3.1.2)
-    sidekiq (3.2.6)
-      celluloid (= 0.15.2)
-      connection_pool (>= 2.0.0)
+      rspec-support (~> 3.2.0)
+    rspec-mocks (3.2.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.2.0)
+    rspec-support (3.2.2)
+    sidekiq (3.3.2)
+      celluloid (>= 0.16.0)
+      connection_pool (>= 2.1.1)
       json
       redis (>= 3.0.6)
       redis-namespace (>= 1.3.1)
-    simplecov (0.9.1)
+    simplecov (0.9.2)
       docile (~> 1.1.0)
       multi_json (~> 1.0)
-      simplecov-html (~> 0.8.0)
-    simplecov-html (0.8.0)
+      simplecov-html (~> 0.9.0)
+    simplecov-html (0.9.0)
     sinatra (1.4.5)
       rack (~> 1.4)
       rack-protection (~> 1.4)
@@ -111,8 +113,9 @@ GEM
     thor (0.19.1)
     thread_safe (0.3.4)
     tilt (1.4.1)
-    timers (1.1.0)
-    tins (1.3.3)
+    timers (4.0.1)
+      hitimes
+    tins (1.3.4)
     tzinfo (1.2.2)
       thread_safe (~> 0.1)
     vegas (0.1.11)

data/README.md

@@ -7,7 +7,7 @@
 [![Dependency Status](https://gemnasium.com/virtualstaticvoid/taskinator.svg)](https://gemnasium.com/virtualstaticvoid/taskinator)
 
 A simple orchestration library for running complex processes or workflows in Ruby. Processes are defined using a simple DSL, where the sequences and
-tasks are defined. Processes can then queued for execution. Sequences can be sychronous or asynchronous, and the overall process can be monitored
+tasks are defined. Processes can then be queued for execution. Sequences can be synchronous or asynchronous, and the overall process can be monitored
 for completion or failure.
 
 Processes and tasks are executed by background workers and you can use any one of the following gems:
@@ -26,7 +26,7 @@ Redis 2.4 or greater is required.
 
 One of the following background worker queue gems: `resque`, `sidekiq` or `delayed_job`.
 
-_Note:_ `resque` or `sidekiq` is recommended since they use Redis as a backing store as well.
+_NOTE:_ `resque` or `sidekiq` is recommended since they use Redis as a backing store as well.
 
 ## Installation
 
@@ -56,7 +56,7 @@ module MyProcess
 end
 ```
 
-Define the process, using the `define_process` method.
+Define the process using the `define_process` method.
 
 ```ruby
 module MyProcess
@@ -69,8 +69,8 @@ module MyProcess
 end
 ```
 
-The `define_process` method optionally takes the list of expected arguments which are used to validate the
-arguments supplied when creating a new process. These should be specified with symbols.
+The `define_process` method optionally takes the list of expected arguments which are used to validate the arguments supplied when creating a new process.
+These should be specified with symbols.
 
 ```ruby
 module MyProcess
@@ -86,11 +86,9 @@ end
 process = MyProcess.create_process Date.today, :option_1 => true
 ```
 
-NOTE: The current implementation performs a naive check on the count of arguments, but this will be
-improved in subsequent versions.
+_NOTE:_ The current implementation performs a naive check on the count of arguments.
 
-Next, specify the tasks with their corresponding implementation methods, that make up the process,
-using the `task` method and providing the `method` to execute for the task.
+Next, specify the tasks with their corresponding implementation methods, that make up the process, using the `task` method and providing the `method` to execute for the task.
 
 ```ruby
 module MyProcess
@@ -144,11 +142,10 @@ module MyProcess
 end
 ```
 
-It is likely that you have already have worker classes for one of the queueing libraries, such as resque or delayed_job, and wish to
-reuse them for executing them in the sequence defined by the process definition.
+It is likely that you already have worker classes for one of the queueing libraries, such as resque or delayed_job, and wish to reuse them for executing them in the sequence defined by the process definition.
 
-You define a `job` step, providing the class of the worker, and them taskinator will execute that worker as part of the process definition.
-The `job` step will be queued and executed on the configured queue for `delayed_job`, or that of the worker for `resque` and `sidekiq`.
+Define a `job` step, providing the class of the worker, and then taskinator will execute that worker as part of the process definition.
+The `job` step will be queued and executed on same queue as configured by `delayed_job`, or that of the worker for `resque` and `sidekiq`.
 
 ```ruby
 # E.g. A resque worker
@@ -173,8 +170,7 @@ end
 ```
 
 You can also define data driven tasks using the `for_each` method, which takes an iterator method name as an argument.
-The iterator method yields the items to produce a parameterized task for that item. Notice that the task method
-takes a parameter in this case, which will be the item provided by the iterator.
+The iterator method yields the parameters necessary for the task or job. Notice that the task method takes a parameter in this case, which will be the return values provided by the iterator.
 
 ```ruby
 module MyProcess
@@ -198,8 +194,7 @@ end
 ```
 
 It is possible to branch the process logic based on the options hash passed in when creating a process.
-The `options?` method takes the options key as an argument and calls the supplied block if the option
-is present and it's value is truthy.
+The `options?` method takes the options key as an argument and calls the supplied block if the option is present and it's value is truthy.
 
 ```ruby
 module MyProcess
@@ -234,7 +229,7 @@ process2.tasks.count #=> 1
 ```
 
 In addition, it is possible to transform the arguments used by a task or job, by including a `transform` step in the definition.
-Similarly to the `for_each` method, `transform` takes a method name as an argument. The transformer method must yield the new arguments as required.
+Similarly for the `for_each` method, `transform` takes a method name as an argument. The transformer method must yield the new arguments as required.
 
 ```ruby
 module MyProcess
@@ -370,8 +365,7 @@ To best understand how arguments are handled, you need to break it down into 3 p
   * Creation and
   * Execution
 
-Firstly, a process definition is declarative in that the `define_process` and a mix of `sequential`, `concurrent`, `for_each`,
-`task` and `job` directives provide the way to specify the sequencing of the steps for the process.
+Firstly, a process definition is declarative in that the `define_process` and a mix of `sequential`, `concurrent`, `for_each`, `task` and `job` directives provide the way to specify the sequencing of the steps for the process.
 Taskinator will interprete this definition and execute each step in the desired sequence or concurrency.
 
 Consider the following process definition:
@@ -418,11 +412,9 @@ end
 
 There are three tasks; namely `:work_step_1`, `:work_step_2` and `:work_step_3`.
 
-The third task, `:work_step_3`, is built up using the `for_each` iterator, which means that the number of `:work_step_3` tasks
-will depend on how many times the `additional_step` iterator method yields to the definition.
+The third task, `:work_step_3`, is built up using the `for_each` iterator, which means that the number of `:work_step_3` tasks will depend on how many times the `additional_step` iterator method yields to the definition.
 
-This brings us to the creation part. When `create_process` is called on the given module, you provide arguments to it, which will get
-passed onto the respective `task` and `for_each` iterator methods.
+This brings us to the creation part. When `create_process` is called on the given module, you provide arguments to it, which will get passed onto the respective `task` and `for_each` iterator methods.
 
 So, considering the `MySimpleProcess` module shown above, `work_step_1`, `work_step_2` and `work_step_3` methods each expect arguments.
 These will ultimately come from the arguments passed into the `create_process` method.
@@ -544,9 +536,7 @@ process.execute
 
 ```
 
-In reality, each task is executed by a worker process, possibly on another host, so the execution process isn't as simple,
-but this example should help you to understand conceptually how the process is executed, and how the arguments are propagated
-through.
+In reality, each task is executed by a worker process, possibly on another host, so the execution process isn't as simple, but this example should help you to understand conceptually how the process is executed, and how the arguments are propagated through.
 
 ### Monitoring
 
@@ -564,9 +554,8 @@ end
 
 ### Redis
 
-By default Taskinator assumes Redis is located at `localhost:6397`. This is fine for development, but for many production environments
-you will need to poiint to an external Redis server. You may also what to use a namespace for the Redis keys.
-NOTE: The configuration hash _must_ have symbolized keys.
+By default Taskinator assumes Redis is located at `localhost:6397`. This is fine for development, but for many production environments you will need to point to an external Redis server. You may also what to use a namespace for the Redis keys.
+_NOTE:_ The configuration hash _must_ have symbolized keys.
 
 ```ruby
 Taskinator.configure do |config|
@@ -580,13 +569,11 @@ end
 Or, alternatively, via an `ENV` variable
 
 Set the `REDIS_PROVIDER` environment variable to the Redis server url.
-E.g. On Heroku, with RedisGreen: set REDIS_PROVIDER=REDISGREEN_URL and Taskinator will use the value of the `REDISGREEN_URL`
-environment variable when connecting to Redis.
+E.g. On Heroku, with RedisGreen: set REDIS_PROVIDER=REDISGREEN_URL and Taskinator will use the value of the `REDISGREEN_URL` environment variable when connecting to Redis.
 
 You may also use the generic `REDIS_URL` which may be set to your own private Redis server.
 
-The Redis configuration leverages the same setup as `sidekiq`. For advanced options, checkout the
-[Sidekiq Advanced Options](https://github.com/mperham/sidekiq/wiki/Advanced-Options#complete-control) wiki for more information.
+The Redis configuration leverages the same setup as `sidekiq`. For advanced options, checkout the [Sidekiq Advanced Options](https://github.com/mperham/sidekiq/wiki/Advanced-Options#complete-control) wiki for more information.
 
 ### Queues
 
@@ -622,6 +609,4 @@ Portions of code are from the Sidekiq project, Copyright (c) Contributed Systems
 
 Inspired by the [sidekiq](https://github.com/mperham/sidekiq) and [workflow](https://github.com/geekq/workflow) gems.
 
-For other workflow solutions, checkout [Stonepath](https://github.com/bokmann/stonepath), the now deprecated
-[ruote](https://github.com/jmettraux/ruote) gem and [workflow](https://github.com/geekq/workflow). Alternatively, for a robust
-enterprise ready solution checkout the [AWS Flow Framework for Ruby](http://docs.aws.amazon.com/amazonswf/latest/awsrbflowguide/welcome.html).
+For other workflow solutions, checkout [Stonepath](https://github.com/bokmann/stonepath), the now deprecated [ruote](https://github.com/jmettraux/ruote) gem and [workflow](https://github.com/geekq/workflow). Alternatively, for a robust enterprise ready solution checkout the [AWS Flow Framework for Ruby](http://docs.aws.amazon.com/amazonswf/latest/awsrbflowguide/welcome.html).

data/lib/taskinator/version.rb

@@ -1,3 +1,3 @@
 module Taskinator
-  VERSION = "0.0.9"
+  VERSION = "0.0.10"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: taskinator
 version: !ruby/object:Gem::Version
-  version: 0.0.9
+  version: 0.0.10
 platform: ruby
 authors:
 - Chris Stefano
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-12-19 00:00:00.000000000 Z
+date: 2015-02-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: redis
@@ -245,6 +245,7 @@ files:
 - lib/taskinator/tasks.rb
 - lib/taskinator/version.rb
 - lib/taskinator/visitor.rb
+- processes_workflow.png
 - sequence.txt
 - spec/examples/process_examples.rb
 - spec/examples/queue_adapter_examples.rb
@@ -273,6 +274,7 @@ files:
 - spec/taskinator/tasks_spec.rb
 - spec/taskinator/visitor_spec.rb
 - taskinator.gemspec
+- tasks_workflow.png
 homepage: https://github.com/virtualstaticvoid/taskinator
 licenses:
 - MIT