boxci 0.0.37 → 0.0.38

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 5041f190911bcff97ac407b11a23db3e1a111c55
-  data.tar.gz: 8f520eedb1cf219b07f150277f4b94285c3b4edf
+  metadata.gz: 6679b4fb3a5a5a83e343a1b4c3dfaa58bcd922e7
+  data.tar.gz: 0df282ea835ce9bf58243238aa78dfc8cecf5801
 SHA512:
-  metadata.gz: bec88ff45d7655b91f6b640f99c83caaac6cc1f913778f95d70d56c2cdab289baad78c6594282212b34a462955c447d1de5e337211343f3cfa9fd66f90348c89
-  data.tar.gz: b020392c1548ed7bcaf59f2595eae0c1167197608d3f4dad8bdd287b99ac20e5c6d672426c0963a53f4ab8eb4ce8177b453a028990b56263c75d47f3d3c0b661
+  metadata.gz: 8a20c8a2906c20cd360ef02e2a012026b3029aa2ce7294eebfbb447e63b50359b941504d5fb07413c405b612b2da77a2c99567d96ad9636153952ed61757668d
+  data.tar.gz: 160d1e96cd7d501a31f33bd1ed061b4fa50f7f0f84cfb38ad0686dc23fcd066558f2ef32ee88f1ea912733f3c0a90ebe828ae6132967ff6ab8fc3f66032f2210

data/.travis.yml

@@ -5,5 +5,8 @@ rvm:
   - "2.0.0"
   - "2.1.0"
   - "2.1.1"
+install:
+  - gem install bundler 
+  - bundle install
 # uncomment this line if your project needs to run something other than `rake`:
 # script: bundle exec rspec spec

data/CHANGELOG.md

@@ -6,6 +6,11 @@ versions as well as provide a rough history.
 
 #### Next Release
 
+#### v0.0.38
+
+- Fix issue with generating `.boxci.yml` incorrectly when no ruby version is
+  found.
+
 #### v0.0.37
 
 - Re-enable cleanup

data/DEVELOPMENT.md

