Run/Debug Configuration: CloudBees Server

Name field and Share option

Item	Description
Name	Use this field to edit the name of the run/debug configuration. This field is not available when editing the run/debug configuration defaults.
Share	Select this check box to make the run/debug configuration available to other team members. If the directory-based project format is used, the settings for a run/debug configuration are stored in a separate xml file in the .idea\runConfigurations folder if the run/debug configuration is shared and in the .idea\workspace.xml file otherwise. If the file-based format is used, the settings are stored in the .ipr file for shared configurations or in the .iws file for the ones that are not shared. This check box is not available when editing the run/debug configuration defaults.

Item

Description

Name

Use this field to edit the name of the run/debug configuration.

This field is not available when editing the run/debug configuration defaults.

Select this check box to make the run/debug configuration available to other team members.

If the directory-based project format is used, the settings for a run/debug configuration are stored in a separate xml file in the .idea\runConfigurations folder if the run/debug configuration is shared and in the .idea\workspace.xml file otherwise.

If the file-based format is used, the settings are stored in the .ipr file for shared configurations or in the .iws file for the ones that are not shared.

This check box is not available when editing the run/debug configuration defaults.

Server tab

Item	Local/Remote	Description
Application server	Remote	Select the server configuration to be used. Click Configure to create a new server configuration or edit an existing one. (The Application Servers dialog will open.) For local CloudBees run/debug configurations, the server configuration is not specified; the Tomcat instance embedded in CloudBees is used. This Tomcat instance is included in CloudBees client libraries which IntelliJ IDEA can download for you.
Start browser	Both	Select this check box to run the default Web browser to study your application output there.
With JavaScript debugger	Both	If this check box is selected, the Web browser is started with the JavaScript debugger enabled. Note JavaScript debugging is available only for Firefox and Google Chrome. Note that when you debug your JavaScript in Firefox for the first time, the JetBrains Firefox extension will be installed.
Startup page	Both	In this field, specify the URL the browser should go to when started. In most typical cases, this URL will correspond to the root of your Web application or its starting page.
VM options	Local	If necessary, specify the command-line options to be passed to the server JVM at the server start. If you need more room to type, click next to the field to open the VM Options dialog where the text entry area is larger. When specifying the options, follow these rules: Use spaces to separate individual options, for example, -client -ea -Xmx1024m. If an option includes spaces, enclose the spaces or the argument that contains the spaces in double quotes, for example, some" "arg or "some arg". If an option includes double quotes (e.g. as part of the argument), escape the double quotes by means of the backslashes, for example, -Dmy.prop=\"quoted_value\".
On 'Update' action	Both	Select the necessary option for the Update application action. Hot swap classes. Changed classes will be recompiled and reloaded at runtime. Note that this option will work only in the debug mode. Redeploy. The overall application will be rebuilt and redeployed. Restart server. The server will be restarted. The application will be rebuilt and deployed at the server startup. (This option is not available for remote run configurations.)
Show dialog	Both	Select this check box if you want to see the Update <application name> dialog every time you perform the Update application action. The Update <application name> dialog is used to view and change the current update option prior to actually updating the application.
On frame deactivation	Both	Specify which application update actions should be performed when switching from IntelliJ IDEA to a different application (for example, a Web browser). (Frame deactivation means switching to a different application.) If no update actions are required, select Do nothing. Otherwise, select the necessary update option. Note that the Redeploy an the Restart server options are not available.
HTTP port	Local	Specify the HTTP port of CloudBees.
JNDI port	Local	Specify the port to be used for exchanging the JNDI information with the server.
Remote connection settings	Remote	The settings for accessing deployed applications. For CloudBees, you don't need to specify any of these settings.
Host	Remote	For CloudBees, IntelliJ IDEA ignores this setting.
Port	Remote	For CloudBees, IntelliJ IDEA ignores this setting.

Deployment tab

Use this tab to specify which artifacts and/or external resources should be deployed onto the server. (An external resource means a deployable Web component such as a .war file which is not represented by a project artifact. Usually, such components are stored outside of the project scope.)

To add items to the deployment list (shown under Deploy at the server startup), use add . For more information, see the table below.

Item	Tooltip and Shortcut	Description
	Add Alt+InsertCommand N; Command Enter	Use this icon or shortcut to add an artifact or an external resource to the list. To add an artifact, select Artifact and choose the desired artifact in the dialog that opens. To add an external resource, select External Source and choose the location of the desired resource in the dialog that opens.
	Remove Alt+DeleteCommand Delete	Use this icon or shortcut to remove the selected artifacts and external resources from the list.
	Edit Artifact F4F4	Use this icon or shortcut to configure the selected artifact. (The Artifacts page of the Project Structure dialog will open.)

