Create JBoss plugin configurations

2 minute readExtensibilityDeveloper productivity

Plugin configurations are sets of parameters that can be applied across some, or all, plugin procedures. They can reduce the repetition of common values, create predefined parameter sets, and securely store credentials. Each configuration is given a unique name that is entered in the designated parameter for the plugin procedures that use them. The following steps illustrate how to create a plugin configuration that can be used by one or more plugin procedures.

To create a plugin configuration:

  1. Navigate to DevOps Essentials  Plugin Management  Plugin configurations.

  2. Select Add plugin configuration to create a new configuration.

  3. In the New Configuration window, specify a Name for the configuration.

  4. Select the Project that the configuration belongs to.

  5. Optionally, add a Description for the configuration.

  6. Select the appropriate Plugin for the configuration.

  7. Configure the plugin configuration parameters.

  8. Select OK.

Depending on your plugin configuration and how you run procedures, the Input parameters  Configuration name field may behave differently in the CloudBees CD/RO UI. For more information, refer to Differences in plugin UI behavior.

JBoss plugin configuration parameters

Table 1. EC-JBoss plugin configuration parameters
Parameter Description


Required. The unique name for the configuration.


The configuration description.

Login as

Select the credential option and then specify the following:

  • Runtime credential: Enter the username and password, and then re-enter the password.

  • Credential reference: Select the project that contains the credential, and then select the credential you wish to use.

Additional Java options

Additional Java options.

JBoss controller location

Required. Address of the JBoss controller that is used to connect. Examples:


  • jboss:9990

  • remote+

Log Level

Log level to use for logging output. Supported values are INFO, WARNING, ERROR and DEBUG.

Physical location of the JBoss client script

Physical location of the JBoss CLI script. For example, jboss-cli.bat or /path/to/ If omitted, the script location from the configuration is used.

Check connection resource

Resource used for testing the connection.