Navigate to the task configuration for the job (this will be the default job if creating a new plan).
Click the name of the desired Grails task, or click Add Task and then Grails if creating a new task.
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'.
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.
If required, specify environment variables and working directory settings:
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>.
For jobs that use CVS, the root directory is 