This page describes how to configure a Bamboo Grails task.
Bamboo supports Grails versions 1.2.x, 1.3.x, and 2.x.
To configure a Grails task:
- Navigate to the Tasks configuration tab for the job (this will be the default job if creating a new plan).
- Select the name of an existing Grails task, or select Add task > Grails to create a new task.
Complete the following settings:
A description of the task, which is displayed in Bamboo.
Disable this task
Check, or clear, to selectively run this task.
Add condition to task
Make task run only when a certain condition is met.
You can find conditions on Atlassian Marketplace or implement your own.
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.
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=truewill pass the parameter 'java.awt.headless' with a value of 'true'.
- You can include variables (see Bamboo variables).
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.
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").
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.
The build will produce test results
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 customized 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
- You can use
- Select Save.
Was this helpful?Yes Provide feedback about this article