beetle 3.0.0.rc2 → 3.0.0.rc4
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 +4 -4
- data/README.rdoc +32 -2
- data/RELEASE_NOTES.rdoc +8 -0
- data/Rakefile +4 -4
- data/lib/beetle/version.rb +1 -1
- metadata +2 -4
- data/features/README.rdoc +0 -23
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: '099a52ef69ab0d75ed3027dc22154f482e4595c2d259117af8b5be4db556e832'
|
4
|
+
data.tar.gz: 5deea72b588ba0cef6666641b41a66c7bcffd2b479dc7dbfe2abd6c835d067d5
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 5368bd7b2c9fd9f910d5068ca95f9be7d44b4b09bbbf94c2a14ba8f692a3d13fc4b47595bf7f0256a0a488a0ee5feb319370271e620ccc6ab4df5dcbc7bb2ca0
|
7
|
+
data.tar.gz: 1f06cbdaa672e7bf68d58506dde08efbb0310c34937881b1b8ec0abb73a149bf48b3706eacf3c4a241fddbb91c8062e067c594e6bf7b7ef2b57f40f314342e4c
|
data/README.rdoc
CHANGED
@@ -121,8 +121,7 @@ distribution.
|
|
121
121
|
|
122
122
|
1. Fork it
|
123
123
|
2. Create your feature branch (`git checkout -b my-new-feature`)
|
124
|
-
3. Hack along and test your code
|
125
|
-
cucumber. You must start consul in order to use cucumber.
|
124
|
+
3. Hack along and test your code.
|
126
125
|
4. Commit your changes (`git commit -am 'Add some feature'`)
|
127
126
|
5. Push to the branch (`git push origin my-new-feature`)
|
128
127
|
6. Create new Pull Request
|
@@ -130,6 +129,37 @@ distribution.
|
|
130
129
|
Don't increase the gem version in your pull requests. It will be done after merging the request,
|
131
130
|
to allow merging of pull requests in a flexible order.
|
132
131
|
|
132
|
+
== Running the tests
|
133
|
+
|
134
|
+
Beetle ships with a cucumber feature to test the automatic redis failover
|
135
|
+
as an integration test.
|
136
|
+
|
137
|
+
To run it, you have to start a RabbitMQ server and a consul
|
138
|
+
development mode.
|
139
|
+
|
140
|
+
The top level Rakefile comes with targets to start several RabbitMQ
|
141
|
+
instances locally. Make sure the corresponding binaries are in your
|
142
|
+
search path. Open two shell windows and execute the following command:
|
143
|
+
|
144
|
+
rake rabbit:start1
|
145
|
+
|
146
|
+
and
|
147
|
+
|
148
|
+
rake consul:start
|
149
|
+
|
150
|
+
Then you can run the cucumber feature by running:
|
151
|
+
|
152
|
+
cucumber
|
153
|
+
|
154
|
+
or
|
155
|
+
|
156
|
+
rake cucumber
|
157
|
+
|
158
|
+
|
159
|
+
Note: Cucumber will automatically run after the unit test when you run rake.
|
160
|
+
|
161
|
+
|
162
|
+
|
133
163
|
== How to release a new gem version
|
134
164
|
|
135
165
|
Update RELEASE_NOTES.rdoc!
|
data/RELEASE_NOTES.rdoc
CHANGED
@@ -1,5 +1,9 @@
|
|
1
1
|
= Release Notes
|
2
2
|
|
3
|
+
== Version 3.0.0.rc3
|
4
|
+
* store redis gc stats in redis and display them in the configuration
|
5
|
+
server web UI
|
6
|
+
|
3
7
|
== Version 3.0.0.rc2
|
4
8
|
* change policy setup to be asynchronous, on demand in publisher and
|
5
9
|
consumer. Users have to run a processors to listen to messages and
|
@@ -9,6 +13,10 @@
|
|
9
13
|
expiry times.
|
10
14
|
* added delete_queue_keys command to beetle to allow deletion of
|
11
15
|
excess dedup store entries for a given queue.
|
16
|
+
* config server: store current master server in consul, if consul
|
17
|
+
config has been provided.
|
18
|
+
* config server: server correctly updates configured client ids when
|
19
|
+
they change in consul.
|
12
20
|
|
13
21
|
== Version 3.0.0.rc1
|
14
22
|
* provide client method to setup queues and queue policies.
|
data/Rakefile
CHANGED
@@ -83,10 +83,10 @@ namespace :redis do
|
|
83
83
|
end
|
84
84
|
|
85
85
|
namespace :consul do
|
86
|
-
|
87
|
-
|
88
|
-
|
89
|
-
|
86
|
+
desc "start consul agent in development mode"
|
87
|
+
task :start do
|
88
|
+
system "consul agent -dev -node machine"
|
89
|
+
end
|
90
90
|
end
|
91
91
|
|
92
92
|
Cucumber::Rake::Task.new(:cucumber) do |t|
|
data/lib/beetle/version.rb
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: beetle
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 3.0.0.
|
4
|
+
version: 3.0.0.rc4
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Stefan Kaes
|
@@ -12,7 +12,7 @@ authors:
|
|
12
12
|
autorequire:
|
13
13
|
bindir: bin
|
14
14
|
cert_chain: []
|
15
|
-
date: 2019-05-
|
15
|
+
date: 2019-05-20 00:00:00.000000000 Z
|
16
16
|
dependencies:
|
17
17
|
- !ruby/object:Gem::Dependency
|
18
18
|
name: bunny
|
@@ -299,7 +299,6 @@ email: opensource@xing.com
|
|
299
299
|
executables: []
|
300
300
|
extensions: []
|
301
301
|
extra_rdoc_files:
|
302
|
-
- features/README.rdoc
|
303
302
|
- RELEASE_NOTES.rdoc
|
304
303
|
- examples/README.rdoc
|
305
304
|
- REDIS_AUTO_FAILOVER.rdoc
|
@@ -328,7 +327,6 @@ files:
|
|
328
327
|
- examples/redundant.rb
|
329
328
|
- examples/rpc.rb
|
330
329
|
- examples/simple.rb
|
331
|
-
- features/README.rdoc
|
332
330
|
- features/redis_auto_failover.feature
|
333
331
|
- features/step_definitions/redis_auto_failover_steps.rb
|
334
332
|
- features/support/beetle_handler
|
data/features/README.rdoc
DELETED
@@ -1,23 +0,0 @@
|
|
1
|
-
=== Cucumber
|
2
|
-
|
3
|
-
Beetle ships with a cucumber feature to test the automatic redis failover
|
4
|
-
as an integration test.
|
5
|
-
|
6
|
-
To run it, you have to start a RabbitMQ.
|
7
|
-
|
8
|
-
The top level Rakefile comes with targets to start several RabbitMQ instances locally.
|
9
|
-
Make sure the corresponding binaries are in your search path. Open a new shell
|
10
|
-
and execute the following command:
|
11
|
-
|
12
|
-
rake rabbit:start1
|
13
|
-
|
14
|
-
Then you can run the cucumber feature by running:
|
15
|
-
|
16
|
-
cucumber
|
17
|
-
|
18
|
-
or
|
19
|
-
|
20
|
-
rake cucumber
|
21
|
-
|
22
|
-
|
23
|
-
Note: Cucumber will automatically run after the unit test when you run rake.
|