doable 0.0.5 → 0.0.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: ae66f67c0262597b37425580b07c0bad85c71621
-  data.tar.gz: 45ad1f5d2df72887db40ec4c441591b5ff02fe02
+  metadata.gz: 354051228fd6d5c41f7f79f8b75b171139549b2a
+  data.tar.gz: 914dae4667be4a6ef4f06d6a4633a31b9943c19a
 SHA512:
-  metadata.gz: 36b6cff4e14a55d0e0f35a50aef0a7935c36c973ae5e5637270191b75254db61839706718543a356c9aa15eb529b8bbf33af061bd110e67ff1627014e199b977
-  data.tar.gz: a56729ec3909eb736ce770aae53dd97582bf8ddfb4418bcbb3790aab8e4eddc77f215f9f04c2c35323f6cec05fbc4bdac5bed9c9076b2df3f02a1063b98fff58
+  metadata.gz: de16e3550956ae75ec4f4d1a8a25870667ea89157fc1fb01300a62fcd121de6e7153d243358ecf9f8751da85ca29fa9175a008dd88b529a2d79309c45df3fe16
+  data.tar.gz: 8c3d29bdcf1330c17fc07d139a1a434b7cf71497d11df9de8cf577479660fe6bac93dbe8ad925f91215e48c9f1663e8eecd3dbd1b8254a2774011032fa4c41c6

data/README.md

@@ -98,11 +98,13 @@ Here is an example job:
         check_disk_space @app_dir, (500 * 1024 * 1024)
       }
       
+      # Create our user
       j.step    { 
         @user  = "cooluser"
         find_or_create_user @user, File.dirname(@app_dir)
       }
       
+      # Unpack our software, and define a way to rollback this step
       j.step    {
         find_or_create_directory @app_dir
         
@@ -115,18 +117,38 @@ Here is an example job:
         remove(@app_dir)
       }
       
+      # Rnn the software as our user
       j.step     {
         run_as_user @user, File.join(@app_dir, "/bin", "start.sh")
       }
     end
     
-    job3.run
+    job3.run # and... go!
 
 Hopefully this demonstrates how to get access to additional helper methods. Also, you may have noticed the `rollback` method added to the step for uncompressing the tarball. If things go wrong, rollbacks can be run to revert changes. To do so, just do this:
 
     job3.rollback!
 
-The `Job` instance also has many other methods available for accessing its internals.
+The `Job` instance also has many other methods available for accessing its internals. For instance, it is possible to query a job to determine if it is running multiple threads:
+
+    job3.multitasking?
+
+Or queries its steps for their status and whether they were successful:
+
+    #!ruby
+    job3.steps.collect {|s| puts "Status: #{s.status}; Success: #{s.successful?}" }
+
+If an individual step failed, it can be retried simply:
+
+    #!ruby
+    job3.steps[2].retry
+
+It's also possible to trigger named hooks externally. Let's say we have a defined a hook called "cleanup":
+
+    #!ruby
+    some_job_with_hooks.trigger(:cleanup)
+
+There are a lot of options for interacting with the internals of jobs, both within the definition of a job, and after.
 
 RubyDoc
 -------

data/lib/doable/job.rb

@@ -73,7 +73,7 @@ module Doable
     def attempt(options = {}, &block)
       @steps << Step.new(self, options) do
         begin
-          block.call
+          self.instance_exec(&block)
         rescue SkipStep => e
           raise e # We'll rescue this somewhere higher up the stack
         rescue => e
@@ -89,7 +89,7 @@ module Doable
     # @return [Step]
     def background(options = {}, &block)
       @steps << Step.new(self, options) do
-        @threads << Thread.new { block.call }
+        @threads << Thread.new { self.instance_exec(&block) }
       end
       @steps.last # return the last step (the one we just defined)
     end # background()

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: doable
 version: !ruby/object:Gem::Version
-  version: 0.0.5
+  version: 0.0.6
 platform: ruby
 authors:
 - Jonathan Gnagy