baleen 0.1.1 → 0.1.2

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: baleen
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.2
 platform: ruby
 authors:
 - Kim, Hirokuni
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-10-19 00:00:00.000000000 Z
+date: 2013-11-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -80,6 +80,20 @@ dependencies:
     - - '>='
       - !ruby/object:Gem::Version
         version: '0'
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: celluloid
   requirement: !ruby/object:Gem::Requirement
@@ -150,6 +164,20 @@ dependencies:
     - - '>='
       - !ruby/object:Gem::Version
         version: '0'
+- !ruby/object:Gem::Dependency
+  name: sinatra
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
 description: Ballen allows you to run standard ruby tests in parallel and isolated
   environment
 email:
@@ -161,97 +189,50 @@ extensions: []
 extra_rdoc_files: []
 files:
 - .gitignore
+- .gitmodules
+- Dockerfile
 - Gemfile
 - LICENSE.txt
 - README.md
 - Rakefile
 - baleen.gemspec
+- baleen.yml.sample
 - bin/baleen
 - bin/baleen-server
 - lib/baleen.rb
+- lib/baleen/builder.rb
+- lib/baleen/ci_server.rb
 - lib/baleen/client.rb
-- lib/baleen/container.rb
+- lib/baleen/configuration.rb
+- lib/baleen/connection.rb
+- lib/baleen/default.rb
 - lib/baleen/error.rb
 - lib/baleen/job.rb
 - lib/baleen/message/base.rb
+- lib/baleen/message/exception.rb
 - lib/baleen/message/message.rb
-- lib/baleen/message/request.rb
-- lib/baleen/message/response.rb
+- lib/baleen/message/to_client.rb
+- lib/baleen/project.rb
 - lib/baleen/result_display.rb
 - lib/baleen/runner.rb
+- lib/baleen/serializable.rb
 - lib/baleen/server.rb
 - lib/baleen/task.rb
-- lib/baleen/utils/colored_puts.rb
+- lib/baleen/task/base.rb
+- lib/baleen/task/cucumber.rb
+- lib/baleen/task/generic.rb
+- lib/baleen/task/image_update.rb
+- lib/baleen/task/run_project.rb
+- lib/baleen/task/task.rb
+- lib/baleen/utils/highlighter.rb
+- lib/baleen/utils/logger.rb
+- lib/baleen/validator.rb
 - lib/baleen/version.rb
-- poc/.gitignore
-- poc/Gemfile
-- poc/README.rdoc
-- poc/Rakefile
-- poc/app/assets/images/rails.png
-- poc/app/assets/javascripts/application.js
-- poc/app/assets/stylesheets/application.css
-- poc/app/controllers/application_controller.rb
-- poc/app/helpers/application_helper.rb
-- poc/app/mailers/.gitkeep
-- poc/app/models/.gitkeep
-- poc/app/models/ar_profile.rb
-- poc/app/views/layouts/application.html.erb
-- poc/config.ru
-- poc/config/application.rb
-- poc/config/boot.rb
-- poc/config/cucumber.yml
-- poc/config/database.yml
-- poc/config/environment.rb
-- poc/config/environments/development.rb
-- poc/config/environments/production.rb
-- poc/config/environments/test.rb
-- poc/config/initializers/backtrace_silencers.rb
-- poc/config/initializers/inflections.rb
-- poc/config/initializers/mime_types.rb
-- poc/config/initializers/secret_token.rb
-- poc/config/initializers/session_store.rb
-- poc/config/initializers/wrap_parameters.rb
-- poc/config/locales/en.yml
-- poc/config/routes.rb
-- poc/db/.gitkeep
-- poc/db/migrate/20130914144710_create_ar_profiles.rb
-- poc/db/schema.rb
-- poc/db/seeds.rb
-- poc/features/step_definitions/fake_test_steps.rb
-- poc/features/support/env.rb
-- poc/features/support/ruby_prof_cucumber.rb
-- poc/features/t1.feature
-- poc/features/t10.feature
-- poc/features/t2.feature
-- poc/features/t3.feature
-- poc/features/t4.feature
-- poc/features/t5.feature
-- poc/features/t6.feature
-- poc/features/t7.feature
-- poc/features/t8.feature
-- poc/features/t9.feature
-- poc/lib/assets/.gitkeep
-- poc/lib/tasks/.gitkeep
-- poc/lib/tasks/cucumber.rake
-- poc/public/404.html
-- poc/public/422.html
-- poc/public/500.html
-- poc/public/favicon.ico
-- poc/public/index.html
-- poc/public/robots.txt
-- poc/script/cucumber
-- poc/script/rails
-- poc/test/fixtures/.gitkeep
-- poc/test/fixtures/ar_profiles.yml
-- poc/test/functional/.gitkeep
-- poc/test/integration/.gitkeep
-- poc/test/performance/browsing_test.rb
-- poc/test/test_helper.rb
-- poc/test/unit/.gitkeep
-- poc/test/unit/ar_profile_test.rb
-- poc/vendor/assets/javascripts/.gitkeep
-- poc/vendor/assets/stylesheets/.gitkeep
-- poc/vendor/plugins/.gitkeep
+- spec/lib/baleen/spec_result_display.rb
+- spec/lib/baleen/spec_serializable.rb
+- spec/lib/baleen/spec_task.rb
+- spec/lib/baleen/spec_validator.rb
+- spec/spec_helper.rb
 homepage: ''
 licenses:
 - MIT
@@ -276,4 +257,9 @@ rubygems_version: 2.0.3
 signing_key: 
 specification_version: 4
 summary: Container-based parallel test runner powered by Docker
-test_files: []
+test_files:
+- spec/lib/baleen/spec_result_display.rb
+- spec/lib/baleen/spec_serializable.rb
+- spec/lib/baleen/spec_task.rb
+- spec/lib/baleen/spec_validator.rb
+- spec/spec_helper.rb

data/lib/baleen/container.rb

@@ -1,32 +0,0 @@
-module Baleen
-  module Container
-
-    class DockerClient
-      Result = Struct.new("Result", :status_code, :container_id, :log)
-
-      def create_container(params)
-        @container = Docker::Container.create('Cmd' => [params.shell, params.opt, params.commands], 'Image' => params.image)
-      end
-
-      def start_container
-        info "Start container #{@container.id}"
-        @container.start
-        @container.wait
-        info "Finish container #{@container.id}"
-      end
-
-      def result
-        rst = @container.json
-        log = @container.attach(:stream => false, :stdout => true, :stderr => true, :logs => true)
-
-        Result.new(
-          rst["State"]["ExitCode"],
-          rst["ID"],
-          log
-        )
-      end
-
-    end
-
-  end
-end

data/lib/baleen/message/request.rb

@@ -1,29 +0,0 @@
-require "json"
-require "baleen/message/base"
-
-module Baleen
-  module Message
-    module Request
-
-      class ClientDisconnect < Base
-        def initialize(opt = {}); super() end
-      end
-
-      class Cucumber < Base
-        def initialize(image: nil, work_dir: "./", files: "features", shell: "/bin/bash", opt: "-c", exe: "bundle exec cucumber", before_command: nil, command: nil, concurrency: 2)
-          super()
-          @params[:image]          = image
-          @params[:shell]          = shell
-          @params[:opt]            = opt
-          @params[:work_dir]       = work_dir
-          @params[:files]          = files
-          @params[:exe]            = exe
-          @params[:before_command] = before_command
-          @params[:command]        = command
-          @params[:concurrency]    = concurrency
-        end
-      end
-
-    end
-  end
-end

data/lib/baleen/message/response.rb

@@ -1,34 +0,0 @@
-require 'json'
-
-module Baleen
-  module Message
-    module Response
-
-      class RunnerFinish < Base
-
-        def initialize(opt = {})
-          super()
-          @params[:status_code]   = opt[:status_code]
-          @params[:log ]          = opt[:log]
-          @params[:container_id ] = opt[:container_id]
-          @params[:file]          = opt[:file]
-        end
-      end
-
-      class JobComplete < Base
-        include Baleen::Message
-
-        def initialize(opt = {})
-          super()
-          @params[:status]  = opt[:status]
-          @params[:results] = opt[:results]
-        end
-
-        def result
-          JSON.parse(@params[:results]).map {|r| symbolize_keys(r) }
-        end
-      end
-
-    end
-  end
-end

