State of Jenkins Configuration as Code (JCasC) support in CloudBees products

Issue

This article covers the support of the Jenkins Configuration as Code plugin (JCasC) in CloudBees products.

  • Can I use the Jenkins Configuration as Code plugin in CloudBees Core?
  • Can I use the Jenkins Configuration as Code plugin in CloudBees Jenkins Distribution?
  • What can I configure using the Jenkins Configuration as Code plugin in CloudBees Core?

Environment

State of Support

As of August 2019, the Jenkins Configuration as Code Plugin is supported as a Technical Preview within certain CloudBees products.

What is a Technical Preview and what does that mean for support?

A plugin that is made available as a Technical Preview has the following characteristics:

  • The plugin has not undergone end-to-end testing with CloudBees products.
  • The plugin is not bundled into the products, but it can be installed from the CloudBees update center.
  • CloudBees will process support requests related to the Jenkins Configuration as Code plugin.
  • CloudBees will process support requests related to plugin compatibility with JCasC plugin.
  • Resolution of reported issues is subject to CloudBees internal priorities.

Current state of support in CloudBees Jenkins Distribution

The Jenkins Configuration as Code Plugin is provided as a Technical Preview within CloudBees Jenkins Distribution.
Please refer to this page for more information about the current status and limitations of Jenkins Configuration as Code.
The referenced page also provides quick start guidelines and public demos which can be used.

The provided materials apply to CloudBees Jenkins Support customers and to freemium users of CloudBees Jenkins Distribution.

Current state of support in CloudBees Jenkins Support

The Jenkins Configuration as Code Plugin is provided as a Technical Preview within CloudBees Jenkins Support.
Starting from the September releases of CloudBees Products and from Jenkins LTS 2.176.3, CloudBees plans to certify the plugin as Tier 2 (Compatible) so that common issue and request for enhancement processes apply to users of the plugin.
See the CloudBees plugin support policies for more information.

If you use CloudBees Jenkins Distribution, please refer to the section above.
If you use Jenkins LTS, please see the Jenkins Configuration as Code community documentation to get more information about the plugin.

Also see this documentation page for more information.

Current state of support in CloudBees Core

As of August 2019, the Jenkins Configuration as Code Plugin is not fully supported in the CloudBees Core, CloudBees Jenkins Enterprise or CloudBees Jenkins Platform products.

Specific issues with the Jenkins Configuration as Code Plugin within CloudBees Core include:

  • Enabling the Jenkins Configuration as Code Plugin on Core instances may lead to system instability, because CloudBees products have not been fully tested against the Configuration as Code Plugin.
  • Although it is technically possible to use the Jenkins Configuration as Code Plugin with Team, Client or Managed Masters in the CloudBees Core environment, you will not be able to configure:
    • CloudBees proprietary plugins, including those delivered through CAP. The plugin manager will override configuration properties set by the Jenkins Configuration as Code plugin.
      • CloudBees-specific configurations in masters or CloudBees Operation Center.
      • Any community/open source plugins that do not support or are not compatible with the Jenkins Configuration as Code Plugin.
      • Any plugins with limited or poorly-implemented support for Jenkins Configuration as Code.
  • Some configuration changes made by the Jenkins Configuration as Code Plugin on a master may be overwritten by values from CloudBees Operations Center.

For more information about the current state, please refer to the following documentation pages:

Current state of support in other Jenkins-based CloudBees products

Please refer to the following materials:

Additional information

Have more questions?

1 Comments

  • 1
    Avatar
    Jesse Fair

    The opensource Jenkins helm chart enables JCasC auto reloading via a sidecar that listens to ConfigMap changes and reloads the corresponding JCasC yaml files that the Jenkins pod has mounted. It also triggers a webhook to tell Jenkins to reload the JCasC configuration. Is there plans to provide this same capability with Cloudbees-Core? If you guys are working on supporting this is there by chance anything to share yet?

Please sign in to leave a comment.