Environment
-
CloudBees CI (CloudBees Core) on modern cloud platforms - Managed controller (CORE-MM)
-
CloudBees CI (CloudBees Core) on modern cloud platforms - Operations Center (CORE-CLOUD-OC)
-
CloudBees CI (CloudBees Core) on traditional platforms - Client controller (CORE-CM)
-
CloudBees CI (CloudBees Core) on traditional platforms - Operations Center (CORE-OC)
-
CloudBees Jenkins Enterprise - Managed controller (CJE-MM)
-
CloudBees Jenkins Enterprise - Operations Center (CJE-OC)
Resolution
CJOC is not a HTTPS/SSL/TLS endpoint
CJOC does not initiate the connection to the controller, so it doesn’t care if the controller is on HTTPS or HTTP.
CJOC is a HTTPS/SSL/TLS endpoint
The Client controller initiates the connection to CJOC. In order for the Client controller to discover the agent port that CJOC is listening on you need to give the controller the TLS cert of CJOC.
You can manually add the certificates to the controller’s trust store following the documentation.
CloudBees Core on modern cloud platforms or CloudBees Jenkins Enterprise 2.x
Deploy Self Signed Certificates in controllers and Agents Deploy Self Signed Certificates in controllers and Agents (Custom Location)
CloudBees Core on traditional platforms or CloudBees Jenkins Platform:
CloudBees Jenkins Enterprise 1.x