Repository URL to install this package:
|
Version:
1.7.4 ▾
|
| bin |
| lib |
| Gemfile |
| README.md |
| uoy-faculty-rake.gemspec |
Add the following to your Gemfile:
source 'https://gem.fury.io/universityofyork/' do group :development do gem 'uoy-faculty-rake', '~> 0.1' end end
And then execute:
$ bundle
Or install it yourself as:
$ gem install --source https://gem.fury.io/universityofyork/ uoy-faculty-rake
In your Rakefile:
require 'faculty/rake'
Then you can initialise rake tasks as required:
Faculty::Rake::BaseUpdate.new 'path-to-base-remote-repository' # For gems Faculty::Rake::GemRename.new # For sinatra apps Faculty::Rake::DockerTasks.new Faculty::Rake::NodeTasks.new Faculty::Rake::SinatraInit.new # For AWS apps Faculty::Rake::Deploy.new
Your Gem's version is picked up automatically from lib/faculty/rake.rb. When any
changes are pushed to master, after the normal CI tasks the pipeline will push
to gemfury automatically. The usual workflow is:
For minor changes, update VERSION and make the change in a single commit
For anything else, create a branch and set VERSION to the version you're
aiming to release for. Make the changes; when the branch is merged, the gem
will be uploaded.
Note that gemfury will never overwrite an existing gem version, even if the old one is yanked!
Tests can be run via rake: rake spec - this doesn't run
performance tests; they can be run separately via rake perf.
You can also run rspec normally e.g. bundle exec rspec -fd.
If you have performance tests that take a while, tag the context / describe
block like this:
context 'when foo is bar baz', :perf do
...
end
Bug reports and pull requests are welcome at https://github.com/university-of-york/faculty-dev-rake-gem