ページ履歴

Configuring a Grails Builder for a Job

...

1. Navigate to the Job's configuration pages, as described on Editing a Job.
   

   アンカー
   builderconfig builderconfig

2. In the 'Builder' dropdown, select the Grails builder that you wish to configure for this Job (e.g. "Grails"). The builder that you select will become one of the Job's capability requirements. For details please see Configuring a Job's Requirements.
   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.
3. 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:

     No Format
     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, No Format 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.

     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 Job's capability requirements. For details please see Configuring a Job's Requirements.
     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.

     情報
     title Specifying Generic JDK Requirements
     Excerpt Include nopanel Configuring an Agent-specific JDK Capability true Configuring an Agent-specific JDK Capability nopanel true You can then specify these generic JDK capabilities as requirements for your Job.

     アンカー
     workingsubdirectory workingsubdirectory

4. If required, update the system environment variables and working directory settings:

   インクルード ページ
   _planBuilderConfig _planBuilderConfig nopanel true

5. インクルード ページ
   _planBuilderConfigplanBuilderCommonOptions
   インクルード ページ
   _planBuilderCommonOptions nopanel true

6. インクルード ページ
   _planBuilderCommonOptionscreateNewPlanOrJobQuestionForBuilders
   インクルード ページ
   _createNewPlanOrJobQuestionForBuilders nopanel true

   include

   インクルード ページ
   _createNewPlanOrJobQuestionForBuilders
   planBuilderCommonOptions2 _planBuilderCommonOptions2 nopanel true

7. include

   インクルード ページ
   _planBuilderCommonOptions2
   planFooterActions _planFooterActions nopanel true_planFooterActions

注意

関連トピック

Specifying a Builder
Editing a Job