Introduction
Introduction
IntroductionInstall CloudBees CD/RO within KubernetesConfigure Helm chartsKubernetes platform-specific configurationsKubernetes configuration optionsScale build resources manually using a procedureConfigure IP protocols for Helm chart componentsConfigure GitOps with Helm chartsVerify Helm chartsCreate custom Docker imagesVerify Docker images
IntroductionInstallation user requirementsInstallation typesDefault installation directoriesVerify installation binariesAgent security recommendations
IntroductionInstall a default configurationInstall a custom configurationInstall an express agent (full installer)Install an express agent (agent-only installer)Install an advanced agent (agent installer)Install CloudBees Analytics
IntroductionInstall a default configurationInstall a custom configurationInstall an express agent (full installer)Express agent command-line installation (agent-only installer)Advanced command-line installation (agent-only installer)Install CloudBees Analytics
IntroductionRun a silent installationSilent installation argumentsLinux silent installation examplesWindows silent installation examplesCloudBees Analytics server unattended installation
IntroductionUNIX agent interactive command-line installationSilent installation method for UNIX or macOS agents
IntroductionPrerequisitesPermissions to install or upgrade remote agentsInstall remote agents using the web interfaceInstall via the API
CloudBees Tools installation
Move the artifact repository in LinuxMove the artifact repository in Windows
Connect CloudBees CD/RO to a Microsoft SQL server
Install the MySQL JDBC connector
IntroductionUninstall CloudBees CD/RO on Linux, Unix, or macOSUninstall on WindowUninstall the CloudBees Analytics server on LinuxUninstall the CloudBees Analytics server on Windows
Upgrade CloudBees CD/RO on KubernetesConfiguration settings preserved after a Kubernetes upgrade
Upgrade Kubernetes CloudBees Analytics environments to OpenSearchMigrate CloudBees Analytics data from Elasticsearch to OpenSearch
IntroductionUpgrade a non-clustered environmentUpgrade a clustered environmentUI upgrade methodInteractive command-line upgrade methodRun a silent upgradeCopy repository contentsUpgrade remote agentsUpgrade the CloudBees Analytics serverConfiguration settings preserved after a traditional upgrade
Upgrade traditional CloudBees Analytics environments to OpenSearchMigrate CloudBees Analytics data from Elasticsearch to OpenSearch
IntroductionZones and gatewaysConfigure custom CAs and CRLs in non-clustered environmentsConfigure custom CAs and CRLs in clustered environmentsConfigure agent environment variablesLicensesCreate and manage usersEdit user settingsCreate and manage groupsPersonasConfigure an external databaseConfigure CloudBees CD/RO to use an alternate databaseInstall services for non-root/non-sudo Linux installationsConfigure autostart for non-root/non-sudo Linux installationsConfigure universal access to the plugins directoryConfigure an environment proxy serverSystem health monitoringIncrease file descriptors on Linux and Linux Docker containersAdjust swappiness on LinuxSet variables on Windows agent machinesServer propertiesServer settingsSource code synchronization
IntroductionConfigure initial events for Workload InsightsConfigure OpenSearch Dashboards to work with CloudBees Analytics
IntroductionArchitecture of a CloudBees CD/RO clusterResource, agent, and procedure considerationsSoftware for clusteringDependencies for clusteringConfigure clusteringSeparate agents from CloudBees CD/RO serversPrepare your cluster resourcesInstall and configure a load balancerInstall ZooKeeperConfigure a multi-ZooKeeper clusterInstall CloudBees CD/RO softwareConfigure repository serversConfigure machines to operate in clustered modeRun a cluster in single-server modeAdd the configuration to ZooKeeperUpload configuration files to ZooKeeperGet cluster information from ZooKeeperAdd a node to an existing clusterConfigure web server propertiesConfigure repository server propertiesConfigure CloudBees CD/RO agentsConfigure the cluster workspaceConfigure CloudBees CD/RO repositoriesAdd trusted agents to clustersVerify CloudBees CD/RO servicesAccess CloudBees CD/RO with clusteringHealth check for the CloudBees CD/RO clusterAdditional ways to improve a clusterInstall the CloudBees Analytics server in cluster modeUse self-signed certificates in CloudBees CD/RO on KubernetesConfigure Disaster Recovery and recover from a disaster
Sign in to CloudBees CD/ROAccess the Home pageMy work dashboardGuided tutorialsLearn about the object modelSearch and filter
IntroductionIntrinsic properties listed by object typeReserved words in CloudBees CD/ROObject types in CloudBees CD/ROSpecial characters in CloudBees CD/RO object namesContext-relative shortcuts to property pathsProperty error codesConfigure properties or property sheetsProperty BrowserProperty reference use case
IntroductionResource poolsCreate or edit resource pools
IntroductionView workspacesCreate or edit workspacesWorkspace file
IntroductionCreate a projectSchedules
IntroductionPipeline stages and gatesPipeline access controlPipeline tasksUse the CloudBees CD/RO API to define tasksDefine manual tasksEntry and exit gatesPipeline conditionsPipeline start and end stages and stage skippingWait dependenciesNative CI integrationPipeline UIAuthor and run pipelinesDefine stage gate rulesPipeline objects and conditionsPipeline stage summaryCredentials in pipelinesRun pipelinesView pipeline runsExample: Create a manual task in a pipelineExample: Plugin pipeline tasksExample: Integrate test automation in release pipelinesExample: Leverage test data management and service virtualization in release pipelines
IntroductionRelease planning, scheduling, and trackingRelease and environment reservations calendarVisibility and status of release pipelinesRelease definitionDeploy with Argo RolloutsRelease dashboardPlanned versus actual view for pipeline statusPath to production viewRelease summaryRun and end releases
IntroductionManage service catalogsManage service catalog itemsManage custom filters for catalogs and catalog items
IntroductionManage procedure runsProcedure run detailsUsing CloudBees CD/RO in your environmentJob step executionPostprocessors: Collecting data for reports
IntroductionWorkflow listsCreate or edit workflow definitionsWorkflow definition detailsRun workflowWorkflow detailsWorkflow LogTransition workflow
Introduction
IntroductionCreate and manage applicationsApplication process run detailsCreate application processesAdd process stepsProcess branchingConfigure plugin process stepsDefine manual stepsExample: Manual step with runtime parametersAttach credentials to processesFull-stack dependency viewApplication deployment optionsConfiguration drift
IntroductionMaster component examplesMaster components list
Introduction
IntroductionStage artifactsManage snapshotsApplication rollbackManage dependencies
IntroductionCreate environmentsDefine environment tier mapsInventory trackingEnvironment inventoryGlobal environment inventoryEnvironment reservationsLock environmentsModel dynamic environmentsAutomated environment discoveryCreate a deployment task to trigger third-party toolsGenerate a deployment packageExample: Dynamic environment with Amazon and ChefExample: Deploy and troubleshoot applicationsExample: Deploy applications with provisioned cloud resourcesExample: Implement deployment strategies
IntroductionArtifactsArtifact versionsRepositories
Create object tagsCreate object schedules
IntroductionConfigure webhook triggersConfigure polling triggers
IntroductionConfigure email notificationsSelect and edit email messages for application or microservice processes
Introduction
IntroductionInstall CloudBees CD/RO pluginsCreate plugin configurationsManage pluginsCreate pluginsManage the plugin catalog

Port usage

3 minute readReference

This section contains the default port values for CloudBees CD/RO servers and CloudBees Analytics servers, along with a list of additional ports available for use. There is also information about avoiding and resolving port conflicts.

Ensure your firewall is open for these ports. These port values apply to all Product and OS versions.

Transport Layer Security (TLS) has replaced Secure Sockets Layer version 3.0 (SSLv3) on the CloudBees CD/RO server and the CloudBees CD/RO web server.

Default server ports

CloudBees CD/RO servers use the following ports:

Port Used by

8000

CloudBees CD/RO server

8443

CloudBees CD/RO server (SSL port)

80

CloudBees CD/RO web server

7080

CloudBees CD/RO web server when installed on Linux platforms without root privileges.

443

CloudBees CD/RO web server (SSL port). You can also use this port for access to the application server API (XML-, JSON-, and REST-based).

7443

CloudBees CD/RO web server (SSL port) when installed on Linux platforms without root privileges.

6800

Port used by the CloudBees CD/RO agent for HTTP communication on the localhost network interface.

7800

CloudBees CD/RO agents (By default, this is an HTTPS port.)

61613

STOMP port used for transferring log files when using the EC-FlowLogCollector plugin, by waitForJob cb-perl API, and preflights.

8200

Artifact repository server (By default, this is an HTTPS port.)

8900

CloudBees CD/RO built-in (default) database. You can change this port number by using the ecconfigure --databasePort <port_number> option or the --databasePort installer argument.

Default CloudBees CD/RO services ports

The Java Service Wrapper uses the following ports to communicate with a Java virtual machine (JVM):

Port Used by

127.0.0.1:32000

CloudBees CD/RO agents

127.0.0.1:32001

CloudBees CD/RO server

127.0.0.1:32002

Artifact repository

Default CloudBees Analytics server ports

The CloudBees Analytics server uses the following ports:

Port Used by

9201

CloudBees Analytics server to retrieve data.

9301

Used by the CloudBees Analytics service for internal communication between nodes within the cluster.

Default CloudBees CD/RO ZooKeeper ports

The following ports are assigned to ZooKeeper in the default CloudBees CD/RO Kubernetes Helm charts:

Port Used by

53

ZooKeeper network policy

2181

CloudBees CD/RO server

2888

ZooKeeper server

3888

ZooKeeper server replicas

Additional ports

The following ports are available for use.

Port Description Server Client Comment

22

Universal (proxy) agent

Proxy agent

Proxy target

Default when used

25

Mail

SMTP mail server

CloudBees CD/RO server

Default

138

SMB/CIFS

Workspace storage

CloudBees CD/RO agent/apache

Optional

139

SMB/CIFS

Workspace storage

CloudBees CD/RO agent/apache

Optional

389

Active Directory or LDAP server

Active Directory or LDAP

CloudBees CD/RO server

Default

445

SMB/CIFS

Workspace storage

Agent/apache

Optional

465

Mail

SSMTP mail server

CloudBees CD/RO server

Default

636

Active Directory or LDAP server

Active Directory or LDAP

CloudBees CD/RO server

Default

1433

Database

SQL Server

CloudBees CD/RO server

Default when used

1521

Database

Oracle

CloudBees CD/RO server

Default when used

2049

NFS

Workspace storage

CloudBees CD/RO agent and apache

Optional

3306

Database

MySQL

CloudBees CD/RO server

Default when used

5445

Apache ActiveMQ

Only when CloudBees CD/RO server is clustered.

Peer CloudBees CD/RO server in the cluster.

Only when CloudBees CD/RO server is clustered.

5446-5449

JGroups

Only when CloudBees CD/RO server is clustered.

Peer CloudBees CD/RO server in the cluster.

Only when CloudBees CD/RO server is clustered. (The two for TCP and two for Failure detection account for the four JGroups ports.)

9500

Avoiding port conflicts

If you are using ports to install CloudBees CD/RO components on a system and the port is already in use, take one of the following actions:

  • Select a different web server or application port.

  • Uninstall the existing web server or application.

  • Disable the existing web server or application.

  • Reconfigure the existing web server or application to use another port.

Resolving port conflicts

Windows

From a cmd.exe prompt, use

"netstat -ab"

to show all the currently used ports and the executable using the port.

Linux

From a shell prompt, use

"netstat -ap"

to show all the currently used ports and the executable using the port.

Kubernetes cluster and storage requirements
Database requirements