stove 1.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: dde2723a21fab73bfd26086db3d4d3bfc8119c9b
+  data.tar.gz: 89dd4e5c0346b7650c02fae1252d23286cac5775
+SHA512:
+  metadata.gz: 35291802106df5fc1021dadf947521cc9d0d3972a23f87e82cae09fd16337c27ceb62837d757c888dba09577c6d9a5cd3f6bff86267da09c460436cd50f69420
+  data.tar.gz: c4b3ecd3b3ea84e2f2d7f135794fbadf37355ce634e8dd85635a5d0050c27a2a655491d3c3dad97eed28112249a8a88f51b21fbf82145e504aa63be2d3e6e2c7

data/.gitignore

@@ -0,0 +1,17 @@
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp

data/.travis.yml

@@ -0,0 +1,5 @@
+rvm:
+  - 1.9.3
+  - 2.0.0
+script:
+  - bundle exec cucumber --color --format progress --strict

data/Gemfile

@@ -0,0 +1,2 @@
+source 'https://rubygems.org'
+gemspec

data/LICENSE

@@ -0,0 +1,202 @@
+                              Apache License
+                        Version 2.0, January 2004
+                     http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don't include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright 2013 Seth Vargo <sethvargo@gmail.com>
+Copyright 2013 Opscode, Inc
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/README.md

