Plugin Information

This plugin allows Hudson to invoke Gradle build script as the main build step.

The plugin works much like Gant or Ant builder, and using it is very easy. You basically just need to specify the Gradle switches, tasks and optionally build script that you want to run:

If 'gradle' is not in PATH, or if you have multiple Gradle installations and need to be able to configure which project uses which Gradle, then you can go to the system configuration and tell Hudson where your Gradle are:

Roadmap

March 2010 (in progress)

• Use the Gradle API for accessing all the Gradle functionality
• Provide a Maven-like integration
  • Multi-projects detection
  • Adding the automatic detection paths of the tests result
  • Listing the executed tasks with time execution for each task
  • Providing a log for each module in a multi project

Changelog

Release 1.3 (in trunk)

• Added a description message in the build step
• The plugin makes its possible to extract a Gradle distribution from a shared location or from a command line, and uses this
  distribution for running the build.

Release 1.2 (February 07, 2009)

• Added a distinction between switches and tasks
• The plugin makes its possible to specify the location of the build script if the workspace has a top-level build.gradle in somewhere other than the module root directory
• Improved user help messages

Release 1.1 (November 07, 2008)

• Added the support of Gradle 0.5
  Before the version 0.5, the gradle windows executable file is "gradle.exe" and you lost the ERRORLEVEL value.
  From Gradle 0.5, the window launcher is a .bat file that conserves the correct ERRORLEVEL value.

Release 1.0 (October 04, 2008)

• Initial release