chef-handler-jenkins 0.2 → 0.3

data/README.md

@@ -20,7 +20,8 @@ This approach is best suited if you own the operation environment and want to do
 Use [chef_handler cookbook](http://community.opscode.com/cookbooks/chef_handler) and activate this handler via your recipe:
 
     chef_gem 'chef-handler-jenkins'
-    
+    require 'chef/handler/jenkins'
+
     chef_handler 'Chef::Handler::Jenkins' do
       source 'chef/handler/jenkins'
       arguments :url => 'http://myserver.acme.com/jenkins'

data/chef-handler-jenkins.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |g|
   g.name = 'chef-handler-jenkins'
-  g.version = '0.2'
+  g.version = '0.3'
 
   g.summary = 'Chef report handler for tracking with Jenkins'
   g.description = 'Track deployment of files through Jenkins'

data/lib/chef/handler/jenkins.rb

@@ -30,14 +30,14 @@ class Chef
             # res.checksum is SHA1 sum
           end
 
-          if res.class == Chef::Resource::SaladJenkinsTracking
-            # TODO is this a good way to check the class name?
-            updates << {
-                "path" => res.path,
-                "md5" => res.checksum,
-                "type" => res.class.name
-            }
-          end
+#          if res.class == Chef::Resource::SaladJenkinsTracking
+#            # TODO is this a good way to check the class name?
+#            updates << {
+#                "path" => res.path,
+#                "md5" => res.checksum,
+#                "type" => res.class.name
+#            }
+#          end
         end
 
         # add envelop to the data

metadata

@@ -1,12 +1,12 @@
 --- !ruby/object:Gem::Specification 
 name: chef-handler-jenkins
 version: !ruby/object:Gem::Version 
-  hash: 15
+  hash: 13
   prerelease: 
   segments: 
   - 0
-  - 2
-  version: "0.2"
+  - 3
+  version: "0.3"
 platform: ruby
 authors: 
 - Kohsuke Kawaguchi
@@ -14,7 +14,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2014-03-31 00:00:00 Z
+date: 2014-09-25 00:00:00 Z
 dependencies: 
 - !ruby/object:Gem::Dependency 
   name: chef