capistrano-raygun-deployment 1.0.0 → 1.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +8 -8
- data/README.md +8 -2
- data/VERSION +1 -1
- data/lib/capistrano/tasks/raygun-deployment.cap +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,15 +1,15 @@
|
|
|
1
1
|
---
|
|
2
2
|
!binary "U0hBMQ==":
|
|
3
3
|
metadata.gz: !binary |-
|
|
4
|
-
|
|
4
|
+
YzZlZGU5YTE4MGVlM2E0NjRiNTUwNTMxMjEyM2VkZmFiYWIyNDA3Zg==
|
|
5
5
|
data.tar.gz: !binary |-
|
|
6
|
-
|
|
6
|
+
NThhNWMyYjkwNjgxYmRmODIyZjI2MTBiNWFkMDRjYjM3OTQ4Mzk4OQ==
|
|
7
7
|
SHA512:
|
|
8
8
|
metadata.gz: !binary |-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
9
|
+
MzI0OTA3MTBkMmZlNGYxNTBiMTdmZjBiZmY5Njc2MWVlYmYwNTcxNzQyNGYy
|
|
10
|
+
MGQ0OGFkNjhiMThiMTU1MmNlMTk0YzJkMjJmOWU3ZjZmYjZiYmIzYTA3Yjk2
|
|
11
|
+
MzRjNzQxYWE3OTM5NGNiMWYxNjJlM2E4MjFkZjk0NzJiMDJlODU=
|
|
12
12
|
data.tar.gz: !binary |-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
13
|
+
MzMwNzJmZWQ3MTk2NzcwYTkwNjYzNDkzZjY2OTAzMTA1NzEzNThkMTAxZjk3
|
|
14
|
+
YjYxODExZDAwMTgxOTdiN2IwZWY3NmZlZjRlODhiMzUwNDI4ZWU1OTZiYWY2
|
|
15
|
+
ODU3ZjRjODg0OTk2ZTg1MzQxMDRkOGJiM2RlYjNiY2M4YmMzMWE=
|
data/README.md
CHANGED
|
@@ -29,7 +29,7 @@ You'll need the Raygun API Key for your application, plus an External Auth Token
|
|
|
29
29
|
Finally, create a release file. We default to checking `RELEASE`, but you can change this by setting `:raygun_release_path`
|
|
30
30
|
This is an example release file:
|
|
31
31
|
|
|
32
|
-
version: 6.0.0
|
|
32
|
+
version: 6.0.0
|
|
33
33
|
ownerName: Jamie Penney
|
|
34
34
|
emailAddress: jamie@example.com
|
|
35
35
|
notes: |
|
|
@@ -39,4 +39,10 @@ This is an example release file:
|
|
|
39
39
|
|
|
40
40
|
### Jamie
|
|
41
41
|
|
|
42
|
-
Once you've written this to `RELEASE`, you can deploy with `cap deploy` and your deployment will be sent to Raygun!
|
|
42
|
+
Once you've written this to `RELEASE`, you can deploy with `cap deploy` and your deployment will be sent to Raygun!
|
|
43
|
+
|
|
44
|
+
# Changelog
|
|
45
|
+
|
|
46
|
+
* **1.1.0**: Use `after deploy:finished` instead of `after :published` so that deployments are only pushed to Raygun when things
|
|
47
|
+
fully succeed.
|
|
48
|
+
* **1.0.0**: Initial release
|
data/VERSION
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
1.
|
|
1
|
+
1.1.0
|
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: capistrano-raygun-deployment
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 1.
|
|
4
|
+
version: 1.1.0
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Jamie Penney
|
|
@@ -9,7 +9,7 @@ authors:
|
|
|
9
9
|
autorequire:
|
|
10
10
|
bindir: bin
|
|
11
11
|
cert_chain: []
|
|
12
|
-
date: 2015-
|
|
12
|
+
date: 2015-09-14 00:00:00.000000000 Z
|
|
13
13
|
dependencies: []
|
|
14
14
|
description: A capistrano task to notify Raygun.io of a deployment
|
|
15
15
|
email: hello@raygun.io
|