right_develop 3.1.10 → 3.1.11

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: ca1ee47286ed9116bc3e025b1596019d85b1b59c
-  data.tar.gz: 524daf75dc03226c0fa94d0c265dc494f24e7ac2
+  metadata.gz: 8a1b5ee8065e071139d0264f52b6437f2f6cfd84
+  data.tar.gz: 756634df8bf97a65ec710891ca693616ab793c2f
 SHA512:
-  metadata.gz: 2264a0ad0de1f8cef1de281cca8d9ab688c3d2d14006d5a4225decb2cf7fd346cb67226832abee3933f43b65b9a5f157b5a121159d90591223a40b2ed05463a3
-  data.tar.gz: c00c17b93fb059d26181ebc335f25fcbecee4e8c7f0d0e7e6542a179b05a47ced720c0973e7ec9d8dc56ad1bf6a0e1801128b74b2afdfadcdcc07a70069251cc
+  metadata.gz: 9ab44eaf5b40975729c7c483a932f5fb7f4ccefe6a659783a06690b5767867c77813a9325449a0b08e41643bb8480eebfdbc4ef28a1734dc103c318b48a745f0
+  data.tar.gz: d1dcf58d68ee081e707128bcfa646f8ca91a8c60519fe5f51c9c0e645287f2f0cdaad6fac3cf1c55665f8746ef26bb86b95cbaefa9aeaa05573674392349fbe9

data/CHANGELOG.md

@@ -1,6 +1,13 @@
-# 1.0
+# 3.1
 
-Initial release calved from RightSupport.
+Made CI RSpec/Cucumber integration optional; the Rake task will adapt to whichever gems are present
+in the bundle.
+
+# 3.0
+
+Reformatted CI harnesss substantially, changing class names and definitions for better modularity
+and compatibility across RSpec v1-3. Rake task interface is compatible with RightDevelop v2;
+there should be no problems upgrading from v2 unless you were relying on RightDevelop internals.
 
 # 2.0
 
@@ -10,8 +17,7 @@ local class definitions. Some developer-specific git behavior remains.
 Other than removing the Git functionality, no interface-breaking changes have occurred; there
 should be no problems upgrading from v1 unless you were relying on the Git module.
 
-# 3.0
+# 1.0
+
+Initial release calved from RightSupport.
 
-Reformatted CI harnesss substantially, changing class names and definitions for better modularity
-and compatibility across RSpec v1-3. Rake task interface is compatible with RightDevelop v2;
-there should be no problems upgrading from v2 unless you were relying on RightDevelop internals.

data/README.md

@@ -13,13 +13,12 @@ Maintained by the RightScale Engineering Team.
 
 ## Continuous Integration
 
-Jenkins groks JUnit XML test results very well, and has lots of hidden features associated with them. Tests are tests,
-so we've written an RSpec formatter that Jenkins will feel right at home with!
+RightScale uses a mixture of CI applications and testing frameworks; we value consistent behavior and output formatting between environments. To help promote consistency, we've written a CI harness.
 
 To use our CI harness, just add the following to your Rakefile (or into lib/tasks/ci.rake):
 
-  require 'right_develop'
-  RightDevelop::CI::RakeTask.new
+	require 'right_develop'
+	RightDevelop::CI::RakeTask.new
 
 ### Integrating CI with Rails
 
@@ -30,16 +29,16 @@ task, ensuring that the DB is prepared before running tests.
 RightDevelop has a similar hook; the ci:prep task is executed before running any ci:* task. If you need to perform
 app-specific CI setup, you can hook into it like this:
 
-  task 'ci:prep' => ['db:my_special_setup_task']
+	task 'ci:prep' => ['db:my_special_setup_task']
 
 Unfortunately, db:test:prepare does some things that aren't so useful in the CI environment, such as verifying
 that the development DB exists and is fully migrated. The development DB is irrelevant when running tests, and if someone
 has failed to commit changes to schema.rb then we _want_ the tests to break. Therefore, to setup a Rails app properly,
 use the following dependency:
 
