Run/Debug Configuration: CloudBees Server
- Name field and Share option
- Server tab
- Deployment tab
- Logs tab
- Code Coverage tab
- Startup/Connection tab
- Before Launch options
Name field and Share option
|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
If the file-based format is used,
the settings are stored in the
This check box is not available when editing the run/debug configuration defaults.
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.|
|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:
|On 'Update' action||Both||
Select the necessary option for the Update application action.
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.|
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 . For more information, see the table below.
|Item||Tooltip and Shortcut||Description|
Use this icon or shortcut to add an artifact or an external resource to the list.
|Use this icon or shortcut to remove the selected artifacts and external resources from the list.|
|Use this icon or shortcut to configure the selected artifact. (The Artifacts page of the Project Structure dialog will open.)|
|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:
|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. 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.
|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.|
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
Specify which tasks should be carried out before starting the run/debug configuration. The specified tasks are performed in the order that they appear in the list.
Click this icon to add a task to the list. Select the task to be added:
|Alt+Delete||Click this icon to remove the selected task from the list.|
|Enter||Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.|
|Alt+Up/Alt+Down||Click these icons to move the selected task one line up or down in the list.|
|Show this page||Select this check box to show the run/debug configuration settings prior to actually starting the run/debug configuration.|
|Alt+Insert||Use this icon or shortcut to create a new run/debug configuration.|
|Alt+Delete||Use this icon or shortcut to delete the selected run/debug configuration.|
|Ctrl+D||Use this icon or shortcut to create a copy of the selected run/debug configuration.|
|Click this button to edit the default settings of the selected run/debug configuration. This button it disabled for defaults.|
|Alt+Up/Alt+Down||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.
These buttons are disabled for defaults.
You can group run/debug configurations by placing them into folders.
To create a folder, select the configurations to be grouped and click . Specify the name of the folder.
Then, to move a configuration into a folder, between the folders or out of a folder, use and . You can also drag a configuration into a folder.
To remove grouping, select a folder and click .