Logs tab

Use this tab to specify which log files generated while running or debugging should be displayed in the console, that is, on the dedicated tabs of the Run or Debug tool window.

Item	Description
Is Active	Select check boxes in this column to have the log entries displayed in the corresponding tabs in the Run tool window or Debug tool window.
Log File Entry	The read-only fields in this column list the log files to show. The list can contain: Full paths to specific files. Ant patterns that define the range of files to be displayed. Aliases to substitute for full paths or patterns. These aliases are also displayed in the headers of the tabs where the corresponding log files are shown. Note If a log entry pattern defines more than one file, the tab header shows the name of the file instead of the log entry alias.
Skip Content	Select this check box to have the previous content of the selected log skipped.
Save console output to file	Select this check box to save the console output to the specified location. Type the path manually, or click the browse button and point to the desired location in the dialog that opens.
Show console when standard out changes	Select this check box to activate output console and bring it forward, if associated process writes to Standard.out.
Show console when standard error changes	Select this check box to activate output console and bring it forward, if associated process writes to Standard.err.
	Click this button to open the Edit Log Files Aliases dialog where you can select a new log entry and specify an alias for it.
	Click this button to edit the properties of the selected log file entry in the Edit Log Files Aliases dialog.
	Click this button to remove the selected log entry from the list.
	Click this button to edit the select log file entry. Note The button is available only when an entry is selected.

Code Coverage tab

Use this tab to configure code coverage monitoring options.

Note that this tab is not available for remote servers.

Item	Description
Choose code coverage runner	Select the desired code coverage runner.
Sampling	Select this option to measure code coverage with minimal slow-down.
Tracing	Select this option to collect accurate branch coverage. This mode is available for the IntelliJ IDEA code coverage runner only.
Track per test coverage	Select this check box to detect lines covered by one test and all tests covering line.
Packages and classes to record code coverage data	If necessary, specify the classes and packages to be measured. Use or to add classes or packages to the list. To remove the classes or packages from the list, select the corresponding list items and click .
Enable coverage in test folders.	Select this check box to include the test source folders in code coverage analysis.

Startup/Connection tab

This tab, usually, contains recommendations for starting a remote server. For CloudBees, there are no particular recommendations.

This tab is available only for remote run configurations.

Before Launch options

Item	Description
Before Launch	Specify which activities should be performed before starting the run/debug configuration: Make. If this check box is selected, the project is compiled automatically prior to running or debugging. This option helps you ensure that all changes are included and compiled. Build Artifacts. If this check box is selected, the specified artifacts will be built prior to running or debugging. To define the artifacts to be built, click and select the desired artifacts. Run Ant target. If this check box is selected, the specified Ant target will be built prior to running or debugging. To define the Ant target, click and select the desired target. To learn more about Ant support, refer to the Ant Support section. Run Maven goal. If this check box is selected, the specified Maven goal will be executed prior to running or debugging. To define the Maven goal to be executed, click and select the desired goal. To learn more about Maven support, refer to the Maven Support section. Show this page. Select this check box if you want the Run/Debug Configurations dialog to be shown every time you launch this run/debug configuration. Note The Before Launch actions are performed in the order they appear in the Run/Debug Configurations dialog.

Item

Description

Before Launch

Specify which activities should be performed before starting the run/debug configuration:

Make. If this check box is selected, the project is compiled automatically prior to running or debugging. This option helps you ensure that all changes are included and compiled.
Build Artifacts. If this check box is selected, the specified artifacts will be built prior to running or debugging. To define the artifacts to be built, click and select the desired artifacts.
Run Ant target. If this check box is selected, the specified Ant target will be built prior to running or debugging. To define the Ant target, click and select the desired target.
To learn more about Ant support, refer to the Ant Support section.
Run Maven goal. If this check box is selected, the specified Maven goal will be executed prior to running or debugging. To define the Maven goal to be executed, click and select the desired goal.
To learn more about Maven support, refer to the Maven Support section.
Show this page. Select this check box if you want the Run/Debug Configurations dialog to be shown every time you launch this run/debug configuration.

Note

The Before Launch actions are performed in the order they appear in the Run/Debug Configurations dialog.

Toolbar

Item	Description
(InsertInsert)	Use this icon or shortcut to create a new run/debug configuration.
(DeleteDelete)	Use this icon or shortcut to delete the selected run/debug configuration.
(Ctrl+DCtrl+D)	Use this icon or shortcut to create a copy of the selected run/debug configuration.
	Click this button to edit the default settings for run/debug configurations.
	Use these buttons to move the selected run/debug configuration up and down in the list. The order of configurations in the list defines the order in which the configurations appear in the corresponding list on the main toolbar.

IntelliJ IDEA 12.1.0 Web Help