janky 0.9.14.rc1 → 0.9.14

data/CHANGES

@@ -1,4 +1,6 @@
-= 0.9.14 / 2012-??-??
+= 0.9.14 / 2013-02-26
+
+ * Many doc changes and improvements
 
  * Make the Jenkins job name human readable [Riley Guerin]
 

data/COPYING

@@ -1,4 +1,4 @@
-Copyright (c) 2011 GitHub, Inc. <https://github.com>
+Copyright (c) 2011-2012 GitHub, Inc. <https://github.com>
 
 Permission is hereby granted, free of charge, to any person
 obtaining a copy of this software and associated documentation

data/README.md

@@ -107,7 +107,20 @@ After configuring the app (see below), create the database:
 
 [gist]: https://gist.github.com/1497335
 
-### Configuring
+Upgrading
+---------
+
+We **strongly recommend** backing up your Janky database before upgrading.
+
+The general process is to then upgrade the gem, and then run migrate.  Here is how
+you do that on a local box you have access to (this process will differ for Heroku):
+    
+    cd [PATH-TO-JANKY]
+    gem update janky
+    rake db:migrate
+
+Configuring
+-----------
 
 Janky is configured using environment variables. Use the `heroku config`
 command:
@@ -139,7 +152,7 @@ Optional database settings:
 * `JANKY_DATABASE_SOCKET`: Path to the database socket. Example:
   `/var/run/mysql5/mysqld.sock`.
 
-#### GitHub Enterprise
+### GitHub Enterprise
 
 Using Janky with [GitHub Enterprise][ghe] requires one extra setting:
 
@@ -155,7 +168,7 @@ https://github.com/blog/1227-commit-status-api
 To update pull requests with the build status generate an OAuth token
 like so:
 
-  curl -u username:password -d '{ "scopes": [ "repo:status" ], "note": "janky" }' https://api.github.com/authorizations
+    curl -u username:password -d '{ "scopes": [ "repo:status" ], "note": "janky" }' https://api.github.com/authorizations
 
 then set `JANKY_GITHUB_STATUS_TOKEN`.
 
@@ -264,7 +277,9 @@ Contributing
 ------------
 
 Fork the [Janky repository on GitHub](https://github.com/github/janky) and
-send a Pull Request.
+send a Pull Request.  Note that any changes to behavior without tests will
+be rejected.  If you are adding significant new features, please add both 
+tests and documentation.
 
 Copying
 -------

data/janky.gemspec

@@ -8,6 +8,12 @@ Gem::Specification.new "janky", Janky::VERSION do |s|
   s.homepage = "https://github.com/github/janky"
   s.has_rdoc = false
 
+  s.post_install_message = <<-EOL
+If you are upgrading from Janky 0.9.13, you will want to add a JANKY_BRANCH parameter
+to your config/default.xml.erb. See
+https://github.com/github/janky/commit/0fc6214e3a75cc138aed46a2493980440e848aa3#commitcomment-1815400 for details.
+EOL
+
   # runtime
   s.add_dependency "rake", "~>0.9.2"
   s.add_dependency "sinatra", "~>1.3"

data/lib/janky/chat_service/hipchat.rb

@@ -13,7 +13,12 @@ module Janky
         @from = settings["JANKY_CHAT_HIPCHAT_FROM"] || "CI"
       end
 
-      def speak(message, room_id, options = {:color => "yellow"})
+      def speak(message, room_id, options = {})
+        default = {
+          :color => "yellow",
+          :message_format => "text"
+        }
+        options = default.merge(options)
         @client[room_id].send(@from, message, options)
       end
 

data/lib/janky/github/receiver.rb

@@ -25,6 +25,10 @@ module Janky
           return Rack::Response.new("Invalid signature", 403).finish
         end
 
+        if @request.content_type != "application/json"
+          return Rack::Response.new("Invalid Content-Type", 400).finish
+        end
+
         if !payload.head_commit
           return Rack::Response.new("Ignored", 400).finish
         end
@@ -57,10 +61,6 @@ module Janky
       end
 
       def data!
-        if @request.content_type != "application/json"
-          return Rack::Response.new("Invalid Content-Type", 400).finish
-        end
-
         body = ""
         @request.body.each { |chunk| body << chunk }
         body

data/lib/janky/hubot.rb

@@ -81,7 +81,7 @@ module Janky
     end
 
     # Get the status of a repository's branch.
-    get %r{\/([-_\.0-9a-zA-Z]+)\/([-_\.a-zA-z0-9\/]+)} do |repo_name, branch_name|
+    get %r{\/([-_\.0-9a-zA-Z]+)\/([-_\+\.a-zA-z0-9\/]+)} do |repo_name, branch_name|
       limit = params["limit"]
 
       repo   = find_repo(repo_name)
@@ -114,6 +114,9 @@ ci setup github/janky [name]
 ci toggle janky
 ci rooms
 ci set room janky development
+ci status
+ci status janky
+ci status janky/master
 EOS
     end
   end

data/lib/janky/version.rb

@@ -1,3 +1,3 @@
 module Janky
-  VERSION = "0.9.14.rc1"
+  VERSION = "0.9.14"
 end

metadata

@@ -1,15 +1,15 @@
 --- !ruby/object:Gem::Specification
 name: janky
 version: !ruby/object:Gem::Version
-  version: 0.9.14.rc1
-  prerelease: 7
+  version: 0.9.14
+  prerelease: 
 platform: ruby
 authors:
 - Simon Rozet
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-12-12 00:00:00.000000000 Z
+date: 2013-02-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake
@@ -303,7 +303,15 @@ files:
 - test/test_helper.rb
 homepage: https://github.com/github/janky
 licenses: []
-post_install_message: 
+post_install_message: ! 'If you are upgrading from Janky 0.9.13, you will want to
+  add a JANKY_BRANCH parameter
+
+  to your config/default.xml.erb. See
+
+  https://github.com/github/janky/commit/0fc6214e3a75cc138aed46a2493980440e848aa3#commitcomment-1815400
+  for details.
+
+'
 rdoc_options: []
 require_paths:
 - lib
@@ -316,9 +324,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
-  - - ! '>'
+  - - ! '>='
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.23