propel 0.1.3 → 0.2.1

Sign up to get free protection for your applications and to get access to all the features.
Files changed (4) hide show
  1. data/Gemfile.lock +1 -1
  2. data/README.md +8 -1
  3. data/lib/propel/version.rb +1 -1
  4. metadata +3 -3
data/Gemfile.lock CHANGED
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- propel (0.1.2)
4
+ propel (0.2.1)
5
5
  json
6
6
 
7
7
  GEM
data/README.md CHANGED
@@ -23,7 +23,14 @@ passing the option --status-url http://ci.example.com/yourbuild.rss. Propel wil
23
23
  passing as of the latest commit for Jenkins, Team City and CI Joe.
24
24
 
25
25
  Once you figure out the options that work for you, just put a .propel file in the root of your project.
26
- Command line parameters override the options found in the configuration file.
26
+ Command line parameters override the options found in the configuration file. Your configuration file should
27
+ have one parameter on each line. For example:
28
+
29
+ --status-url http://ci.example.com/job/Test%20project/rssAll
30
+ --wait
31
+
32
+ This will set the status url for the project, and default to waiting for the CI build to pass if it is currently
33
+ failing.
27
34
 
28
35
  ## Credits
29
36
 
@@ -1,3 +1,3 @@
1
1
  module Propel
2
- VERSION = "0.1.3"
2
+ VERSION = "0.2.1"
3
3
  end
metadata CHANGED
@@ -1,13 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: propel
3
3
  version: !ruby/object:Gem::Version
4
- hash: 29
4
+ hash: 21
5
5
  prerelease:
6
6
  segments:
7
7
  - 0
8
+ - 2
8
9
  - 1
9
- - 3
10
- version: 0.1.3
10
+ version: 0.2.1
11
11
  platform: ruby
12
12
  authors:
13
13
  - Justin Leitgeb