Grails

This page describes how to configure a Bamboo task that uses a Grails executable.

Bamboo supports Grails versions 1.2.x, 1.3.x, and 2.x.

To configure a Grails task:

1. Navigate to the Tasks configuration tab for the job (this will be the default job if creating a new plan).
2. Click the name of the desired Grails task, or click Add Task and then Grails if creating a new task.

3. Complete the following settings:

   Grails configuration
   Task Description	A description of the task, which is displayed in Bamboo.
   Executable	The Grails executable that is available to perform the task. The executable that you select will become one of the task's (and so, the job's) requirements. You can add other executables, if required.
   Grails Commands	The Grails commands that you want Bamboo to execute. See the Grails Command Line Reference documentation for more details on Grails commands. You can use '-D' to define one or more JVM parameters, e.g.: -Djava.awt.headless=true will pass the parameter 'java.awt.headless' with a value of 'true'. You can include variables (see Using global, plan or build-specific variables).
   Build JDK	The JDKs that are available to perform the task. The JDK that you select will become one of the task's (and so, the job's) requirements. You can add other JDKs, if required.

4. If required, specify environment variables and working directory settings:

   Environment Variables

   (Optional)  Additional system environment variables that you want to pass to your build. Note that existing environment variables are automatically available to the executable. You can also include Bamboo global or build-specific variables (see Using global, plan or build-specific variables). Multiple variables should be separated with spaces. Parameters with spaces must be quoted (e.g ANT_OPTS="-Xms200m -Xmx700m").

   Working Sub Directory

   (Optional)  An alternative subdirectory, relative to the job's root directory, where Bamboo will run the executable. The root directory contains everything checked out from the job's configured source repository. If you leave this field blank, Bamboo will look for build files in the root directory. This option is useful if your task has a build script in a subdirectory and the executable needs to be run from within that subdirectory.

5. If applicable, select The build will produce test results and choose one of the following:

   Look in the standard test results directory	Bamboo looks in the standard directory for the test results. Use this unless you've customised your test runner to output the results to a different location.
   Specify custom results directories	Specify the custom directory, relative to the root directory, where test results will be created. You can use Ant-style patterns such as **/test-reports/*.xml. Bamboo requires test results to be in JUnit XML format. For jobs that use CVS, the root directory is <bamboo-home>/xml-data/build-dir/JOB_KEY/<cvs-module>.

6. Click Save.