View Rake on the plugin site for more information.
This plugin allows Jenkins to invoke Rake tasks as build steps.
The plugin detects the ruby VM installed on the host and it allows you to include new instances. You can configure Jenkins to allow that each project will select the installation that will use.
This plugin works as other builders like Ant builder or Gant builder. You just need to specify the Rake tasks to run but you can also configure other Rake options.
Since version 1.7 the Rake plugin also detects the machine's Rvm installation and collects its Ruby instances to use them as normal instances:
If your Rvm installation is not in the default directory, $HOME/.rvm, the path can be modified into the Jenkins' system configuration panel:
- Minor feature: Reload the gemsets where rake is not found. Thanks to Brian Fletcher (@punkle) for pull request #15.
- Minor improvement: Order list of rake installations for the dropdown. Thanks to Brian Fletcher (@punkle) for pull request #16.
- Minor feature: Add option to use bundle exec. Thanks to Scott Nelson (@sanelson2000) for pull request #17.
- Work around JRE bug that prevents the default rake installation from being used on Windows (JENKINS-18822)
- Ensure we search global gemsets for the rake gem, and update path accordingly
- Make sure the global path is added in addition to the gemset path
- Ensure we include the Ruby bin path (needed by JRuby)
- Add rvm bin path to the environment path
- Add initial path to the environment
- Fix gems bin parent directory
- Rake Plugin does not properly discover available gemsets. (issue GH-1)
- Rake plugin can't always find Rake with rvm installed. (JENKINS-7947)
- Rake plugin fails when job configured to use (Default) Rake installation. (JENKINS-7530)
- Autodetect Rvm installation and its Ruby instances. #rvm
- Maintenance release, fixing JENKINS-5110 and JENKINS-6194.
- Custom root directory added
- Bug fixed: when you added several build tasks they copied data from the first one.
- Some bugs fixed
- Rake version selector moved to a separated template in order to use it in dependent plugins.
- Updated to keep up with changes in Hudson core 1.250 (report)