capistrano-deploytags 1.0.4 → 1.0.5
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/lib/capistrano/deploytags.rb +1 -1
- metadata +8 -5
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 3947b46418a3587766b346b9d6cefd3e452b1248
|
|
4
|
+
data.tar.gz: 6dae6ea7df761fe5f7528182906711490b917a6e
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: cdd7c25fc00efc7dac3b4b852e27cf9a7ab08f3227ea39c7f4f9a6439969bdde4a8b8f84fddacef3e38901fd2c06d887bc62399faafe35da0487bf44a3de5deb
|
|
7
|
+
data.tar.gz: 5e025c1dc4941b38495c7cf9668422b9f6ae2bc1b2bc41ffee10e01ae19f1fbb3b8d492dd01e727d30fccb3ad6f11930de77bd72612d2ae5d35f8a4f8cd489cf
|
|
@@ -22,7 +22,7 @@ module CapistranoDeploytags
|
|
|
22
22
|
|
|
23
23
|
def self.commit_message(current_sha, stage)
|
|
24
24
|
if fetch(:deploytag_commit_message, false)
|
|
25
|
-
deploytag_commit_message
|
|
25
|
+
fetch(:deploytag_commit_message)
|
|
26
26
|
else
|
|
27
27
|
tag_user = (ENV['USER'] || ENV['USERNAME'] || 'deployer').strip
|
|
28
28
|
"#{tag_user} deployed #{current_sha} to #{stage}"
|
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: capistrano-deploytags
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 1.0.
|
|
4
|
+
version: 1.0.5
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Karl Matthias
|
|
@@ -53,8 +53,12 @@ dependencies:
|
|
|
53
53
|
- - "~>"
|
|
54
54
|
- !ruby/object:Gem::Version
|
|
55
55
|
version: 3.0.0
|
|
56
|
-
description:
|
|
57
|
-
|
|
56
|
+
description: " Capistrano Deploytags is a simple plugin to Capistrano 3 that works
|
|
57
|
+
with your deployment framework to track your code releases. All you have to do is
|
|
58
|
+
require capistrano-deploytags/capistrano and each deployment will add a new tag
|
|
59
|
+
for that deployment, pointing to the latest commit. This lets you easily see which
|
|
60
|
+
code is deployed on each environment, and allows you to figure out which code was
|
|
61
|
+
running in an environment at any time in the past.\n"
|
|
58
62
|
email:
|
|
59
63
|
- relistan@gmail.com
|
|
60
64
|
- gavin.heavyside@mydrivesolutions.com
|
|
@@ -87,9 +91,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
|
87
91
|
version: '0'
|
|
88
92
|
requirements: []
|
|
89
93
|
rubyforge_project:
|
|
90
|
-
rubygems_version: 2.
|
|
94
|
+
rubygems_version: 2.5.1
|
|
91
95
|
signing_key:
|
|
92
96
|
specification_version: 4
|
|
93
97
|
summary: Add dated, environment-specific tags to your git repo at each deployment.
|
|
94
98
|
test_files: []
|
|
95
|
-
has_rdoc:
|