-  # Make sure we run the Rails DB-setup stuff before any CI run. Avoid using db:test:prepare
-  # because it also checks for pending migrations in the dev database, which is not useful to us.
-  task 'ci:prep' => ['db:test:purge', 'db:test:load', 'db:schema:load']
+	# Make sure we run the Rails DB-setup stuff before any CI run. Avoid using db:test:prepare
+	# because it also checks for pending migrations in the dev database, which is not useful to us.
+	task 'ci:prep' => ['db:test:purge', 'db:test:load', 'db:schema:load']
 
 
 ### Customizing your CI Harness
@@ -47,15 +46,15 @@ use the following dependency:
 You can override various aspects of the CI harness' behavior by passing a block to the constructor which
 tweaks various instance variables of the resulting Rake task:
 
-  RightDevelop::CI::RakeTask.new do |task|
-    task.ci_namespace  = :my_happy_ci
-    task.rspec_name    = :important                       # run as my_happy_ci:important
-    task.rspec_desc    = "important specs with CI output" # or use cucumber_{name,desc} for Cucumber
-    task.rspec_pattern = "spec/important/**/*_spec.rb"    # only run the important specs for CI
-    task.rspec_opts    = ["-t", "important"]              # alternatively, only run tasks tagged as important
-    task.output_path   = "ci_results"                     # use ci_results as the base dir for all output files
-    task.rspec_output  = "happy_specs.xml"                # write to ci_results/rspec/happy_specs.xml
-  end
+	RightDevelop::CI::RakeTask.new do |task|
+	  task.ci_namespace  = :my_happy_ci
+	  task.rspec_name    = :important                       # run as my_happy_ci:important
+	  task.rspec_desc    = "important specs with CI output" # or use cucumber_{name,desc} for Cucumber
+	  task.rspec_pattern = "spec/important/**/*_spec.rb"    # only run the important specs for CI
+	  task.rspec_opts    = ["-t", "important"]              # alternatively, only run tasks tagged as important
+	  task.output_path   = "ci_results"                     # use ci_results as the base dir for all output files
+	  task.rspec_output  = "happy_specs.xml"                # write to ci_results/rspec/happy_specs.xml
+	end
 
 ### Keeping the CI Harness Out of Production
 
@@ -65,19 +64,19 @@ due to potential bugs in test code.
 
 To prevent RightDevelop from shipping to production, simply put it in the "development" group of your Gemfile:
 
-  group :development do
-    gem 'right_develop'
-  end
+	group :development do
+	  gem 'right_develop'
+	end
 
 And ensure that you deploy your code using Bundler's --without flag:
 
-  bundle install --deployment --without development
+	bundle install --deployment --without=development
 
 And finally, modify your Rakefile so you can tolerate the absence of the RightDevelop rake classes. For this,
 you can use RightSupport's Kernel#require_succeeds? extension to conditionally instantiate the Rake tasks:
 
-  require 'right_support'
+	require 'right_support'
 
-  if require_succeeds?('right_develop')
-    RightDevelop::CI::RakeTask.new
-  end
+	if require_succeeds?('right_develop')
+	  RightDevelop::CI::RakeTask.new
+	end

data/VERSION

@@ -1 +1 @@
-3.1.10
+3.1.11

data/right_develop.gemspec

@@ -2,16 +2,16 @@
 # DO NOT EDIT THIS FILE DIRECTLY
 # Instead, edit Jeweler::Tasks in Rakefile, and run 'rake gemspec'
 # -*- encoding: utf-8 -*-
-# stub: right_develop 3.1.10 ruby lib
+# stub: right_develop 3.1.11 ruby lib
 
 Gem::Specification.new do |s|
   s.name = "right_develop"
-  s.version = "3.1.10"
+  s.version = "3.1.11"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.require_paths = ["lib"]
   s.authors = ["Tony Spataro"]
-  s.date = "2014-12-10"
+  s.date = "2014-12-29"
   s.description = "A toolkit of development tools created by RightScale."
   s.email = "support@rightscale.com"
   s.executables = ["right_develop"]

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: right_develop
 version: !ruby/object:Gem::Version
-  version: 3.1.10
+  version: 3.1.11
 platform: ruby
 authors:
 - Tony Spataro
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-12-12 00:00:00.000000000 Z
+date: 2014-12-29 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: right_support