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:
-
Navigate to
. -
Select Add plugin configuration to create a new configuration.
-
In the New Configuration window, specify a Name for the configuration.
-
Select the Project that the configuration belongs to.
-
Optionally, add a Description for the configuration.
-
Select the appropriate Plugin for the configuration.
-
Configure the plugin configuration parameters.
-
Select OK.
Depending on your plugin configuration and how you run procedures, the Differences in plugin UI behavior. field may behave differently in the CloudBees CD/RO UI. For more information, refer to |
GitHub-Checks plugin configuration parameters
Parameter | Description | ||
---|---|---|---|
Name |
Required. The unique name for the configuration. |
||
Description |
The configuration description. |
||
REST API endpoint |
GitHub endpoint to connect to. By default, |
||
GitHub App ID |
Required. Provide your GitHub App ID.
|
||
GitHub private key |
Required. Private key in
|
||
Ignore SSL issues |
Turns SSL verification off for instances with self-signed certificates. |
||
HTTP proxy |
A proxy server URL that should be used for connections. |
||
Proxy authorization |
The username and password for the proxy. |
||
Debug level |
This option sets the debug level for logs. If Info is selected, only a summary is displayed. If Debug is selected, debug information is displayed. If Trace is selected, all requests and responses are displayed. |