factorylabs-auto_tagger 0.1.1

data/.document

@@ -0,0 +1,6 @@
+README.md
+CHANGELOG
+MIT-LICENSE
+bin/*
+lib/**/*
+recipes/**/*

data/.gitignore

@@ -0,0 +1,6 @@
+pkg/*
+rdoc/*
+*.gem
+.DS_Store
+test_files/*
+.idea/*

data/CHANGELOG

@@ -0,0 +1,30 @@
+2009-10-15
+
+- You can now define your stages as strings or symbols and auto-tagger will not fail (thanks to Chad Wooley for the bug report)
+- When deploying from a branch auto_tagger uses real_revision, not the previous tag, to create the new tag (Brian Takita)
+
+2009-04-30
+
+- Fixed bug whereby auto-tagger would use the wrong tag because it found tags that had similar names to what it uses.
+
+2009-04-20
+
+- `release_tagger:create_tag` creates a production tag if you don't set any stages
+
+2009-04-05
+
+- Added basic support for cap-ext-multistage
+- Changed "stages" variable to "autotagger_stages" so as not to conflict with the multistage "stages" variable in capistrano
+- Changed the :current_stage variable in the capistrano tasks to just :stage
+
+2009-03-31
+
+- Capistrano bases new tags off of old tags from the previous environment when tagging if there is a tag from the previous environment
+- Added the following cap tasks:
+  - print_latest_tags
+  - read_tag_from_shared
+  - write_tag_to_shared
+
+2009-03-29
+
+- Capistrano tasks :set_branch no longer sets the branch to nil.  If the CapistranoHelper returns nil, it leaves the branch alone.

data/MIT-LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2009 [Jeff Dean]
+
+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,176 @@
+# IMPORTANT NOTE
+
+This gem is still in it's infancy, and lots of things might change.  Since this creates and pushes tags to your git repository, please use with caution.
+
+# AutoTagger
+
+AutoTagger is a gem that helps you automatically create a date-stamped tag for each stage of your deployment, and deploy from the last tag from the previous environment.
+
+Let's say you have the following workflow:
+
+ * Run all test on a Continuous Integration (CI) server
+ * Deploy to a staging server
+ * Deploy to a production server
+
+You can use the `autotag` command to tag releases on your CI box, then use the capistrano tasks to auto-tag each release.
+
+## Installation
+
+    sudo gem install auto_tagger
+
+## Contribute
+
+  * [GitHub Repository](http://github.com/zilkey/auto_tagger/tree/master)
+
+## The autotag executable
+
+Installing the gem creates an executable file named autotag, which takes two arguments: the stage, and optionally the path to the git repo:
+
+    $ autotag demo  # => creates a tag like demo/200804041234 in the current directory
+    $ autotag demo . # => same as above
+    $ autotag demo /Users/me/foo # => cd's to /Users/me/foo before creating the tag
+
+Running autotag does the following:
+
+    $ git fetch origin --tags
+    $ git tag <stage>/<timestamp>
+    $ git push origin --tags
+
+## Capistrano Integration
+
+AutoTagger comes with 2 capistrano tasks: 
+
+  * `release_tagger:set_branch` tries to set the branch to the last tag from the previous environment.
+  * `release_tagger:create_tag` runs autotag for the current stage
+
+Example `config/deploy.rb` file:
+
+    require 'release_tagger'
+
+    # The :autotagger_stages variable is required
+    set :autotagger_stages, [:ci, :staging, :production]
+
+    # The :working_directory variable is optional, and defaults to Dir.pwd
+    # :working_directory can be an absolute or relative path
+    set :working_directory, "../../"
+
+    task :production do
+      # In each of your environments that need auto-branch setting, you need to set :stage
+      set :stage, :production
+    end
+
+    task :staging do
+      # If you do not set stage, it will not auto-set your branch
+      # set :stage, :staging
+    end
+
+    # You need to add the before/ater callbacks yourself
+    before "deploy:update_code", "release_tagger:set_branch"
+    after  "deploy", "release_tagger:create_tag"
+    after  "deploy", "release_tagger:write_tag_to_shared"
+    after  "deploy", "release_tagger:print_latest_tags"
+
+### Cpistano-ext multistage support
+
+If you use capistano-ext multistage, you can use auto_tagger.
+
+    set :autotagger_stages, [:ci, :staging, :production]
+    set :stages, [:staging, :production]
+    set :default_stage, :staging
+    require 'capistrano/ext/multistage'
+
+When you deploy, autotagger will auto-detect your current stage.
+
+### release_tagger:set_branch
+
+This task sets the git branch to the latest tag from the previous stage.  Assume you have the following tags in your git repository:
+
+  * ci/01
+  * staging/01
+  * production/01
+
+And the following stages in your capistrano file:
+
+    set :autotagger_stages, [:ci, :staging, :production]
+
+The deployments would look like this:
+
+    cap staging release_tagger:set_branch    # => sets branch to ci/01
+    cap production release_tagger:set_branch # => sets branch to staging/01
+
+You can override with with the -Shead and -Stag options
+
+    cap staging release_tagger:set_branch -Shead=true      # => sets branch to master
+    cap staging release_tagger:set_branch -Stag=staging/01 # => sets branch to staging/01
+
+If you add `before "deploy:update_code", "release_tagger:set_branch"`, you can just deploy with:
+
+    cap staging deploy
+    
+and the branch will be set for you automatically.
+
+### release_tagger:create_tag
+
+This cap task creates a new tag, based on the latest tag from the previous environment.  
+
+If there is no tag from the previous stage, it creates a new tag from the latest commit in your _working directory_.
+
+If you don't specify any `autotagger_stages`, autotagger will create a tag that starts with "production".
+
+### release_tagger:print_latest_tags
+
+This task reads the git version from the text file in shared:
+
+    cap staging release_tagger:read_tag_from_shared
+
+### release_tagger:print_latest_tags
+
+This task takes the latest tag from each environment and prints it to the screen.  You can add it to your deploy.rb like so:
+
+    after  "deploy", "release_tagger:print_latest_tags"
+
+Or call it directly, like:
+
+    cap production release_tagger:print_latest_tags
+    
+This will produce output like:
+
+    ** AUTO TAGGER: release tag history is:
+     ** ci         ci/20090331045345              8031807feb5f4f99dd83257cdc07081fa6080cba some commit message
+     ** staging    staging/20090331050908         8031807feb5f4f99dd83257cdc07081fa6080cba some commit message
+     ** production production/20090331050917      8031807feb5f4f99dd83257cdc07081fa6080cba some commit message
+
+## Running tests:
+
+You must be able to ssh into your box via localhost (remote login).  To make this easier, add your own key to your own account:
+
+    cat ~/.ssh/id_rsa.pub >>~/.ssh/authorized_keys
+    
+To ensure that this has worked, try this:
+
+    ssh localhost
+    
+If it asks you for a password, you've done something wrong.
+
+To run the specs, execute:
+
+    spec spec/
+    
+To run the cucumber features, execute:
+
+    cucumber features/
+
+## Acknowledgments
+
+Special thanks to 
+
+ * Brian Takita for the original recipes
+ * Mike Dalessio for his git fu
+ * Chad Wooley for his feature ideas
+ * Tim Holahan for his QA
+
+## Links
+
+ * http://codeintensity.blogspot.com/2008/06/changelogs-and-deployment-notification.html
+  
+Copyright (c) 2009 [Jeff Dean], released under the MIT license

data/Rakefile

@@ -0,0 +1,46 @@
+require 'rubygems'
+require 'rake'
+
+begin
+  require 'jeweler'
+  Jeweler::Tasks.new do |gem|
+    gem.name = "factorylabs-auto_tagger"
+    gem.summary = %Q{Helps you automatically create tags for each stage in a multi-stage deploment and deploy from the latest tag from the previous environment}
+    gem.email = "jeff@zilkey.com"
+    gem.homepage = "http://github.com/zilkey/auto_tagger"
+    gem.authors = ["Jeff Dean", "Brian Takita", "Mike Grafton"]
+    gem.add_dependency('capistrano', [">= 2.5.3"])
+    gem.require_paths = ["lib"]
+    gem.executables = ["autotag"]
+    gem.default_executable = %q{autotag}
+    gem.date = %q{2009-03-28}
+  end
+  Jeweler::GemcutterTasks.new
+rescue LoadError
+  puts "Jeweler (or a dependency) not available. Install it with: sudo gem install jeweler"
+end
+
+require 'spec/rake/spectask'
+Spec::Rake::SpecTask.new(:spec) do |spec|
+  spec.libs << 'lib' << 'spec'
+  spec.spec_files = FileList['spec/**/*_spec.rb']
+end
+
+Spec::Rake::SpecTask.new(:rcov) do |spec|
+  spec.libs << 'lib' << 'spec'
+  spec.pattern = 'spec/**/*_spec.rb'
+  spec.rcov = true
+end
+
+
+task :default => :spec
+
+require 'rake/rdoctask'
+Rake::RDocTask.new do |rdoc|
+  version = File.exist?('VERSION') ? File.read('VERSION') : ""
+
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title = "the-perfect-gem #{version}"
+  rdoc.rdoc_files.include('README*')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end

