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 and CloudBees Jenkins Support

The Jenkins Configuration as Code Plugin is provided as a Technical Preview within CloudBees Jenkins Distribution and CloudBees Jenkins Support. Please refer to this page for more information about the current status and limitations of Jenkins Configuration as Code.

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.

Current state of support in other Jenkins-based CloudBees products

As of August 2019:

  • CloudBees Jenkins Operations Center: Jenkins Configuration as Code is not fully supported.
  • CloudBees Jenkins X Distribution: Jenkins Configuration as Code is not fully supported.
  • CloudBees Jenkins X Support: Jenkins Configuration as Code is not fully supported.

Additional information

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.