Houston interfaces with your version-control, ticket-tracking, continuous integration, and other systems to stitch together a picture of your projects and teams.

Ticket Workflow	Testing Workflow	Automatic Release Notes	Reports

• Ruby 2.0+
• Postgres

Clone Houston:

git clone [email protected]:houstonmc/houston.git
cd houston
script/bootstrap
bundle exec rake db:seed
bundle exec rails server

You can control Houston's feature, permissions, events, colors, and more in config/config.rb.

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.)

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—or your company's needs—but then be able to extend it as you wish. Houston is a framework for just that!

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

Four models are central to Houston:

• 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 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

The specific details of Houston's operation are described in config/config.rb (example).