@@ -0,0 +1,117 @@
+Stove
+=====
+[![Gem Version](https://badge.fury.io/rb/stove.png)](http://badge.fury.io/rb/stove)
+[![Build Status](https://travis-ci.org/sethvargo/stove.png?branch=master)](https://travis-ci.org/sethvargo/stove)
+[![Dependency Status](https://gemnasium.com/sethvargo/stove.png)](https://gemnasium.com/sethvargo/stove)
+[![Code Climate](https://codeclimate.com/github/sethvargo/stove.png)](https://codeclimate.com/github/sethvargo/stove)
+
+A utility for releasing and managing Chef Cookbooks. It will:
+
+- Edit the `metadata.rb` and insert the proper version
+- Create a CHANGELOG from JIRA tickets
+- Commit and push these changes to git
+- Create a git tag and push those changes to git
+- Upload the cookbook to the Opscode community site
+- Resolve (close) the JIRA tickets
+
+
+Why?
+----
+Existing tools to package cookbooks (such as [Knife Community](https://github.com/miketheman/knife-community) and `knife cookbook site share`) require a dependency on Chef. Because of thier dependency on Chef, they enforce the use of a "cookbook repo". Especially with the evolution of [Berkshelf](https://github.com/RiotGames/berkshelf), cookbooks are individualized artifacts and are often contained in their own repositories. [stove](https://github.com/sethvargo/stove) is **cookbook-centric, rather than Chef-centric**. Since all commands are run from inside the cookbook, it's safe to include stove in your cookbooks `Gemfile`.
+
+
+Installation
+------------
+It is highly recommended that you include `stove` in your cookbook's Gemfile:
+
+```ruby
+gem 'stove'
+```
+
+Alternatively, you may install it as a gem:
+
+    $ gem install stove
+
+Create a special JIRA credentials file at '~/.stove' that has the following JSON:
+
+```javascript
+{
+  "jira_username": "JIRA_USERNAME",
+  "jira_password": "JIRA_PASSWORD",
+  "opscode_username": "OPSCODE_USERNAME",
+  "opscode_pem_file": "OPSCODE_PEM_FILE"
+}
+```
+
+For example:
+
+```javascript
+{
+  "jira_username": "sethvargo",
+  "jira_password": "bAc0ñ",
+  "opscode_username": "sethvargo",
+  "opscode_pem_file": "~/.chef/sethvargo.pem"
+}
+```
+
+
+Usage
+-----
+The gem is packaged as a binary. It should be run from _inside the cookbook to release_:
+
+    (~/cookbooks/bacon) $ bake 1.2.3
+
+```text
+Usage: bake x.y.z
+    -l, --log-level [LEVEL]          Ruby log level
+    -c, --category [CATEGORY]        The category for the cookbook (optional for existing cookbooks)
+    -p, --path [PATH]                The path to the cookbook to release (default: PWD)
+        --[no-]git                   Automatically tag and push to git (default: true)
+    -r, --remote                     The name of the git remote to push to
+    -b, --branch                     The name of the git branch to push to
+        --[no-]jira                  Automatically populate the CHANGELOG from JIRA tickets and close them (default: false)
+        --[no-]upload                Upload the cookbook to the Opscode Community Site (default: true)
+        --[no-]changelog             Automatically generate a CHANGELOG (default: true)
+    -h, --help                       Show this message
+    -v, --version                    Show version
+```
+
+
+Contributing
+------------
+1. Fork it
+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
+
+TODO:
+- Secure the authentication file
+
+
+See Also
+--------
+- [Knife Community](https://github.com/miketheman/knife-community)
+- [Emeril](https://github.com/fnichol/emeril)
+
+
+License & Authors
+-----------------
+- Author: Seth Vargo (sethvargo@gmail.com)
+
+```text
+Copyright 2013 Seth Vargo <sethvargo@gmail.com>
+Copyright 2013 Opscode, Inc
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+```

data/Rakefile

@@ -0,0 +1 @@
+require "bundler/gem_tasks"

data/bin/bake

@@ -0,0 +1,5 @@
+#!/usr/bin/env ruby
+
+$:.unshift(File.expand_path(File.join(File.dirname(__FILE__), '..', 'lib')))
+require 'stove/cli'
+Stove::Cli.new(ARGV.dup).execute!

data/features/changelog.feature

@@ -0,0 +1,26 @@
+Feature: Changelog
+  As a stove user
+  In order to have a human-readable changeset
+  I want to automatically generate a Changelog
+
+  Background:
+    * the CLI options are all off
+    * I have a cookbook named "bacon"
+
+  Scenario: --no-changelog
+    * I successfully run `bake 1.0.0 --no-changelog`
+
+  Scenario: --changelog
+    * the environment variable EDITOR is "cat"
+    * I successfully run `bake 1.0.0 --changelog`
+    * the file "CHANGELOG.md" should contain:
+      """
+      v1.0.0
+      ------
+      _Enter CHANGELOG for bacon (1.0.0) here_
+      """
+
+  Scenario: bad $EDITOR
+    * the environment variable EDITOR is "not-a-real-shell-command"
+    * I run `bake 1.0.0 --changelog`
+    * the exit status will be "Error"

data/features/cli.feature

@@ -0,0 +1,15 @@
+Feature: Cli
+  As a stove user
+  In order to use Stove
+  I want to have a Cli that is useful
+
+  Background:
+    * I have a cookbook named "bacon"
+
+  Scenario: no version
+    * I run `bake`
+    * the exit status will be "InvalidVersionError"
+
+  Scenario: invalid version
+    * I run `bake 1.2`
+    * the exit status will be "InvalidVersionError"

data/features/git.feature

@@ -0,0 +1,32 @@
+Feature: Git
+  As a stove user
+  In order to have a useful git tree
+  I want to automatically tag and push to git
+
+  Background:
+    * the CLI options are all off
+
+  Scenario: --no-git
+    * I have a cookbook named "bacon" with git support
+    * I successfully run `bake 1.0.0 --no-git`
+    * the git remote will not have the commit "Version bump to v1.0.0"
+    * the git remote will not have the tag "v1.0.0"
+
+  Scenario: --git
+    * I have a cookbook named "bacon" with git support
+    * I successfully run `bake 1.0.0 --git`
+    * the git remote will have the commit "Version bump to v1.0.0"
+    * the git remote will have the tag "v1.0.0"
+
+  Scenario: A dirty git repo
+    * I have a cookbook named "bacon" with git support
+    * I append to "CHANGELOG.md" with "# A change"
+    * I run `bake 1.0.0 --git`
+    * the git remote will not have the commit "Version bump to v1.0.0"
+    * the git remote will not have the tag "v1.0.0"
+    * the exit status will be "GitError::DirtyRepo"
+
+  Scenario: Not a git repo
+    * I have a cookbook named "bacon"
+    * I run `bake 1.0.0 --git`
+    * the exit status will be "GitError::NotARepo"