chef-handler-jenkins 0.1

data/Gemfile

@@ -0,0 +1,9 @@
+source 'https://rubygems.org'
+
+# ruby ">= 2.0.0"
+
+gemspec
+
+group :development do
+  gem 'pry'
+end

data/LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2014, Jenkins project
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,28 @@
+This is a Chef report handler that allows [Jenkins](http://jenkins-ci.org/) to track
+when files are deployed where.
+
+# Usage
+There are two ways to configure Chef Handler.
+
+## Via solo.rb or client.rb
+Install `chef-handler-jenkins` gem upfront first:
+
+    $ gem install chef-handler-jenkins
+
+Then configure Chef to use it with the following lines. For chef-solo, you can put that in your [/etc/chef/solo.rb](http://docs.opscode.com/config_rb_solo.html) (or your local override). For chef-client, you can put that in your [/etc/chef/client.rb](http://docs.opscode.com/config_rb_client.html).
+
+   require 'chef/handler/jenkins'
+   report_handlers << Chef::Handler::Jenkins.new(:url => 'http://myserver.acme.com/jenkins')
+ 
+This approach is best suited if you own the operation environment and want to do the deployment integration without modifying recipes.
+
+## Via recipes
+Use [chef_handler cookbook](http://community.opscode.com/cookbooks/chef_handler) and activate this handler via your recipe:
+
+    chef_gem 'chef-handler-jenkins'
+
+    chef_handler 'Chef::Handler::Jenkins' do
+      source 'chef/handler/jenkins'
+      arguments :url => 'http://myserver.acme.com/jenkins'
+      action :enable
+    end

data/chef-handler-jenkins.gemspec

@@ -0,0 +1,15 @@
+Gem::Specification.new do |g|
+  g.name = 'chef-handler-jenkins'
+  g.version = '0.1'
+
+  g.summary = 'Chef report handler for tracking with Jenkins'
+  g.description = 'Track deployment of files through Jenkins'
+  g.authors = ['Kohsuke Kawaguchi']
+  g.email = 'kk@kohsuke.org'
+  g.homepage = 'http://jenkins-ci.org/'
+
+  g.require_paths = ['lib']
+  g.files = `git ls-files`.split($\)
+
+  g.add_dependency 'chef', '>=11.6'
+end

data/lib/chef/handler/jenkins.rb

@@ -0,0 +1,93 @@
+require "chef/log"
+require 'digest/md5'
+
+module Chef
+  module Handler
+    #noinspection RubyStringKeysInHashInspection
+    class TrackingHandler < Chef::Handler
+      def initialize(config)
+        @config = config
+        raise ArgumentError, 'Jenkins URL is not specified' unless @config[:url]
+      end
+
+      def report
+        # for interactive exploration
+        #require 'pry'
+        #binding.pry
+
+        updates = []
+
+        puts "Machine name: #{run_status.node.name}"
+        run_status.updated_resources.each do |res|
+          # res is instance of CookbookFile
+          if res.class <= Chef::Resource::File
+            updates << {
+              "path" => res.path,
+              "action" => res.action,
+              "md5" => Digest::MD5.hexdigest(IO.read(res.path)),
+              "type" => res.class.name
+            }
+            # 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
+        end
+
+        # add envelop to the data
+        env = {
+          "node" => run_status.node.name,
+          "environment" => run_status.node.environment,
+          "start_time" => run_status.start_time.rfc2822,
+          "end_time" => run_status.end_time.rfc2822,
+          "updates" => updates
+        }
+
+        print env.inspect
+
+        if false  # TODO: work in progress
+        # if !Chef::Config[:solo]
+          # databag submission only works in chef-client
+          submit_databag run_status,env
+        end
+        submit_jenkins run_status,env
+      end
+
+      # Submit the tracking report as a databag
+      #
+      # @param [Chef::RunStatus] run_status
+      # @param [Hash] report
+      def submit_databag(run_status, env)
+        # TODO: too expensive to load them. all we want to do is to check if databag exists
+        #begin
+        #  Chef::DataBag.load("jenkins")
+        #rescue Net::HTTPServerException => e
+        #  if e.response.code=="404"
+        #    bag = Chef::DataBag.new
+        #    bag.name "jenkins"
+        #    bag.save
+        #  end
+        #end
+
+        i = Chef::DataBagItem.new
+        i.data_bag("jenkins")  # set the name
+
+        id = run_status.node.name + '_' + run_status.end_time.strftime("%Y%m%d-%H%M%S")
+
+        i.raw_data = env
+        i.save id
+      end
+
+      def submit_jenkins(run_status, env)
+        r = Chef::REST.new(@config[:url])
+        r.post("chef/report", env)
+      end
+    end
+  end
+end

metadata

@@ -0,0 +1,83 @@
+--- !ruby/object:Gem::Specification 
+name: chef-handler-jenkins
+version: !ruby/object:Gem::Version 
+  hash: 9
+  prerelease: 
+  segments: 
+  - 0
+  - 1
+  version: "0.1"
+platform: ruby
+authors: 
+- Kohsuke Kawaguchi
+autorequire: 
+bindir: bin
+cert_chain: []
+
+date: 2014-03-31 00:00:00 Z
+dependencies: 
+- !ruby/object:Gem::Dependency 
+  name: chef
+  prerelease: false
+  requirement: &id001 !ruby/object:Gem::Requirement 
+    none: false
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        hash: 43
+        segments: 
+        - 11
+        - 6
+        version: "11.6"
+  type: :runtime
+  version_requirements: *id001
+description: Track deployment of files through Jenkins
+email: kk@kohsuke.org
+executables: []
+
+extensions: []
+
+extra_rdoc_files: []
+
+files: 
+- Gemfile
+- LICENSE
+- README.md
+- chef-handler-jenkins.gemspec
+- lib/chef/handler/jenkins.rb
+homepage: http://jenkins-ci.org/
+licenses: []
+
+post_install_message: 
+rdoc_options: []
+
+require_paths: 
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement 
+  none: false
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      hash: 3
+      segments: 
+      - 0
+      version: "0"
+required_rubygems_version: !ruby/object:Gem::Requirement 
+  none: false
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      hash: 3
+      segments: 
+      - 0
+      version: "0"
+requirements: []
+
+rubyforge_project: 
+rubygems_version: 1.8.15
+signing_key: 
+specification_version: 3
+summary: Chef report handler for tracking with Jenkins
+test_files: []
+
+has_rdoc: