houston-core 0.5.0.beta1 → 0.5.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 7a9edb88c1dfdec80ec2121bf68abc2fad01281f
-  data.tar.gz: 8697e901809002abec27b5af0735b84ccea631b8
+  metadata.gz: f27a41cf18a79ea1e6804607c6144712bb5cab1c
+  data.tar.gz: 6a6a00a46f6c47375f3835ace2d6101e184678ce
 SHA512:
-  metadata.gz: 2eef6a5f7c47f18bbcf86ea06a87282f7a2175a0b80c229d4d904553baed9bc936b04a9dcfe7f5326004ac9f5df66b2b642412824eae62e7a122175fbfc9855c
-  data.tar.gz: a57953c9b89e3260e67c46288c1be2ee15f9aa15c5af136a79200c7fb591db54ee74df703bd357609c9036fae5e830f4a3edd0c143e0704ac755c737c3a16a83
+  metadata.gz: d3efec7157215eb18771ea14d7f39cc8e04ee4c00d67d5b6491ff943d8dcf31e5405815cbb577bac1a4d8d92fe582f31fd7763fb03489073670fedc0c5736b42
+  data.tar.gz: ec0521adbd55e4bd34da8595145adfab8c250c843afdc67a927871d9559423013e889efef2df48fec0bd0858d0385d1ba04195efb2d25756cbd1e85d747f7ab7

data/.codeclimate.yml

@@ -21,8 +21,6 @@ engines:
     enabled: true
   csslint:
     enabled: true
-  bundler-audit:
-    enabled: true
 
 # Engines can analyze files and report issues on them, but you can separately
 # decide which files will receive ratings based on those issues. This is

data/.gitignore

@@ -11,6 +11,9 @@
 /log/*.log
 /tmp
 
+# Ignore built gems
+/pkg
+
 # Ignore misc.
 REVISION
 .sass-cache

data/Gemfile

@@ -15,6 +15,7 @@ group :test do
   gem "rr"
   gem "webmock", require: "webmock/minitest"
   gem "factory_girl_rails"
+  gem "test_after_commit"
   
   # For Jenkins
   gem "therubyracer"

data/Gemfile.lock

@@ -1,82 +1,81 @@
 PATH
   remote: .
   specs:
-    houston-core (0.5.0.beta1)
-      activerecord-insert_many
+    houston-core (0.5.0)
+      activerecord-import
       activerecord-pluck_in_batches
       addressable
       backbone-rails (~> 1.0.0)
       boblail-unfuddle
       bundler
-      cancan
+      cancan (~> 1.6.10)
       codeclimate-test-reporter (= 0.4.1)
       coffee-rails (~> 4.0.0)
       default_value_for (= 3.0.0.1)
       devise (~> 3.0.0)
-      devise_invitable
-      engineyard
-      faraday
-      faraday-http-cache
-      faraday-raise-errors
-      gemnasium
-      gemoji
-      googlecharts
+      devise_invitable (~> 1.2.1)
+      engineyard (~> 3.2.1)
+      faraday (~> 0.8.10)
+      faraday-http-cache (~> 1.2.2)
+      faraday-raise-errors (~> 0.2.0)
+      gemoji (~> 2.1.0)
+      googlecharts (~> 1.6.12)
       handlebars_assets (~> 0.18.0)
       houston-devise_ldap_authenticatable
       houston-oauth-plugin
       houston-vestal_versions
-      hpricot
+      hpricot (~> 0.8.6)
       neat-rails
       nested_editor_for
-      nokogiri
-      octokit
-      oj
+      nokogiri (~> 1.6.6.2)
+      octokit (~> 4.1.0)
+      oj (~> 2.12.14)
       openxml-xlsx
       pg (~> 0.18.2)
-      pg_search
-      premailer
+      pg_search (~> 1.0.5)
+      premailer (~> 1.8.6)
       progressbar
-      rack-utf8_sanitizer
-      rails (~> 4.1.0)
-      redcarpet
-      rufus-scheduler
-      rugged (~> 0.23.0)
+      rack-utf8_sanitizer (~> 1.3.1)
+      rails (~> 4.1.13)
+      redcarpet (~> 3.3.2)
+      rufus-scheduler (~> 3.1.4)
+      rugged (~> 0.23.2)
       sass-rails (~> 4.0.0)
-      simplecov
-      strongbox
+      simplecov (~> 0.9.1)
+      strongbox (~> 0.7.2)
       sugar-rails
-      thread_safe
+      thread_safe (~> 0.3.5)
       uglifier (>= 1.3.0)
       whenever (= 0.9.2)
 
 GEM
   remote: https://rubygems.org/
   specs:
-    actionmailer (4.1.12)
-      actionpack (= 4.1.12)
-      actionview (= 4.1.12)
+    actionmailer (4.1.13)
+      actionpack (= 4.1.13)
+      actionview (= 4.1.13)
       mail (~> 2.5, >= 2.5.4)
-    actionpack (4.1.12)
-      actionview (= 4.1.12)
-      activesupport (= 4.1.12)
+    actionpack (4.1.13)
+      actionview (= 4.1.13)
+      activesupport (= 4.1.13)
       rack (~> 1.5.2)
       rack-test (~> 0.6.2)
-    actionview (4.1.12)
-      activesupport (= 4.1.12)
+    actionview (4.1.13)
+      activesupport (= 4.1.13)
       builder (~> 3.1)
       erubis (~> 2.7.0)
-    activemodel (4.1.12)
-      activesupport (= 4.1.12)
+    activemodel (4.1.13)
+      activesupport (= 4.1.13)
       builder (~> 3.1)
-    activerecord (4.1.12)
-      activemodel (= 4.1.12)
-      activesupport (= 4.1.12)
+    activerecord (4.1.13)
+      activemodel (= 4.1.13)
+      activesupport (= 4.1.13)
       arel (~> 5.0.0)
-    activerecord-insert_many (0.1.0)
-      activerecord
+    activerecord-import (0.10.0)
+      activerecord (>= 3.0)
     activerecord-pluck_in_batches (0.1.0)
       activerecord
-    activesupport (4.1.12)
+    activesupport (4.1.13)
       i18n (~> 0.6, >= 0.6.9)
       json (~> 1.7, >= 1.7.7)
       minitest (~> 5.1)
@@ -115,7 +114,7 @@ GEM
     coffee-script-source (1.9.1.1)
     crack (0.4.2)
       safe_yaml (~> 1.0.0)
-    css_parser (1.3.6)
+    css_parser (1.3.7)
       addressable
     default_value_for (3.0.0.1)
       activerecord (>= 3.2.0, < 5.0)
@@ -128,7 +127,7 @@ GEM
       actionmailer (>= 3.2.6, < 5)
       devise (~> 3.0.0)
     docile (1.1.5)
-    domain_name (0.5.24)
+    domain_name (0.5.25)
       unf (>= 0.0.5, < 1.0.0)
     engineyard (3.2.1)
       engineyard-cloud-client (~> 2.1)
@@ -151,13 +150,12 @@ GEM
     factory_girl_rails (4.5.0)
       factory_girl (~> 4.5.0)
       railties (>= 3.0.0)
-    faraday (0.8.10)
+    faraday (0.8.11)
       multipart-post (~> 1.2.0)
     faraday-http-cache (1.2.2)
       faraday (~> 0.8)
     faraday-raise-errors (0.2.0)
       faraday
-    gemnasium (3.2.1)
     gemoji (2.1.0)
     googlecharts (1.6.12)
     handlebars_assets (0.18)
@@ -191,9 +189,9 @@ GEM
     mail (2.6.3)
       mime-types (>= 1.16, < 3)
     method_source (0.8.2)
-    mime-types (2.6.1)
+    mime-types (2.6.2)
     mini_portile (0.6.2)
-    minitest (5.8.0)
+    minitest (5.8.1)
     minitest-reporters (1.0.7)
       ansi
       builder
@@ -218,7 +216,7 @@ GEM
       multi_json (~> 1.3)
       multi_xml (~> 0.5)
       rack (~> 1.2)
-    octokit (4.1.0)
+    octokit (4.1.1)
       sawyer (~> 0.6.0, >= 0.5.3)
     oj (2.12.14)
     open_xml_package (0.1.0)
@@ -246,23 +244,23 @@ GEM
       rack (>= 1.0)
     rack-utf8_sanitizer (1.3.1)
       rack (~> 1.0)
-    rails (4.1.12)
-      actionmailer (= 4.1.12)
-      actionpack (= 4.1.12)
-      actionview (= 4.1.12)
-      activemodel (= 4.1.12)
-      activerecord (= 4.1.12)
-      activesupport (= 4.1.12)
+    rails (4.1.13)
+      actionmailer (= 4.1.13)
+      actionpack (= 4.1.13)
+      actionview (= 4.1.13)
+      activemodel (= 4.1.13)
+      activerecord (= 4.1.13)
+      activesupport (= 4.1.13)
       bundler (>= 1.3.0, < 2.0)
-      railties (= 4.1.12)
+      railties (= 4.1.13)
       sprockets-rails (~> 2.0)
-    railties (4.1.12)
-      actionpack (= 4.1.12)
-      activesupport (= 4.1.12)
+    railties (4.1.13)
+      actionpack (= 4.1.13)
+      activesupport (= 4.1.13)
       rake (>= 0.8.7)
       thor (>= 0.18.1, < 2.0)
     rake (10.4.2)
-    redcarpet (3.3.2)
+    redcarpet (3.3.3)
     ref (2.0.0)
     rest-client (1.8.0)
       http-cookie (>= 1.0.2, < 2.0)
@@ -271,8 +269,8 @@ GEM
     rr (1.1.2)
     ruby-progressbar (1.7.0)
     rubyzip (1.1.7)
-    rufus-scheduler (3.1.4)
-    rugged (0.23.2)
+    rufus-scheduler (3.1.6)
+    rugged (0.23.3)
     safe_yaml (1.0.4)
     sass (3.2.19)
     sass-rails (4.0.5)
@@ -306,6 +304,8 @@ GEM
       activerecord
     sugar-rails (1.4.1)
       railties (>= 3.0.0)
+    test_after_commit (0.4.1)
+      activerecord (>= 3.2)
     therubyracer (0.12.2)
       libv8 (~> 3.16.14.0)
       ref
@@ -346,6 +346,7 @@ DEPENDENCIES
   rr
   shoulda-context
   simplecov-json
+  test_after_commit
   therubyracer
   timecop
   webmock

data/README.md

@@ -1,133 +1,25 @@
-# Houston [![Code Climate](https://codeclimate.com/github/houston/houston.png)](https://codeclimate.com/github/houston/houston)
+# Houston Core [![Code Climate](https://codeclimate.com/github/houston/houston-core.png)](https://codeclimate.com/github/houston/houston-core)
 
-### Mission Control for your projects and teams.
-
-Houston interfaces with your version-control, ticket-tracking, continuous integration, and other systems to stitch together a picture of your projects and teams.
- 
-<table>
-  <tr>
-    <td align="center" vertical-align="top">
-      <a href="http://houston.github.com/houston/images/screenshots/burndown-chart.png" target="_blank" title="Ticket Workflow">
-        <img src="http://houston.github.com/houston/images/screenshots/burndown-chart.png" width="180" alt="Ticket Workflow" />
-      </a>
-    </td>
-    <td align="center" vertical-align="top">
-      <a href="http://houston.github.com/houston/images/screenshots/testing-conversation-2.png" target="_blank" title="Testing Workflow">
-        <img src="http://houston.github.com/houston/images/screenshots/testing-conversation-2.png" width="180" alt="Testing Workflow" />
-      </a>
-    </td>
-    <td align="center" vertical-align="top">
-      <a href="http://houston.github.com/houston/images/screenshots/new-release-2.png" target="_blank" title="Automatic Release Notes">
-        <img src="http://houston.github.com/houston/images/screenshots/new-release-2.png" width="180" alt="Automatic Release Notes" />
-      </a>
-    </td>
-    <td align="center" vertical-align="top">
-      <a href="http://houston.github.com/houston/images/screenshots/timeline.png" target="_blank" title="Reports">
-        <img src="http://houston.github.com/houston/images/screenshots/timeline.png" width="180" alt="Reports" />
-      </a>
-    </td>
-  </tr>
-  <tr>
-    <th>Ticket Workflow</th>
-    <th>Testing Workflow</th>
-    <th>Automatic Release Notes</th>
-    <th>Reports</th>
-  </tr>
-</table>
-
-
-
-## Getting Started
-
-#### Requirements
-
-  * Ruby 2.0+
-  * Postgres 9.2+
-
-
-#### Getting Houston Running
-
- 1. Clone Houston:
-
-    git clone git@github.com:houston/houston.git
-
- 2. Modify config/database.yml to connect to your database (See [the Rails Guide](http://guides.rubyonrails.org/configuring.html#configuring-a-database) for examples)
-
- 3. Set up your database
-
-    cd houston
-    script/bootstrap
-    bundle exec rake db:seed
-
- 4. Start Houston
-
-    bundle exec rails server
-
-
-#### Configuring Houston
-
-You can control Houston's feature, permissions, events, colors, and more in `config/config.rb`.
+This is the Houston application. Deploy it by forking [houston/houston](https://github.com/houston/houston) and configuring for your team!
 
+### What is Houston?
 
-#### Writing your own modules
-
-To create a new module for Houston, run:
-
-    gem install houston-cli
-    houston_new_module warpcore
-
-This will generate a gem for a Rails Engine named `houston-warpcore`.
-
-Then add something like the following to `config/config.rb`:
-
-    use :warpcore, github: "mscott/warpcore", branch: "master"
-
-(You can use the same options after `use :warpcore` that you'd use after `gem "houston-warpcore"` in a `Gemfile`.)
-
-
-
-## Vision
-
-Houston does not intend to become a ticket-tracking system or continuous integration server. It's goal is to glue those systems together and synthesize information from them. Houston has three parts:
-
- 1. A model of your projects and teams
- 2. Adapters for various version-control, ticket-tracking, and other systems
- 3. Custom views that synthesize that information
-
-You should pick a ticket-tracking system or a continuous integration server based on your teams needs&mdash;or your company's needs&mdash;but then be able to extend it as you wish. Houston is a framework for just that!
-
-
-
-## Features
-
-The following are examples of how Houston can be used:
-
- - **Kanban** allows you define stages for tickets and then depicts how all of your tickets, across projects, fall into those stages.
- - **Testing Report** collects tickets awaiting QA from multiple projects, and shows the progress and evolution of testing
- - **Release Notes** are generated automatically from your commit messages, and can be configured to automatically close tickets when released
- - **Scheduler** shows you tickets that need effort and value estimates and generates to-do lists from them based on your queuing discipline
- - **CI** can be configured to trigger CI jobs and publish the results upon version-control events
-
+###### Mission Control for your projects and team
 
+Houston interfaces with your version-control, ticket-tracking, continuous integration, and other systems to stitch together a picture of your projects and teams.
 
-## Architecture
+It makes it easy to set up **triggers** and **notifications** like:
 
-### Models
+ - Resolving an exception report when a commit that mentions it is deployed
+ - Slacking team members when a pull request is labeled or unlabeled
+ - Notifying a committer when their commit breaks a test
 
-Four models are central to Houston:
+And it provides a foundation for custom views like **dashboards** and **reports**.
 
- - **Project** which ties together a slug, color, and different adapters with a project
- - **User** which has a role and is tied to different permissions and notifications
- - **Ticket** a generic concept of a ticket
- - **Commit** a generic concept of a commit
+Houston is also extensible through **modules**.
 
-### Adapters
 
-Houston uses adapters to support multiple systems. There are three right now:
- - **TicketTracking**: `Unfuddle` and `None` supported
- - **VersionControl**: `Git` and `None` supported
- - **CI**: `Jenkins` and `None` supported
 
-### Configuration
+## Getting Started with Houston
 
-The specific details of Houston's operation are described in config/config.rb ([example](https://github.com/houston/houston/blob/master/config/config.sample.rb)).
+Fork [houston/houston](https://github.com/houston/houston) and follow the instructions to get it set up for your team!

data/app/adapters/houston/adapters/ci_server/errors.rb

@@ -1,16 +1,16 @@
 module Houston
   module Adapters
     module CIServer
-      
+
       class Error < StandardError
       end
-      
+
       class NotConfiguredError < ::Houston::Adapters::CIServer::Error
       end
-      
+
       class NotFoundError < ::Houston::Adapters::CIServer::Error
       end
-      
+
     end
   end
 end