pivotal-bootstrap 1.0.0

checksums.yaml

@@ -0,0 +1,15 @@
+---
+!binary "U0hBMQ==":
+  metadata.gz: !binary |-
+    ZGQzOGVjN2M1NzI0ZjliODM5NzQ2N2NkNWYyYzE4ZjZhNDM2NDk1YQ==
+  data.tar.gz: !binary |-
+    ZWQzNzlmOTU3ZTU3MTc0MDUwYzgwOGEzNzE1NzExMzc2ZTUxMTRiMA==
+!binary "U0hBNTEy":
+  metadata.gz: !binary |-
+    OWU4YzM4MWQ2OGRmNDMzYWFhZmQ1ODJkNzk3YjM3NTBhMDQ0MDE5MWZjODRl
+    M2FiZjBhZWI5NzliOTM3YTVhYTgyZTM1ZjE4MTViYWNmNjY5NTU2NmIxYWE5
+    NzllN2UwNWY4OGY5MTc5MzYzNmFkOTgxNTA3MDQ0NmYwMmIyNTM=
+  data.tar.gz: !binary |-
+    YjRlZDU0MDQ2Y2NiODVhOTczNzU2NzA3NzFiMTI4NmUxMGQ5ZDkyYjllNGY0
+    MjhhNTk5ZDNjODM5M2ExNjcyZmFiNThkYTBjYTRkNWE2ZjM2OGI5YTA4MWIx
+    YzEyYWUyNzc1ZGEzYjc5MWU3YWQwNjNjYzFmZWVlZjc4MTRmNjE=

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/.ruby-version

@@ -0,0 +1 @@
+ruby-1.9.3-p194@pivotal-bootstrap

data/Gemfile

@@ -0,0 +1,4 @@
+source "http://rubygems.org"
+
+gem 'httparty'
+gem 'trollop'

data/Gemfile.lock

