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 Preview within certain CloudBees products.

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

For more information on CloudBees Previews see the definition in the Lexicon.

Current state of support in Jenkins-based CloudBees products

Please refer to the following materials:

Additional information

Was this article helpful?
0 out of 0 found this helpful

Have more questions?

2 Comments

Date Votes
  • 2
    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?

  • 0
    Avatar
    Karen Taggart

    Jesse - Apologies for delay in responding to your comment here. It's a great use case you raise. I am going to go ahead and add it as an RFE to our Feedback system so that we have it in our backlog as we plan the next iterations. I will likely be in touch directly to get additional feedback from you. Thanks again! Please don't hesitate to contact me directly if you want to discuss further - ktaggart@cloudbees, Product Owner, CBCI

Please sign in to leave a comment.