data/poc/.gitignore

@@ -1,15 +0,0 @@
-# See http://help.github.com/ignore-files/ for more about ignoring files.
-#
-# If you find yourself ignoring temporary files generated by your text editor
-# or operating system, you probably want to add a global ignore instead:
-#   git config --global core.excludesfile ~/.gitignore_global
-
-# Ignore bundler config
-/.bundle
-
-# Ignore the default SQLite database.
-/db/*.sqlite3
-
-# Ignore all logfiles and tempfiles.
-/log/*.log
-/tmp

data/poc/Gemfile

@@ -1,49 +0,0 @@
-source 'https://rubygems.org'
-
-gem 'rails', '3.2.12'
-
-# Bundle edge Rails instead:
-# gem 'rails', :git => 'git://github.com/rails/rails.git'
-
-gem 'sqlite3'
-
-
-# Gems used only for assets and not required
-# in production environments by default.
-group :assets do
-  gem 'sass-rails',   '~> 3.2.3'
-  gem 'coffee-rails', '~> 3.2.1'
-
-  # See https://github.com/sstephenson/execjs#readme for more supported runtimes
-  # gem 'therubyracer', :platforms => :ruby
-
-  gem 'uglifier', '>= 1.0.3'
-end
-
-gem 'jquery-rails'
-
-# To use ActiveModel has_secure_password
-# gem 'bcrypt-ruby', '~> 3.0.0'
-
-# To use Jbuilder templates for JSON
-# gem 'jbuilder'
-
-# Use unicorn as the app server
-# gem 'unicorn'
-
-# Deploy with Capistrano
-# gem 'capistrano'
-
-# To use debugger
-# gem 'debugger'
-
-group :test do
-  gem 'cucumber-rails', :require => false
-  # database_cleaner is not required, but highly recommended
-  gem 'database_cleaner'
-  gem 'ruby-prof'
-end
-
-gem 'therubyracer'
-
-

data/poc/README.rdoc

@@ -1,261 +0,0 @@
-== Welcome to Rails
-
-Rails is a web-application framework that includes everything needed to create
-database-backed web applications according to the Model-View-Control pattern.
-
-This pattern splits the view (also called the presentation) into "dumb"
-templates that are primarily responsible for inserting pre-built data in between
-HTML tags. The model contains the "smart" domain objects (such as Account,
-Product, Person, Post) that holds all the business logic and knows how to
-persist themselves to a database. The controller handles the incoming requests
-(such as Save New Account, Update Product, Show Post) by manipulating the model
-and directing data to the view.
-
-In Rails, the model is handled by what's called an object-relational mapping
-layer entitled Active Record. This layer allows you to present the data from
-database rows as objects and embellish these data objects with business logic
-methods. You can read more about Active Record in
-link:files/vendor/rails/activerecord/README.html.
-
-The controller and view are handled by the Action Pack, which handles both
-layers by its two parts: Action View and Action Controller. These two layers
-are bundled in a single package due to their heavy interdependence. This is
-unlike the relationship between the Active Record and Action Pack that is much
-more separate. Each of these packages can be used independently outside of
-Rails. You can read more about Action Pack in
-link:files/vendor/rails/actionpack/README.html.
-
-
-== Getting Started
-
-1. At the command prompt, create a new Rails application:
-       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
-
-2. Change directory to <tt>myapp</tt> and start the web server:
-       <tt>cd myapp; rails server</tt> (run with --help for options)
-
-3. Go to http://localhost:3000/ and you'll see:
-       "Welcome aboard: You're riding Ruby on Rails!"
-
-4. Follow the guidelines to start developing your application. You can find
-the following resources handy:
-
-* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
-* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
-
-
-== Debugging Rails
-
-Sometimes your application goes wrong. Fortunately there are a lot of tools that
-will help you debug it and get it back on the rails.
-
-First area to check is the application log files. Have "tail -f" commands
-running on the server.log and development.log. Rails will automatically display
-debugging and runtime information to these files. Debugging info will also be
-shown in the browser on requests from 127.0.0.1.
-
-You can also log your own messages directly into the log file from your code
-using the Ruby logger class from inside your controllers. Example:
-
-  class WeblogController < ActionController::Base
-    def destroy
-      @weblog = Weblog.find(params[:id])
-      @weblog.destroy
-      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
-    end
-  end
-
-The result will be a message in your log file along the lines of:
-
-  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
-
-More information on how to use the logger is at http://www.ruby-doc.org/core/
-
-Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
-several books available online as well:
-
-* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
-* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
-
-These two books will bring you up to speed on the Ruby language and also on
-programming in general.
-
-
-== Debugger
-
-Debugger support is available through the debugger command when you start your
-Mongrel or WEBrick server with --debugger. This means that you can break out of
-execution at any point in the code, investigate and change the model, and then,
-resume execution! You need to install ruby-debug to run the server in debugging
-mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
-
-  class WeblogController < ActionController::Base
-    def index
-      @posts = Post.all
-      debugger
-    end
-  end
-
-So the controller will accept the action, run the first line, then present you
-with a IRB prompt in the server window. Here you can do things like:
-
-  >> @posts.inspect
-  => "[#<Post:0x14a6be8
-          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
-       #<Post:0x14a6620
-          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
-  >> @posts.first.title = "hello from a debugger"
-  => "hello from a debugger"
-
-...and even better, you can examine how your runtime objects actually work:
-
-  >> f = @posts.first
-  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
-  >> f.
-  Display all 152 possibilities? (y or n)
-
-Finally, when you're ready to resume execution, you can enter "cont".
-
-
-== Console
-
-The console is a Ruby shell, which allows you to interact with your
-application's domain model. Here you'll have all parts of the application
-configured, just like it is when the application is running. You can inspect
-domain models, change values, and save to the database. Starting the script
-without arguments will launch it in the development environment.
-
-To start the console, run <tt>rails console</tt> from the application
-directory.
-
-Options:
-
-* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
-  made to the database.
-* Passing an environment name as an argument will load the corresponding
-  environment. Example: <tt>rails console production</tt>.
-
-To reload your controllers and models after launching the console run
-<tt>reload!</tt>
-
-More information about irb can be found at:
-link:http://www.rubycentral.org/pickaxe/irb.html
-
-
-== dbconsole
-
-You can go to the command line of your database directly through <tt>rails
-dbconsole</tt>. You would be connected to the database with the credentials
-defined in database.yml. Starting the script without arguments will connect you
-to the development database. Passing an argument will connect you to a different
-database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
-PostgreSQL and SQLite 3.
-
-== Description of Contents
-
-The default directory structure of a generated Ruby on Rails application:
-
-  |-- app
-  |   |-- assets
-  |       |-- images
-  |       |-- javascripts
-  |       `-- stylesheets
-  |   |-- controllers
-  |   |-- helpers
-  |   |-- mailers
-  |   |-- models
-  |   `-- views
-  |       `-- layouts
-  |-- config
-  |   |-- environments
-  |   |-- initializers
-  |   `-- locales
-  |-- db
-  |-- doc
-  |-- lib
-  |   `-- tasks
-  |-- log
-  |-- public
-  |-- script
-  |-- test
-  |   |-- fixtures
-  |   |-- functional
-  |   |-- integration
-  |   |-- performance
-  |   `-- unit
-  |-- tmp
-  |   |-- cache
-  |   |-- pids
-  |   |-- sessions
-  |   `-- sockets
-  `-- vendor
-      |-- assets
-          `-- stylesheets
-      `-- plugins
-
-app
-  Holds all the code that's specific to this particular application.
-
-app/assets
-  Contains subdirectories for images, stylesheets, and JavaScript files.
-
-app/controllers
-  Holds controllers that should be named like weblogs_controller.rb for
-  automated URL mapping. All controllers should descend from
-  ApplicationController which itself descends from ActionController::Base.
-
-app/models
-  Holds models that should be named like post.rb. Models descend from
-  ActiveRecord::Base by default.
-
-app/views
-  Holds the template files for the view that should be named like
-  weblogs/index.html.erb for the WeblogsController#index action. All views use
-  eRuby syntax by default.
-
-app/views/layouts
-  Holds the template files for layouts to be used with views. This models the
-  common header/footer method of wrapping views. In your views, define a layout
-  using the <tt>layout :default</tt> and create a file named default.html.erb.
-  Inside default.html.erb, call <% yield %> to render the view using this
-  layout.
-
-app/helpers
-  Holds view helpers that should be named like weblogs_helper.rb. These are
-  generated for you automatically when using generators for controllers.
-  Helpers can be used to wrap functionality for your views into methods.
-
-config
-  Configuration files for the Rails environment, the routing map, the database,
-  and other dependencies.
-
-db
-  Contains the database schema in schema.rb. db/migrate contains all the
-  sequence of Migrations for your schema.
-
-doc
-  This directory is where your application documentation will be stored when
-  generated using <tt>rake doc:app</tt>
-
-lib
-  Application specific libraries. Basically, any kind of custom code that
-  doesn't belong under controllers, models, or helpers. This directory is in
-  the load path.
-
-public
-  The directory available for the web server. Also contains the dispatchers and the
-  default HTML files. This should be set as the DOCUMENT_ROOT of your web
-  server.
-
-script
-  Helper scripts for automation and generation.
-
-test
-  Unit and functional tests along with fixtures. When using the rails generate
-  command, template test files will be generated for you and placed in this
-  directory.
-
-vendor
-  External libraries that the application depends on. Also includes the plugins
-  subdirectory. If the app has frozen rails, those gems also go here, under
-  vendor/rails/. This directory is in the load path.

data/poc/Rakefile

@@ -1,7 +0,0 @@
-#!/usr/bin/env rake
-# Add your own tasks in files placed in lib/tasks ending in .rake,
-# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
-
-require File.expand_path('../config/application', __FILE__)
-
-CiApp::Application.load_tasks

data/poc/app/assets/javascripts/application.js

@@ -1,15 +0,0 @@
-// This is a manifest file that'll be compiled into application.js, which will include all the files
-// listed below.
-//
-// Any JavaScript/Coffee file within this directory, lib/assets/javascripts, vendor/assets/javascripts,
-// or vendor/assets/javascripts of plugins, if any, can be referenced here using a relative path.
-//
-// It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the
-// the compiled file.
-//
-// WARNING: THE FIRST BLANK LINE MARKS THE END OF WHAT'S TO BE PROCESSED, ANY BLANK LINE SHOULD
-// GO AFTER THE REQUIRES BELOW.
-//
-//= require jquery
-//= require jquery_ujs
-//= require_tree .

data/poc/app/assets/stylesheets/application.css

@@ -1,13 +0,0 @@
-/*
- * This is a manifest file that'll be compiled into application.css, which will include all the files
- * listed below.
- *
- * Any CSS and SCSS file within this directory, lib/assets/stylesheets, vendor/assets/stylesheets,
- * or vendor/assets/stylesheets of plugins, if any, can be referenced here using a relative path.
- *
- * You're free to add application-wide styles to this file and they'll appear at the top of the
- * compiled file, but it's generally better to create a new file per style scope.
- *
- *= require_self
- *= require_tree .
- */

data/poc/app/controllers/application_controller.rb

@@ -1,3 +0,0 @@
-class ApplicationController < ActionController::Base
-  protect_from_forgery
-end

data/poc/app/helpers/application_helper.rb

@@ -1,2 +0,0 @@
-module ApplicationHelper
-end

data/poc/app/models/ar_profile.rb

@@ -1,3 +0,0 @@
-class ArProfile < ActiveRecord::Base
-  # attr_accessible :title, :body
-end