@@ -0,0 +1,16 @@
+GEM
+  remote: http://rubygems.org/
+  specs:
+    httparty (0.11.0)
+      multi_json (~> 1.0)
+      multi_xml (>= 0.5.2)
+    multi_json (1.7.2)
+    multi_xml (0.5.3)
+    trollop (2.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  httparty
+  trollop

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2013 Element 84, LLC
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,110 @@
+# pivotal-bootstrap
+
+This gem provides a command-line application, "pivotal-bootstrap", which
+imports stories from one or more YAML files into Pivotal Tracker.
+
+The command makes it easy to bootstrap new projects with a common set of
+pre-canned stories or to quickly capture stories in a text file for later
+import.
+
+YAML files contain grouped stories, allowing you to choose which groups to import.
+This is useful when bootstrapping a new Pivotal project with common stories,
+since every group of stories may not be applicable to every type of project
+(see the example stories.yml for an instance of this).
+
+## Installation
+
+Run
+
+    $ gem install pivotal-bootstrap
+
+Retrieve a Pivotal Tracker API token from https://www.pivotaltracker.com/profile
+
+You may specify this token on the command line or place it in ~/.pivotal_tracker
+for easier reuse.  ~/.pivotal_tracker should look like this:
+
+    token: your_token_here
+
+## Usage
+
+To retrieve a list of available arguments, run
+
+    $ pivotal-bootstrap --help
+
+By default, the application reads stories from stories.yml in the current directory.
+If you have your stories in stories.yml and your token in ~/.pivotal_tracker as
+described above, simply run
+
+    $ pivotal-bootstrap --project=$PROJECT_ID
+
+Where $PROJECT_ID is the ID of the pivotal project contained in the project's URL.
+
+The application will ask you which groups of stories to import.  You may also specify
+groups on the command line:
+
+    $ pivotal-bootstrap --project=$PROJECT_ID --groups=group1 group2
+
+or you can import all the stories:
+
+    $ pivotal-bootstrap --project=$PROJECT_ID --all
+
+Another example providing an API token and a project ID, importing all stories from
+multiple files:
+
+   $ pivotal-bootstrap --token=$PIVOTAL_TOKEN --project=$PROJECT_ID --all some_stories.yml other_stories.yml
+
+
+## Sample YAML stories file:
+
+    # Sample stories to import into Pivotal Tracker when first creating a project
+
+    # The top level specifies a group.  The CLI allows you to specify which groups
+    # to import or interactively select groups using these keys.  By default, this
+    # string is used as a label for each item in the group.
+    project:
+
+      # Within each group, you may include a list of chores, features, releases,
+      # and/or bugs to import (all optional).
+      chores:
+        # Each story type contains a list of stories.  If these are strings, they
+        # represent the story name.
+        - Set up git project
+        - Set up customer Pivotal accounts
+
+        # You may also specify more fields for the story.  The field names match
+        # those provided by the Pivotal API
+        - name: Set up tests
+          labels: project, tests       # Multiple labels are separated by commas
+          description: >-              # Use YAML syntax for multi-line strings
+            Set up automated testing within the project and a TeamCity build to run
+            the tests.
+      features:
+        - Design user interface
+      releases:
+        - Release v1.0
+
+    ios-project:
+      labels: project
+      chores:
+        - Provision customer devices
+        - Submit app for review
+      features:
+        - Add analytics to the project
+
+    web-project:
+      labels: project
+      chores:
+        - Set up staging server
+        - Set up production server
+
+    accounts:
+      features:
+        - Create account
+        - Log in
+        - Log out
+        - Change password
+        - Recover password
+        - Show user account information
+        - Update user account information
+
+

data/Rakefile

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

data/bin/pivotal-bootstrap

@@ -0,0 +1,121 @@
+#!/usr/bin/env ruby
+
+# Allow the binary to be run during development
+if File.exists?(File.join(File.expand_path('../..', __FILE__), '.git'))
+  pivotal_bootstrap_path = File.expand_path('../../lib', __FILE__)
+  $:.unshift(pivotal_bootstrap_path)
+end
+
+require 'rubygems'
+require 'httparty'
+require 'trollop'
+require 'yaml'
+require 'pivotal-bootstrap/version'
+
+def parse_story_file(file, opts)
+  groups = YAML.load_file(file)
+
+  result = []
+  groups.each do |name, attrs|
+    if opts[:interactive]
+      print("Include group \"#{name}\"? [y/N] ")
+      next unless STDIN.gets.chomp.downcase == 'y'
+    else
+      next unless opts[:all] || opts[:groups].include?(name)
+    end
+
+    label = attrs['labels'] || name
+
+    # Iterating the hash this way preserves the order of the YML file
+    attrs.each do |name, value|
+      if ['chores', 'features', 'bugs', 'releases'].include? name
+
+        story_type = name.chop
+        stories = value
+
+        defaults = {
+          'labels' => label,
+          'story_type' => story_type
+        }
+
+        result += stories.map do |story|
+          story = {'name' => story} if story.is_a? String
+          defaults.merge(story)
+        end
+      end
+    end
+  end
+  result
+end
+
+def parse_stories(opts)
+  # Load all stories in all provided files in reverse order so they appear
+  # in the correct order in Pivotal
+  opts[:files].map {|f| parse_story_file(f, opts)}.flatten(1).reverse
+end
+
+def bootstrap_stories(opts)
+  project_stories_url = "https://www.pivotaltracker.com/services/v3/projects/#{opts[:project]}/stories"
+  http_options = {headers: {'X-TrackerToken' => opts[:token]}}
+
+  $stdout.sync = true
+
+  parse_stories(opts).each do |story|
+    print "Loading \"[#{story['labels']}] #{story['name']}\"........"
+    response = HTTParty.post(project_stories_url, http_options.merge(body: {story: story}))
+    if response.code >= 400
+      puts "Fail!"
+      puts "An error occurred while loading stories:"
+      puts response.parsed_response["response"]["__content__"]
+      puts "Exiting"
+      exit false
+    end
+    puts "Done!"
+  end
+end
+
+
+def parse_options
+  opts = Trollop::options do
+    banner <<-EOS
+pivotal-bootstrap (v#{Pivotal::Bootstrap::VERSION})
+
+Loads stories into pivotal
+
+Usage:
+       pivotal-bootstrap [options] <filenames>*
+
+
+where <filenames> are a list of YAML files containing stories to load.  See stories.yml for details on the YAML format.
+
+Available options:
+EOS
+
+    opt :all, "Import all groups in the given files without prompting"
+    opt :groups, "A space-separated list of groups to import", type: :strings
+    opt :token, "Your Pivotal API token.  You may also set this in ~/.pivotal_tracker with the text \"token: <your token>\"", type: :string
+    opt :project, "Pivotal project id from the project URL", type: :string, required: true
+  end
+
+  opts[:files] = ARGV
+  opts[:files] << 'stories.yml' if opts[:files].size == 0 && File.exist?('stories.yml')
+
+  opts[:groups] ||= []
+  opts[:interactive] ||= !opts[:all] && opts[:groups].size == 0
+
+  unless opts[:token]
+    token_file_path = "#{Dir.home}/.pivotal_tracker"
+    if File.exist?(token_file_path)
+      opts[:token] = YAML.load_file(token_file_path)['token']
+    end
+
+    Trollop::die "You must specify a token on the command line or ~/.pivotal_tracker" unless opts[:token]
+  end
+
+  Trollop::die "Please specify at least one filename containing stories to import" unless ARGV.length > 0
+
+  opts
+end
+
+
+bootstrap_stories(parse_options)

data/lib/pivotal-bootstrap/version.rb

@@ -0,0 +1,5 @@
+module Pivotal
+  module Bootstrap
+    VERSION = "1.0.0"
+  end
+end

data/lib/pivotal-bootstrap.rb

@@ -0,0 +1,7 @@
+require "pivotal-bootstrap/version"
+
+module Pivotal
+  module Bootstrap
+    # Your code goes here...
+  end
+end

data/pivotal-bootstrap.gemspec

@@ -0,0 +1,33 @@
+# -*- encoding: utf-8 -*-
+lib = File.expand_path('../lib', __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'pivotal-bootstrap/version'
+
+Gem::Specification.new do |gem|
+  gem.name          = "pivotal-bootstrap"
+  gem.version       = Pivotal::Bootstrap::VERSION
+  gem.authors       = ["Patrick Quinn"]
+  gem.email         = ["patrick@element84.com"]
+  gem.description   = %q{Imports stories in a YAML file into Pivotal Tracker}
+  gem.summary       = <<-EOS
+This gem provides a command-line application, "pivotal-bootstrap", which
+imports stories from one or more YAML files into Pivotal Tracker.
+
+The command makes it easy to bootstrap new projects with a common set of
+pre-canned stories or to quickly capture stories in a text file for later
+import.
+
+YAML files contain grouped stories, allowing you to choose which groups to import.
+This is useful when bootstrapping a new Pivotal project with common stories,
+since every group of stories may not be applicable to every type of project
+(see the example stories.yml for an instance of this).
+EOS
+
+  gem.homepage      = ""
+
+  gem.license = 'MIT'
+  gem.files         = `git ls-files`.split($/)
+  gem.executables   = gem.files.grep(%r{^bin/}).map{ |f| File.basename(f) }
+  gem.test_files    = gem.files.grep(%r{^(test|spec|features)/})
+  gem.require_paths = ["lib"]
+end

data/stories.yml

@@ -0,0 +1,51 @@
+# Sample stories to import into Pivotal Tracker when first creating a project
+
+# The top level specifies a group.  The CLI allows you to specify which groups
+# to import or interactively select groups using these keys.  By default, this
+# string is used as a label for each item in the group.
+project:
+
+  # Within each group, you may include a list of chores, features, releases,
+  # and/or bugs to import (all optional).
+  chores:
+    # Each story type contains a list of stories.  If these are strings, they
+    # represent the story name.
+    - Set up git project
+    - Set up customer Pivotal accounts
+
+    # You may also specify more fields for the story.  The field names match
+    # those provided by the Pivotal API
+    - name: Set up tests
+      labels: project, tests       # Multiple labels are separated by commas
+      description: >-              # Use YAML syntax for multi-line strings
+        Set up automated testing within the project and a TeamCity build to run
+        the tests.
+  features:
+    - Design user interface
+  releases:
+    - Release v1.0
+
+ios-project:
+  labels: project
+  chores:
+    - Provision customer devices
+    - Submit app for review
+  features:
+    - Add analytics to the project
+
+web-project:
+  labels: project
+  chores:
+    - Set up staging server
+    - Set up production server
+
+accounts:
+  features:
+    - Create account
+    - Log in
+    - Log out
+    - Change password
+    - Recover password
+    - Show user account information
+    - Update user account information
+

metadata

@@ -0,0 +1,64 @@
+--- !ruby/object:Gem::Specification
+name: pivotal-bootstrap
+version: !ruby/object:Gem::Version
+  version: 1.0.0
+platform: ruby
+authors:
+- Patrick Quinn
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2013-05-03 00:00:00.000000000 Z
+dependencies: []
+description: Imports stories in a YAML file into Pivotal Tracker
+email:
+- patrick@element84.com
+executables:
+- pivotal-bootstrap
+extensions: []
+extra_rdoc_files: []
+files:
+- .gitignore
+- .ruby-version
+- Gemfile
+- Gemfile.lock
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/pivotal-bootstrap
+- lib/pivotal-bootstrap.rb
+- lib/pivotal-bootstrap/version.rb
+- pivotal-bootstrap.gemspec
+- stories.yml
+homepage: ''
+licenses:
+- MIT
+metadata: {}
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 2.0.3
+signing_key: 
+specification_version: 4
+summary: This gem provides a command-line application, "pivotal-bootstrap", which
+  imports stories from one or more YAML files into Pivotal Tracker.  The command makes
+  it easy to bootstrap new projects with a common set of pre-canned stories or to
+  quickly capture stories in a text file for later import.  YAML files contain grouped
+  stories, allowing you to choose which groups to import. This is useful when bootstrapping
+  a new Pivotal project with common stories, since every group of stories may not
+  be applicable to every type of project (see the example stories.yml for an instance
+  of this).
+test_files: []