When you configure a plan, you need to specify which builder should be used for the plan's builds. If you specify a Grails builder, you will also need to choose a JDK.
(info) Bamboo supports Grails versions 1.2.x and 1.3.x.

To configure a Maven builder for a plan,

(info) If you are creating a new plan, start at step 5.

  1. Click 'Home' to go to the Dashboard.
  2. Click the 'All Plans' tab.
  3. Locate the plan in the list and click this icon:
  4. The 'Configuration' tab will be displayed. Click the 'Builder' sub-tab.
  5. The 'Builder' sub-tab will be displayed.
  6. In the 'Builder' field, select the Grails builder that you wish to configure for this plan (e.g. "Grails"). The builder that you select will become one of the plan's capability requirements. For details please see Specifying a Plan's Capability Requirements.
    (tick) Tip: If you want to configure a new shared local builder capability in Bamboo, you can do so by clicking the 'Add New Builder' link and entering the builder details in the window that displays. Once you have added the new builder, it will be available for you to select from the 'Builder' dropdown.
  7. The screen will refresh to display the builder settings specific to Grails:
    • 'Grails Commands' — Specify the Grails command that you want Bamboo to execute each time the source code changes. For example:
      clean
      test-app
      
      (this will run the Grails command 'clean' followed by the Grails command 'test-app'). You can also use '-D' to define one or more JVM parameters, e.g.: -Djava.awt.headless=true (this will pass the parameter 'java.awt.headless' with a value of 'true') and include variables (see Using Global 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.

      (tick) Tip: Please refer to the Grails Command Line Reference documentation for more details on Grails commands that can be entered into this text box.
    • 'Build JDK' — Choose a JDK from the list. The JDK that you select will become one of the plan's capability requirements. For details please see Specifying a Plan's Capability Requirements.
      (tick) Tip: If you want to configure a new shared local JDK capability in Bamboo, you can do so by clicking the 'Add New JDK' link and entering the JDK details in the window that displays. Once you have added the new JDK, it will be available for you to select from the 'JDK' dropdown.

      You can then specify these generic JDK capabilities as requirements for your plan.

  8. Update the system environment variables, working directory, project file and plan dependencies setting. These are optional settings:
  9. Specifying a Plan's Capability Requirements