depl 0.0.1 → 0.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 68f043ef8f3eee4c482df1aeb3d01a3260591faf
-  data.tar.gz: 7931ea5e765b4dc6b669c7dd475f3f44fe8b407e
+  metadata.gz: 0405248bce5c6321632cbbb540b4c913b803103d
+  data.tar.gz: f23990bbb4bc143cf80cfdb06a9eb9ce8d9fadbb
 SHA512:
-  metadata.gz: 9cc658d19daabfa9c1b24e3d693eaffc7787e72a340cb0ad41f835b24772d8864e1310eebb9f6449183e3a6e28fd62b979e77408b43f61c1312ddd1e5f4971fe
-  data.tar.gz: 35a5440ae2c9bd56e30f10e6c1efce23813d38275668d63c3c9303c01ad7a7f69327521f8e1b6d165a4d3c08e73feff6c738f5051975e33310343dec9d2453b9
+  metadata.gz: 331d2951f60cb9aa44a0139032165e40243b17240c2fa7e912febbbbd2b5ec061c25f95f2974a85ed0ff41442103ae381e1ed8b9a15ec3ea2c20a21683683dbd
+  data.tar.gz: eef9109183ae547b604e63293cbc900e8fa901cc4009c263e5cc0603f0cb48713bbb58010d5952371790c76ad05bf0527352cf55771196bbd8e122c23c67c7f8

data/README.md

@@ -27,6 +27,7 @@ Movable Ink uses Chef to push out new code, and Chef is set up to use environmen
 
 ## History
 
+* _0.0.2_ - Updated gem description.
 * _0.0.1_ - Forked from deploy_s3; initial release.
 
 ## License

data/depl.gemspec

@@ -10,7 +10,7 @@ Gem::Specification.new do |s|
   s.homepage    = "https://github.com/movableink/depl"
   s.summary     = %q{Writes project deployment hash to s3 file}
   s.licenses    = "MIT"
-  s.description = %q{Separate out the deployment concerns from your application by using depl to write your latest deployed git hash to s3. Then let your provisioning system (for instance, chef + deploy_revision provider) take care of actually deploying new code. depl shows diffs between your current branch and the deployed revision.}
+  s.description = %q{Separate out the deployment concerns from your application by using depl to update your git branches. Then let your provisioning system (for instance, chef + deploy_revision provider) take care of actually deploying new code. depl shows diffs between your current branch and the deployed revision.}
 
   s.add_runtime_dependency "highline", "~> 1.6"
   s.add_runtime_dependency "colorize", "~> 0.7"

data/lib/depl/version.rb

@@ -1,3 +1,3 @@
 module Depl
-  VERSION = "0.0.1"
+  VERSION = "0.0.2"
 end

data/spec/depl/main_spec.rb

@@ -2,8 +2,7 @@ require 'spec_helper'
 
 describe Depl::Main do
   let(:deploy) {
-    Depl::Main.new(:environment => 'production',
-                       :config => {'s3' => 'my-bucket/deployments/foo'})
+    Depl::Main.new(:environment => 'production')
   }
 
   describe '#environment' do
@@ -12,18 +11,6 @@ describe Depl::Main do
     end
   end
 
-  describe '#filename' do
-    it 'computes the filename' do
-      expect(deploy.filename).to eql('production.sha')
-    end
-  end
-
-  describe '#key' do
-    it 'computes the key' do
-      expect(deploy.key).to eq('deployments/foo/production.sha')
-    end
-  end
-
   describe '#diff' do
     it 'uses git to find the commits between two shas' do
       deploy.should_receive(:remote_sha).and_return("remote")
@@ -36,6 +23,17 @@ describe Depl::Main do
     end
   end
 
+  describe '#save_sha' do
+    it 'pushes a sha to the origin' do
+      deploy.should_receive(:local_sha).and_return("12345")
+
+      cmd = "git push --force origin 12345:refs/heads/deploy-production"
+      deploy.should_receive(:execute).with(cmd)
+
+      deploy.save_sha
+    end
+  end
+
   describe '#up_to_date' do
     it 'returns true when shas match' do
       deploy.should_receive(:remote_sha).and_return("same")

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: depl
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 0.0.2
 platform: ruby
 authors:
 - Michael Nutt
@@ -53,9 +53,9 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '2.5'
 description: Separate out the deployment concerns from your application by using depl
-  to write your latest deployed git hash to s3. Then let your provisioning system
-  (for instance, chef + deploy_revision provider) take care of actually deploying
-  new code. depl shows diffs between your current branch and the deployed revision.
+  to update your git branches. Then let your provisioning system (for instance, chef
+  + deploy_revision provider) take care of actually deploying new code. depl shows
+  diffs between your current branch and the deployed revision.
 email:
 - michael@movableink.com
 executables: