Continuous Delivery architecture

Continuous Delivery communicates with your PE installation, your source control system, the servers you've designated as job hardware, and the browser you use to connect to the web UI.

This diagram shows the architecture and port requirements for a Continuous Delivery 5.x installation.

Continuous Delivery uses TCP (Transmission Control Protocol) connections.

Diagram of  port requirements and
                    architecture.

Port Use
* (variable) On this port, Continuous Delivery makes API requests to, and clones from, source control over HTTPS or SSH. The specific port number depends on your source control integration.
22 The default SSH port Bolt uses to connect to the Continuous Delivery node. Configurable in Bolt.
443 On this port, Continuous Delivery job hardware servers communicate with the Continuous Delivery application, and users access the Continuous Delivery application's web UI over HTTPS.
4433 The Continuous Delivery application uses this PE port to communicate with the node classifier and the PE console (for authentication).
8000 The port where the source control provider webhooks send traffic to Continuous Delivery.
8081 The Continuous Delivery application uses this PE port to send queries to PuppetDB.
8140 The Continuous Delivery application and Continuous Delivery job hardware servers use this PE port to communicate with Puppet Server.
8142 Continuous Delivery job hardware servers and PE communicate through Puppet Agent on this port.
8143 The Continuous Delivery application uses this PE port to communicate with Puppet Orchestrator.
8170 The Continuous Delivery application uses this PE port to communicate with Code Manager.

You can configure ports 4433, 8081, 8140, 8143, and 8170 in the PE integration settings.

For more information about PE ports, refer to PE documentation, such as the PE Firewall configuration diagrams.