murmurs 0.1.1 → 0.1.2

Sign up to get free protection for your applications and to get access to all the features.
Files changed (2) hide show
  1. data/README.md +32 -4
  2. metadata +8 -6
data/README.md CHANGED
@@ -40,11 +40,39 @@ Note, the post-receive hook installed will never block you push commits to serve
40
40
  Test Git integration
41
41
  -------------------
42
42
 
43
- To confirm you can post a murmur o your Mingle project from the Git server with the configurations, you can run the following command:
43
+ If you had concerns and wanted to try out before trying out on your production Git server, you can try the followings to get the idea of how your Git server will integrate with your Mingle project. (Please install murmurs gem, and get all configurations mentioned above ready before you start)
44
44
 
45
- murmurs -m https://site-name.mingle-api.thoughtworks.com/api/v2/projects/your_project/murmurs.xml -k mingle_access_key_id -s mingle_access_secure_key "This is a test."
45
+ Create a local git repository
46
+
47
+ cd /tmp
48
+ mkdir mingle_test
49
+ cd mingle_test
50
+ git init --bare
51
+
52
+ Setup murmurs git integration
53
+
54
+ murmurs -a /tmp/mingle_test
55
+ cd /tmp/mingle_test
56
+ git config hooks.minglemurmursurl "https://<your-site>.mingle-api.thoughtworks.com/api/v2/projects/<your-project>/murmurs.xml"
57
+ git config hooks.mingleaccesskeyid <Mingle user access key id>
58
+ git config hooks.mingleaccesssecretkey <Mingle user access secret key>
46
59
 
47
- Type "murmurs -h" for full details.
60
+ Clone a local test repository
48
61
 
62
+ cd /tmp
63
+ git clone mingle_test mingle_test_local
64
+
65
+ Make an empty commit and push to origin master to trigger post-receive hook on origin repository
66
+
67
+ cd mingle_test_local
68
+ git commit --allow-empty -m "hello world, this is git mingle integration test"
69
+ git push origin master
70
+
71
+ Test post a murmur on your project
72
+ -------------------
73
+
74
+ To confirm you can post a murmur to your Mingle project from the Git server with the configurations, you can run the following command:
75
+
76
+ murmurs -m https://site-name.mingle-api.thoughtworks.com/api/v2/projects/your_project/murmurs.xml -k mingle_access_key_id -s mingle_access_secure_key "This is a test."
49
77
 
50
- So before you integrate Git server with your Mingle project, you can test the configurations on your Git server first, for example:
78
+ Type "murmurs -h" for full details of the options available.
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: murmurs
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.1
4
+ version: 0.1.2
5
5
  prerelease:
6
6
  platform: ruby
7
7
  authors:
@@ -27,9 +27,11 @@ dependencies:
27
27
  - - ! '>='
28
28
  - !ruby/object:Gem::Version
29
29
  version: 1.0.3
30
- description: ! 'Post murmur to your Mingle project from command line.
30
+ description: ! 'Itegrate Git with your Mingle project by posting murmurs to your Mingle
31
+ project when new commits got pushed to Git server.
31
32
 
32
- Git post-receive hook to post murmurs when new commits pushed to Git server.
33
+ This gem provides command to generate Git post-receive hook and post murmurs to
34
+ your Mingle project.
33
35
 
34
36
  '
35
37
  email:
@@ -58,7 +60,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
58
60
  version: '0'
59
61
  segments:
60
62
  - 0
61
- hash: 716371937611647900
63
+ hash: -2214621304214247920
62
64
  required_rubygems_version: !ruby/object:Gem::Requirement
63
65
  none: false
64
66
  requirements:
@@ -67,11 +69,11 @@ required_rubygems_version: !ruby/object:Gem::Requirement
67
69
  version: '0'
68
70
  segments:
69
71
  - 0
70
- hash: 716371937611647900
72
+ hash: -2214621304214247920
71
73
  requirements: []
72
74
  rubyforge_project:
73
75
  rubygems_version: 1.8.23
74
76
  signing_key:
75
77
  specification_version: 3
76
- summary: Post murmur to Mingle project murmurs
78
+ summary: Integrate Git with your Mingle project
77
79
  test_files: []