data/VERSION

@@ -0,0 +1 @@
+0.1.1

data/auto_tagger.gemspec

@@ -0,0 +1,83 @@
+# Generated by jeweler
+# DO NOT EDIT THIS FILE DIRECTLY
+# Instead, edit Jeweler::Tasks in Rakefile, and run the gemspec command
+# -*- encoding: utf-8 -*-
+
+Gem::Specification.new do |s|
+  s.name = %q{auto_tagger}
+  s.version = "0.1.1"
+
+  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
+  s.authors = ["Jeff Dean", "Brian Takita", "Mike Grafton"]
+  s.date = %q{2010-04-06}
+  s.default_executable = %q{autotag}
+  s.email = %q{jeff@zilkey.com}
+  s.executables = ["autotag"]
+  s.extra_rdoc_files = [
+    "README.md"
+  ]
+  s.files = [
+    ".document",
+     ".gitignore",
+     "CHANGELOG",
+     "MIT-LICENSE",
+     "README.md",
+     "Rakefile",
+     "VERSION",
+     "auto_tagger.gemspec",
+     "bin/autotag",
+     "features/autotag.feature",
+     "features/deployment.feature",
+     "features/step_definitions/autotag_steps.rb",
+     "features/step_definitions/deployment_steps.rb",
+     "features/support/env.rb",
+     "features/support/step_helpers.rb",
+     "features/templates/cap_ext_deploy.erb",
+     "features/templates/deploy.erb",
+     "features/templates/stage.erb",
+     "geminstaller.yml",
+     "lib/auto_tagger.rb",
+     "lib/auto_tagger/auto_tagger.rb",
+     "lib/auto_tagger/capistrano_helper.rb",
+     "lib/auto_tagger/commander.rb",
+     "lib/auto_tagger/recipes.rb",
+     "lib/auto_tagger/repository.rb",
+     "lib/auto_tagger/stage_manager.rb",
+     "lib/auto_tagger/tag.rb",
+     "spec/auto_tagger/auto_tagger_spec.rb",
+     "spec/auto_tagger/capistrano_helper_spec.rb",
+     "spec/auto_tagger/commander_spec.rb",
+     "spec/auto_tagger/repository_spec.rb",
+     "spec/auto_tagger/stage_manager_spec.rb",
+     "spec/auto_tagger/tag_spec.rb",
+     "spec/spec_helper.rb"
+  ]
+  s.homepage = %q{http://github.com/zilkey/auto_tagger}
+  s.rdoc_options = ["--charset=UTF-8"]
+  s.require_paths = ["lib"]
+  s.rubygems_version = %q{1.3.6}
+  s.summary = %q{Helps you automatically create tags for each stage in a multi-stage deploment and deploy from the latest tag from the previous environment}
+  s.test_files = [
+    "spec/auto_tagger/auto_tagger_spec.rb",
+     "spec/auto_tagger/capistrano_helper_spec.rb",
+     "spec/auto_tagger/commander_spec.rb",
+     "spec/auto_tagger/repository_spec.rb",
+     "spec/auto_tagger/stage_manager_spec.rb",
+     "spec/auto_tagger/tag_spec.rb",
+     "spec/spec_helper.rb"
+  ]
+
+  if s.respond_to? :specification_version then
+    current_version = Gem::Specification::CURRENT_SPECIFICATION_VERSION
+    s.specification_version = 3
+
+    if Gem::Version.new(Gem::RubyGemsVersion) >= Gem::Version.new('1.2.0') then
+      s.add_runtime_dependency(%q<capistrano>, [">= 2.5.3"])
+    else
+      s.add_dependency(%q<capistrano>, [">= 2.5.3"])
+    end
+  else
+    s.add_dependency(%q<capistrano>, [">= 2.5.3"])
+  end
+end
+

data/bin/autotag

@@ -0,0 +1,38 @@
+#!/usr/bin/env ruby
+require File.expand_path(File.join(File.dirname(__FILE__), "..", "lib", "auto_tagger"))
+require 'getoptlong'
+
+opts = GetoptLong.new(
+  ['--help', '-h', '-?', GetoptLong::NO_ARGUMENT]
+)
+
+def usage
+  puts
+  puts "USAGE: #{File.basename($0)} <stage> [<repository>]"
+  puts
+  puts '    where:    stage       sets the tag prefix'
+  puts '              repository  sets the repository to act on - defualts to the current directory'
+  puts
+  puts '    examples: autotag'
+  puts '              autotag .'
+  puts '              autotag ../'
+  puts '              autotag /data/myrepo'
+  puts '              autotag demo'
+  puts
+  puts
+  exit 0
+end
+
+opts.each do |opt, arg|
+  case opt
+  when "--help"
+    usage
+  end
+end
+
+if ARGV[0]
+  AutoTagger.new(ARGV[0], ARGV[1]).create_tag
+  exit 0
+else
+  usage
+end

data/features/autotag.feature

@@ -0,0 +1,39 @@
+Feature: Deployment
+  In order to get auto-tagging goodness on ci boxes
+  As a ruby and git ninja
+  I want to be able to easily create a tag from the command line with the same name format as the one created by the cap tasks
+
+  Scenario: user runs autotag with no args
+    Given a repo
+    When I run autotag with no arguments
+    Then I should see "USAGE:"
+    And no tags should be created
+    
+  Scenario: user runs autotag with "--help"
+    Given a repo
+    When I run autotag with "--help"
+    Then I should see "USAGE:"
+    And no tags should be created
+
+  Scenario: user runs autotag with "-h"
+    Given a repo
+    When I run autotag with "-h"
+    Then I should see "USAGE:"
+    And no tags should be created
+
+  Scenario: user runs autotag with "-?"
+    Given a repo
+    When I run autotag with "-?"
+    Then I should see "USAGE:"
+    And no tags should be created
+
+  Scenario: user runs autotag with "demo"
+    Given a repo
+    When I run autotag with "demo"
+    # can't check output here for some reason
+    Then a "demo" tag should be created
+
+  Scenario: user runs autotag with "demo ."
+    Given a repo
+    When I run autotag with "demo"
+    Then a "demo" tag should be created