This page describes how to configure a Grails executable for a Task. On this page:

Configuring a Grails Executable for a Task

Before you begin:

• Bamboo supports Grails versions 1.2.x and 1.3.x.

To configure a Grails executable for a Task:

1. Navigate to the Task configuration 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. In the 'Executable' dropdown, select the Grails executable that you wish to configure for this Task (e.g. "Grails"). The executable that you select will become one of the Task's capability requirements (and hence, one of the Job's requirements). For details, please see Configuring a Job's Requirements.
4. The screen will refresh to display the settings specific to Grails:
   • 'Grails Commands' — Specify the Grails command that you want Bamboo to execute each time the source code changes. For example, the following example will run the Grails command 'clean' followed by the Grails command 'test-app':

     clean test-app

   • 'Build JDK' — Choose a JDK from the list. The JDK that you select will become one of the Task's capability requirements (and hence, one of the Job's requirements). For details, please see Configuring a Job's Requirements.
     
5. If required, update the system environment variables and working directory settings:
6. 
7. 

Notes

• About Grails Commands — Please refer to the Grails Command Line Reference documentation for more details on Grails commands. In particular, note the following:
  • 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).
  • Please be aware that unlike Ant or Maven, Grails generally does not permit the execution of a series of commands on the same line. Therefore, each Grails command should be entered on a new line in the 'Grails Commands' text box. For example, the following Grails commands,

    clean set-version ${bamboo.buildKey} test-app war

    will set the version of your Grails application to that of your Bamboo build key value, run unit tests within the Grails application and then create a JEE Web Application Archive (WAR) file from the Grails application.
• Specifying Generic JDK Requirements — You can specify generic JDK capabilities as requirements for your Task. You will need to configure a generic JDK capability first:

Related Topics

Configuring Tasks
Editing a Job
Configuring an Agent-specific JDK Capability