Determining plugin compatibility using CasC

1 minute readScalabilityAutomation

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 Configuration as Code (CasC) for Controllers bundles through the plugin-catalog.yaml file inside the bundle.

The plugin catalog feature can be also used separately (non CasC) on CloudBees CI controllers as described in the documentation. However, when using it inside a Configuration as Code (CasC) for Controllers bundle there are the following limitations:

  • Credentials: The use of Jenkins credentials (under the httpCredentialsProvider section) requires a running Jenkins instance; however, Configuration as Code (CasC) for Controllers is designed to run during Jenkins start up, so Jenkins credentials are not available.

  • Maven 2 layout: This layout is not supported when using Plugin Catalogs in a Configuration as Code (CasC) for Controllers bundle.