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 CI (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 CI (Core)?
Environment
-
CloudBees CI (CloudBees Core) on modern cloud platforms - Managed controller
-
CloudBees CI (CloudBees Core) on modern cloud platforms - Operations Center
-
CloudBees CI (CloudBees Core) on traditional platforms - Client controller
-
CloudBees CI (CloudBees Core) on traditional platforms - Operations Center
State of Support
Starting in version 2.222.4.3, CloudBees CI and CloudBees Jenkins Platform support using Jenkins Configuration as Code via Configuration as Code (CasC) for controllers. CloudBees will support the features of Jenkins Configuration as Code when it is used as a part of implementing Configuration as Code (CasC) for controllers.
Use of Jenkins Configuration as Code outside of this feature will receive support limited to commercially reasonable efforts, meaning that support requests may be closed without resolution. CloudBees will not be able to escalate or fix bugs that are not encountered when using Configuration as Code (CasC) for controllers.
Additional information
-
Configuration as Code for CloudBees CI (Core) on modern cloud platforms
-
Configuration as Code for CloudBees CI (Core) on traditional platforms
-
CloudBees Blog: "Jenkins Configuration as Code: Look Ma, No Hands"
-
CloudBees Blog: "Jenkins Configuration as Code: Sensitive Data"
-
Demonstration examples of Jenkins Configuration as Code on GitHub