jumpup 0.0.3 → 0.0.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 5105b8cc0da609d273f7949b1c9166faf4ac13f3
-  data.tar.gz: 688b114ef4fbf248707d10819991e8c32bb29914
+  metadata.gz: e36b05e3160d56be778d4ee5fa6fd6ea340b8954
+  data.tar.gz: e9c71ca167b554c15e17e6054a918943e28a564b
 SHA512:
-  metadata.gz: e9f6a6988584c24c816e412b11069a87c8aacbe3c898a8dc70c2d3849fb2a3064cbf11cfe8d74fa3f2d3241f56b2a1d79305c28682873e50d1634ab7951de668
-  data.tar.gz: bcb16b9ed90d99ac95085dbf170251717851ec28021b02f25d484c8340cf1a030c91540b2e637ad3c7c4e9a0eec56d9dad2904c84592b2eb98934dc9140492b0
+  metadata.gz: d13c442344af3b29629a976aaf0632abaa2bb4dab0a9c874287b50ec30842c9f330423c3c5a9f9c2ae4f0c4939733aeaf30a7ff868bd79326f4791765d7373eb
+  data.tar.gz: 9cca81bf281ee387f35597ff49183ae7810ddbbf1800dbfcfcae49c9c5d9c09cc23cf8c0d2d789f4cb0c2da8806e132ed2b4512c184d5a4a222efff21eb14d5a

data/CHANGELOG.md

@@ -1,5 +1,34 @@
 # Changelog
 
+## 0.0.4 (February 21, 2014)
+
+### features
+
+### improvements
+
+- Create a CONTRIBUTING file
+- Add info about how release the gem
+- Add info about issues
+- Add info about contributing
+- Add info about credits
+
+### bug fixes
+
+- Fix bundle install on bundler 1.5.2 when have gems from github
+
+## 0.0.3 (January 17, 2014)
+
+### features
+
+### improvements
+
+- Name correct tasks on README
+- Add rake dependency as 0
+
+### bug fixes
+
+- Fix coverage that dont stop the integrate
+
 ## 0.0.2 (January 8, 2014)
 
 ### features

data/CONTRIBUTING.md

