All CloudBees Assurance Program (CAP) Tier 1 and Tier 2 plugins are compatible with CasC at this time; however, they are not all configurable. Refer to Tier 1 and Tier 2 plugins support for Configuration as Code for a list of configurable plugins.
For more information on the CloudBees Assurance Program (CAP) and how CloudBees classifies plugins, refer to CloudBees plugin support policies.
Plugin catalog limitations in CasC
|
Plugin catalogs can be used in controller Configuration as Code bundles through the |
The plugin catalog feature can be also used separately (non CasC) on controllers as described in the documentation. However, when using it inside a Configuration as Code bundle there are the following limitations:
-
Credentials: The use of Jenkins credentials (under the
httpCredentialsProvidersection) requires a running Jenkins instance; however, Configuration as Code is designed to run during Jenkins start up, so Jenkins credentials are not available. -
Layouts: As long as credentials are not supported in the
plugin-catalog.yamlfile, layouts that download the plugins are also not supported; for example, layouts like Nexus 2, Nexus 3, or Artifactory.
Refer to for more information.