@@ -0,0 +1,193 @@
+Great to have you here! Here are a few ways you can help out with
+[BoxCI](http://github.com/reachlocal/boxci).
+
+# Where should I start?
+
+You can start learning about BoxCI by reading [the
+documentation](http://boxci.io).  You can also check out discussions about
+BoxCI on the [BoxCI mailing
+list](https://groups.google.com/forum/#!forum/boxci) and in the [BoxCI IRC
+channel](irc://chat.freenode.net/%23boxci), which is #boxci on Freenode.
+
+## Your first commits
+
+If you’re interested in contributing to BoxCI, that’s awesome! We’d love your
+help.
+
+If you have any questions after reading this page, please feel free to contact
+either [@cyphactor](http://github.com/cyphactor) or
+[@BRIMIL01](http://github.com/brimil01). They are both happy to provide help
+working through your first bugfix or thinking through the problem you’re
+trying to resolve.
+
+## Tackle some small problems
+
+We track [small
+bugs](https://github.com/reachlocal/boxci/issues?state=open) so
+that anyone who wants to help can start with something that's not too
+overwhelming. If nothing on those lists looks good, though, just talk to us.
+
+
+# Development setup
+
+BoxCI specifies the version of Ruby it is currently being developed against in
+its `.ruby-version` file. This file should be compatible with either RVM or
+rbenv. BoxCI also uses Bundler to manage its dependencies when under
+development. To work on BoxCI, you'll probably want to do a couple of things.
+
+1. Install BoxCI's dependencies
+
+        bundle
+
+2. Run the test suite, to make sure things are working
+
+        bundle exec rspec
+
+3. Set up a shell alias to run BoxCI from your clone, e.g. a Bash alias:
+
+        alias dboxci='ruby -I /path/to/boxci/lib /path/to/boxci/bin/boxci'
+
+With that set up, you can test changes you've made to BoxCI by running
+`dboxci`, without interfering with the regular `boxci` command.
+
+# Bug triage
+
+Triage is the work of processing tickets that have been opened into actionable
+issues, feature requests, or bug reports. That includes verifying bugs,
+categorizing the ticket, and ensuring there's enough information to reproduce
+the bug for anyone who wants to try to fix it.
+
+We've created an [issues
+guide](https://github.com/reachlocal/boxci/blob/master/ISSUES.md) to walk
+BoxCI users through the process of troubleshooting issues and reporting
+bugs.
+
+If you'd like to help, awesome! You can [report a new
+bug](https://github.com/reachlocal/boxci/issues/new) or browse our [existing
+open tickets](https://github.com/reachlocal/boxci/issues).
+
+Not every ticket will point to a bug in BoxCI's code, but open tickets
+usually mean that there is something we could improve to help that user.
+Sometimes that means writing additional documentation, sometimes that means
+making error messages clearer, and sometimes that means explaining to a user
+that they need to install git to use git gems.
+
+When you're looking at a ticket, here are the main questions to ask:
+
+  * Can I reproduce this bug myself?
+  * Are the steps to reproduce clearly stated in the ticket?
+  * Which versions of BoxCI manifest this bug?
+  * Which operating systems (OS X, Windows, Ubuntu, CentOS, etc.) manifest
+    this bug?
+  * Which rubies (MRI, JRuby, Rubinius, etc.) and which versions (1.8.7,
+    1.9.3, etc.) have this bug?
+
+If you can't reproduce an issue, chances are good that the bug has been fixed
+(hurrah!). That's a good time to post to the ticket explaining what you did
+and how it worked.
+
+If you can reproduce an issue, you're well on your way to fixing it. :) Fixing
+issues is similar to adding new features:
+
+  1. Discuss the fix on the existing issue. Coordinating with everyone else
+     saves duplicate work and serves as a great way to get suggestions and
+     ideas if you need any.
+  2. Base your commits on the correct branch, generally master.
+  3. Commit the code and at least one test covering your changes to a named
+     branch in your fork.
+  4. Put a line in the
+     [CHANGELOG](https://github.com/reachlocal/boxci/blob/master/CHANGELOG.md)
+     summarizing your changes under the next release.
+  5. Send us a [pull
+     request](https://help.github.com/articles/using-pull-requests) from your
+     topic branch.
+
+Finally, the ticket may be a duplicate of another older ticket. If you notice
+a ticket is a duplicate, simply comment on the ticket noting the original
+ticket’s number. For example, you could say “This is a duplicate of issue #42,
+and can be closed”.
+
+
+# Adding new features
+
+If you would like to add a new feature to BoxCI, please follow these steps:
+
+  1. [Create an issue](https://github.com/reachlocal/boxci/issues/new) to
+     discuss your feature.
+  2. Base your commits on the master branch, since we follow
+     [SemVer](http://semver.org) and don't add new features to old releases.
+  3. Commit the code and at least one test covering your changes to a feature
+     branch in your fork.
+  4. Put a line in the
+     [CHANGELOG](https://github.com/reachlocal/boxci/blob/master/CHANGELOG.md)
+     summarizing your changes under the next release.
+  5. Send us a [pull
+     request](https://help.github.com/articles/using-pull-requests) from your
+     feature branch.
+
+If you don't hear back immediately, don’t get discouraged! We all have day
+jobs, but we respond to most tickets within a day or two.
+
+
+# Beta testing
+
+Early releases require heavy testing, especially across various system setups.
+We :heart: testers, and are big fans of anyone who can run `gem install
+bundler --pre` and try out upcoming releases in their development and staging
+environments.
+
+There may not always be prereleases or beta versions of BoxCI. That said,
+you are always welcome to try checking out master and building a gem yourself
+if you want to try out the latest changes.
+
+
+# Translations
+
+We don't currently have any translations, but please reach out to us if you
+would like to help get this going.
+
+
+# Documentation
+
+Code needs explanation, and sometimes those who know the code well have
+trouble explaining it to someone just getting into it. Because of that, we
+welcome documentation suggestions and patches from everyone, especially if
+they are brand new to using BoxCI.
+
+BoxCI has two main sources of documentation: the built-in help (including
+usage information) and the [BoxCI documentation site](http://boxci.io).
+
+If you have a suggestion or proposed change for
+[boxci.io](http://boxci.io), please open an issue or send a pull request
+to the [boxci-site](https://github.com/reachlocal/boxci-site) repository.
+
+
+
+# Community
+
+Community is an important part of all we do. If you’d like to be part of the
+BoxCI community, you can jump right in and start helping make BoxCI better
+for everyone who uses it.
+
+It would be tremendously helpful to have more people answering questions about
+BoxCI (and often simply about Puppet or Linux itself) in our [issue
+tracker](https://github.com/reachlocal/boxci/issues).
+
+Additional documentation and explanation is always helpful, too. If you have
+any suggestions for the BoxCI website [boxci.io](http://boxci.io), we would
+absolutely love it if you opened an issue or pull request on the
+[boxci-site](https://github.com/reachlocal/boxci-site) repository.
+
+Finally, sharing your experiences and discoveries by writing them up is a
+valuable way to help others who have similar problems or experiences in the
+future. You can write a blog post, create an example and commit it to Github,
+take screenshots, or make videos.
+
+Examples of how BoxCI is used help everyone, and we’ve discovered that
+people already use it in ways that we never imagined when we were writing it.
+If you’re still not sure what to write about, there are also several projects
+doing interesting things based on BoxCI. They could probably use publicity
+too.
+
+If you let someone on the core team know you wrote about BoxCI, we will add
+your post to the list of BoxCI resources on the Github project wiki.

data/ISSUES.md

@@ -0,0 +1,53 @@
+# BoxCI Issues
+
+So! You're having problems with BoxCI. This file is here to help. If you're
+running into an error, try reading the rest of this file for help. If you
+can't figure out how to solve your problem, there are also instructions on how
+to report a bug.
+
+## Documentation
+
+Instructions for common BoxCI uses can be found on the [BoxCI documentation
+site](http://boxci.io/).
+
+Detailed information about each BoxCI command, including help with common
+problems, can be found in the [BoxCI documentation site](http://boxci.io/).
+
+## Troubleshooting
+
+### Other problems
+
+First, figure out exactly what it is that you're trying to do. Then, go to the
+[BoxCI documentation website](http://boxci.io/) and see if we have
+instructions on how to do that.
+
+## Reporting unresolved problems
+
+Hopefully the troubleshooting steps above resolved your problem. If things
+still aren't working the way you expect them to, please let us know so that we
+can diagnose and hopefully fix the problem you're having.
+
+**The best way to report a bug is by providing a reproduction script.**
+
+A half working script with comments for the parts you were unable to automate
+is still appreciated.
+
+If you are unable to do that, please include the following information in your
+report:
+
+ - What you're trying to accomplish
+ - The command you ran
+ - What you expected to happen
+ - What actually happened
+ - The exception backtrace(s), if any
+ - What version of BoxCI you are using (run `boxci --verson`)
+ - What version of Ruby you are using (run `ruby -v`)
+
+[Create a gist](https://gist.github.com) containing all of that information,
+then visit the [BoxCI issue
+tracker](https://github.com/reachlocal/boxci/issues) and [create a
+ticket](https://github.com/reachlocal/boxci/issues/new) describing your
+problem and linking to your gist.
+
+Thanks for reporting issues and helping make BoxCI better! We really
+appreciate it.

data/README.md

@@ -1,124 +1,59 @@
-# boxci: standardizing virtual development & ci environments
-
 [![Build Status](https://travis-ci.org/reachlocal/boxci.svg?branch=master)](https://travis-ci.org/reachlocal/boxci)
 [![Version](https://img.shields.io/gem/v/boxci.svg)](https://rubygems.org/gems/boxci)
 [![Code Climate](https://img.shields.io/codeclimate/github/reachlocal/boxci.svg)](https://codeclimate.com/github/reachlocal/boxci)
 [![Code Coverage](http://img.shields.io/coveralls/reachlocal/boxci.svg)](https://coveralls.io/r/reachlocal/boxci)
 [![Dependency Status](https://gemnasium.com/reachlocal/boxci.svg)](https://gemnasium.com/reachlocal/boxci)
 
-Boxci makes creating a virtualized development & continuous integration
+# BoxCI: virtual dev & ci environments
+
+BoxCI makes creating a virtualized development & continuous integration
 environments as easy as possible.
 
-It does this by focusing on implementing standards around the use of
-[Vagrant](http://www.vagrantup.com/) for managing your development
-and continuous integration environment. This means that it helps you
-configure and setup [Vagrant](http://www.vagrantup.com/), generate a well
-structured initial puppet manifest, and handles spinning up your puppet
-managed continuous integration environment up in the cloud and running your
-automated test suites.
+It does this by implementing standards around the use of
+[Vagrant](http://www.vagrantup.com/) for managing your virtual development and
+continuous integration environment. This means that it helps you configure and
+setup [Vagrant](http://www.vagrantup.com/), generate a well structured initial
+puppet manifest, and handles spinning up your puppet managed continuous
+integration environment in the cloud and running your automated test
+suites.
 
-## Installation
+## Installation and usage
 
 Install it by running the following:
 
-    $ gem install boxci
-
-## Set up your project
-
-Setting a new or existing project up with Boxci is done with the following
-steps.
-
-1. Setup initial `boxci` configs & skeletons
-2. Update the generated configs
-3. Build your base `boxci` puppet manifest
-4. Iterate on your `boxci` puppet manifest
-5. Run your test suite using `boxci`
-
-### Setup initial boxci configs & skeletons
-
-To *boxcify* your project you need to run the `boxci init <language>` command.
-This command will create an initial `.boxci.yml` config for you in the current
-working directory. Therefore, you should run this command from the root of
-your project. It will also handle creating your user level `boxci`
-configurations in the `~/.boxci` directory. An example of this can be seen as
-follows:
-
-    $ boxci init ruby
-
-*Note:* The above will create user level configs using the default provider
-`virtualbox`. If you want to use `boxci` always with a cloud provider simply
-rerun the `init` command specifying one of the supported providers. The
-following is an example:
-
-    $ boxci init -p openstack ruby
-
-This will go through and setup the proper directory structure and create the
-config files just as before. However, when it identifies conflicts with the
-existing files it will prompt you and ask you if you want to overwrite, diff
-the files, not overwrite, etc.
-
-This means that you can rerun the command over and over again and not worry
-about it overwriting your configs unless you tell it too. This is also useful
-in the scenarios where a new version of `boxci` has come out and added config
-options because then you can rerun it and choose to diff them to see what was
-added.
-
-### Update the generated configs
+    gem install boxci
+    boxci init ruby
+    boxci build
+    boxci test
 
-Now that the initial configs and skeleton have been generated. We need to go
-through the configs and update them.
+## Documentation
 
-### Build your base Boxci
+See [boxci.io](http://boxci.io) for the full documentation.
 
-### Iterate on your Boxci
+## Troubleshooting
 
-### Run your Test Suite using Boxci
+For help with common problems, see
+[ISSUES](http://github.com/reachlocal/boxci/blob/master/ISSUES.md).
 
-To run your automated test suite in the cloud or locally in a `boxci` managed
-virtual machine simply run the following from the project's root directory.
-
-    $ boxci test
-
-To see more output on what is happening, pass the "-v" flag for verbose:
-
-    $ boxci test -v
-
-For details on other options you can set for test runs run the following
-command:
-
-    $ boxci help test
-
-## Get Help
-
-`boxci` provides a useful help system within the command line tool. You can
-see these messages by using the help command as follows:
-
-    $ boxci help
-
-The above shows you the top level `boxci help` including a break down of it's
-subcommands. You can get detailed help on each subcommand by running the
-following:
-
-    $ boxci help SUBCOMMAND
-
-For example if you wanted the detailed help on `init` you would run the
-following:
+## Contributing
 
-    $ boxci help init
+If you would like to contribute to BoxCI, please refer to the guide,
+[DEVELOPMENT](http://github.com/reachlocal/boxci/blob/master/DEVELOPMENT.md).
 
-## Config Breakdown
+Please submit bugfixes as pull requests to the master branch.
 
-### .boxci.yml
+## Core Team
 
-After initializing, you need to configure the `.boxci.yml` in the root of your
-project.
+The BoxCI core team is composed of Andrew De Ponte
+([@cyphactor](http://github.com/cyphactor)), Brian Miller
+([@BRIMIL01](http://github.com/brimil01)), and Russell Cloak
+([@russCloak](http://github.com/russCloak)).
 
-See the generated `.boxci.yml` file for help with configuration.
+## Other questions
 
-## Contributing
+To see what has changed in recent versions of BoxCI, see
+[CHANGELOG](http://github.com/reachlocal/boxci/blob/master/CHANGELOG.md).
 
-1. Fork it ( http://github.com/reachlocal/boxci/fork )
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Add some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create new Pull Request
+Feel free to chat with the BoxCI core team and others on IRC in the
+[\#boxci](irc://chat.freenode.net/%23boxci) channel on Freenode, or via e-mail
+on the [BoxCI mailing list](https://groups.google.com/forum/#!forum/boxci).

data/boxci.gemspec

@@ -7,7 +7,7 @@ Gem::Specification.new do |spec|
   spec.name          = "boxci"
   spec.version       = Boxci::VERSION
   spec.authors       = ["Andrew De Ponte", "Brian Miller", "Russell Cloak"]
-  spec.email         = ["cyphactor@gmail.com", "brimil01@gmail.com", "russcloak@gmail.cm"]
+  spec.email         = ["cyphactor@gmail.com", "brimil01@gmail.com", "russcloak@gmail.com"]
   spec.summary       = %q{Tool simplifying Vagrant based development & continuous integration environments.}
   spec.description   = %q{Boxci is focused on defining standards and building tooling around using Vagrant for development & continuous integration environments to make using them as easy as possible.}
   spec.homepage      = "http://boxci.io"
@@ -20,9 +20,9 @@ Gem::Specification.new do |spec|
 
   spec.add_runtime_dependency "thor", "~> 0.18"
   spec.add_runtime_dependency "net-ssh", "~> 2.7"
-  spec.add_runtime_dependency "net-scp", "~> 1.1"
+  spec.add_runtime_dependency "net-scp", "~> 1.2"
 
-  spec.add_development_dependency "bundler", "~> 1.5"
+  spec.add_development_dependency "bundler", "~> 1.6"
   spec.add_development_dependency "rspec", "~> 2.14"
-  spec.add_development_dependency "rake", "~> 10.1"
+  spec.add_development_dependency "rake", "~> 10.2"
 end

data/lib/boxci/templates/dot_boxci.yml.tt

@@ -3,7 +3,7 @@ language: <%= @language -%>
 rbenv:
 <% if @current_ruby_version -%>
   - "<%= @current_ruby_version -%>"
-<% else %>
+<% else -%>
   - "2.1.0"
 <% end -%>
 # uncomment this line if your project needs to run something other than `rake`:

data/lib/boxci/version.rb

@@ -1,3 +1,3 @@
 module Boxci
-  VERSION = "0.0.37"
+  VERSION = "0.0.38"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: boxci
 version: !ruby/object:Gem::Version
-  version: 0.0.37
+  version: 0.0.38
 platform: ruby
 authors:
 - Andrew De Ponte
@@ -10,7 +10,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-03-27 00:00:00.000000000 Z
+date: 2014-04-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: thor
@@ -46,28 +46,28 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.1'
+        version: '1.2'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.1'
+        version: '1.2'
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.5'
+        version: '1.6'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.5'
+        version: '1.6'
 - !ruby/object:Gem::Dependency
   name: rspec
   requirement: !ruby/object:Gem::Requirement
@@ -88,21 +88,21 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '10.1'
+        version: '10.2'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '10.1'
+        version: '10.2'
 description: Boxci is focused on defining standards and building tooling around using
   Vagrant for development & continuous integration environments to make using them
   as easy as possible.
 email:
 - cyphactor@gmail.com
 - brimil01@gmail.com
-- russcloak@gmail.cm
+- russcloak@gmail.com
 executables:
 - boxci
 extensions: []
@@ -114,7 +114,9 @@ files:
 - ".ruby-version"
 - ".travis.yml"
 - CHANGELOG.md
+- DEVELOPMENT.md
 - Gemfile
+- ISSUES.md
 - LICENSE.txt
 - README.md
 - Rakefile