@@ -0,0 +1,21 @@
+# Contributing
+
+We love pull requests. Here's a quick guide:
+
+1. Fork the repo.
+
+1. Create your feature branch (`git checkout -b my-new-feature`)
+
+1. Update [CHANGELOG.md](https://github.com/Helabs/jumpup/blob/master/CHANGELOG.md) with a brief description of your changes under the `unreleased` heading.
+
+1. Commit your changes (`git commit -am 'Added some feature'`)
+
+1. Push to the branch (`git push origin my-new-feature`)
+
+1. Create new Pull Request
+
+At this point you're waiting on us. We like to at least comment on, if not
+accept, pull requests within three business days (and, typically, one business
+day). We may suggest some changes or improvements or alternatives.
+
+Some things that will increase the chance that your pull request is accepted is to follow the practices described on [Ruby style guide](https://github.com/bbatsov/ruby-style-guide), [Rails style guide](https://github.com/bbatsov/rails-style-guide) and [Better Specs](http://betterspecs.org/).

data/README.mkdn

@@ -1,8 +1,9 @@
 # Jumpup
+[![RubyGems][gem_version_badge]][ruby_gems]
 
 ## What
 
-Jumpup is a [Ruby on Rails][ror] plugin that provides a set of tasks to automate all steps of a [synchronous continuous integration][sci] process, that is, [continuous integration][ci] without a server such as [CruiseControl][cc]. Why? Because that's the way we like it!
+Jumpup is a [Ruby on Rails][ror] gem that provides a set of tasks to automate all steps of a [synchronous continuous integration][sci] process, that is, [continuous integration][ci] without a server such as [Travis][travis]. Why? Because that's the way we like it!
 
 ## Installing
 
@@ -12,7 +13,7 @@ Add it to your Gemfile:
       gem 'jumpup'
     end
 
-After installing the plugin is ready to be used and you will need to execute only one task in order to integrate your code safely:
+After installing the gem is ready to be used and you will need to execute only one task in order to integrate your code safely:
 
     rake integrate
 
@@ -102,7 +103,7 @@ Using this almost paranoid sequence of steps it will be hard to check in bad cod
           jumpup:finish
         )
 
-  As a matter of fact, since this case might be very common, **we decided to create a lib/tasks/integration.rake for you once the plugin has been installed. It has this very configuration and you can use it as a starting point to customize your integration process**.
+  As a matter of fact, since this case might be very common, **we decided to create a lib/tasks/integration.rake for you once the gem has been installed. It has this very configuration and you can use it as a starting point to customize your integration process**.
 
 * Spec infected programmer
 
@@ -120,6 +121,25 @@ Using this almost paranoid sequence of steps it will be hard to check in bad cod
 
 Jumpup follows the [Semantic Versioning](http://semver.org/).
 
+## Issues
+
+If you have problems, please create a [Github Issue](https://github.com/Helabs/jumpup/issues).
+
+## Contributing
+
+Please see [CONTRIBUTING.md](https://github.com/Helabs/jumpup/blob/master/CONTRIBUTING.md) for details.
+
+## Release
+
+Follow this steps to release a new version of the gem.
+
+1. Test if everything is running ok;
+1. Change version of the gem on `VERSION` constant;
+1. Add the release date on the `CHANGELOG`;
+1. Do a commit "Bump version x.x.x", follow the semantic version;
+1. Run `$ rake release`, this will send the gem to the rubygems;
+1. Check if the gem is on the rubygems and the tags are correct on the github;
+
 ## License
 
 This code is free to be used under the terms of the [MIT license][mit].
@@ -136,7 +156,14 @@ Jumpup came from the idea of [integration](https://github.com/tapajos/integratio
 * [Sylvestre Mergulhão][sm]
 * [Vinícius Teles][vt]
 
+## Credits
+
+Jumpup is maintained and funded by [HE:labs](http://helabs.com.br/opensource/).
+Thank you to all the [contributors](https://github.com/Helabs/jumpup/graphs/contributors).
+
 
+[gem_version_badge]: https://badge.fury.io/rb/jumpup.png
+[ruby_gems]: http://rubygems.org/gems/jumpup
 [piston]:  http://piston.rubyforge.org/
 [mt]:    https://github.com/tapajos
 [sm]:   https://github.com/mergulhao
@@ -154,8 +181,8 @@ Jumpup came from the idea of [integration](https://github.com/tapajos/integratio
 [co]:    http://www.improveit.com.br/en/contact
 [mit]:  http://www.opensource.org/licenses/mit-license.php
 [ci]:   http://martinfowler.com/articles/continuousIntegration.html
-[cc]:   http://cruisecontrol.sourceforge.net
+[travis]: http://travis-ci.org
 [tar]:  http://en.wikipedia.org/wiki/Tar_%28file_format%29
 [BDD]:  http://en.wikipedia.org/wiki/Behavior_driven_development
 [TDD]:  http://en.wikipedia.org/wiki/Test-driven_development
-[ii]:   http://www.improveit.com.br
+[ii]:   http://www.improveit.com.br

data/lib/jumpup/version.rb

@@ -1,3 +1,3 @@
 module Jumpup
-  VERSION = "0.0.3"
+  VERSION = '0.0.4'
 end

data/lib/tasks/integrate.rake

@@ -41,7 +41,9 @@ namespace :jumpup do
 
   desc 'Run bundle install'
   task :bundle_install do
-    sh 'bundle install --quiet'
+    Bundler.with_clean_env do
+      sh 'bundle install --quiet'
+    end
   end
 
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: jumpup
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.0.4
 platform: ruby
 authors:
 - HE:labs
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-01-17 00:00:00.000000000 Z
+date: 2014-02-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -47,6 +47,7 @@ extra_rdoc_files: []
 files:
 - ".gitignore"
 - CHANGELOG.md
+- CONTRIBUTING.md
 - Gemfile
 - MIT-LICENSE
 - README.mkdn
@@ -76,7 +77,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.2.0
+rubygems_version: 2.2.1
 signing_key: 
 specification_version: 4
 summary: Jumpup gem help people that want to do synchronous continuous integration