Platform notes

3 minute readReference

This page provides additional implementation notes for CloudBees CD/RO platforms in your enterprise. Refer to the following topics for a list of officially supported platforms for CloudBees CD/RO:

CloudBees CD/RO server platform notes

Here are platform notes for the CloudBees CD/RO, web, repository, and CloudBees Analytics servers.

Microsoft Windows platforms

Platform Notes

Windows Server 2019

An administrator might need to disable User Account Control (UAC). If the installer runs under account x, but services run under account y, installation directories (both program and data) probably have permissions that prevent y’s access. This applies particularly to data directories.

Windows Server 2016

Windows 10

No notes

Linux platforms

Platform Notes

CentOS 7

The following installation prerequisites apply to all CloudBees CD/RO installers.

Do not choose nobody for the CentOS user. CentOS does not allow a command such as su - nobody -c foo.sh, because it is not a shell account.

Red Hat Enterprise Linux 9

The following installation prerequisites apply to all CloudBees CD/RO installers.

Do not choose nobody for the RHEL user. RHEL does not allow a command such as su - nobody -c foo.sh, because it is not a shell account.

For CloudBees CD/RO v2023.10.0, only the package libxcrypt-compat is required. Use the dnf list libxcrypt-compat command to verify the package is installed. If the libxcrypt-compat package is not installed, install it using sudo dnf -y install libxcrypt-compat.

Red Hat Enterprise Linux 8

The following installation prerequisites apply to all CloudBees CD/RO installers.

Do not choose nobody for the RHEL user. RHEL does not allow a command such as su - nobody -c foo.sh, because nobody is not a shell account.

Red Hat Enterprise Linux 7

Ubuntu 22.04

The following installation prerequisites apply to all CloudBees CD/RO installers.

Choosing the Ubuntu user

Do not choose “nobody” for the Ubuntu user. Ubuntu does not allow a command such as su - nobody -c foo.sh, because nobody is not a shell account.

Adding the bin directory to the PATH environment variable

Update /etc/environment to include the CloudBees CD/RO Automation Platform bin directory in the PATH environment variable. Steps running with impersonation on Ubuntu use PATH that is set in /etc/environment. As a side-effect, the CloudBees CD/RO Automation Platform bin directory is not in PATH in the impersonation context, so calls to tools such as ectool and postp fail with a “not found” error.

Fixing the raise ValueError, need a file or string Error

If you receive an error during installation similar to the following:

[source,shell] ---- File "/usr/lib/lsb/install_initd", line 3, in <module> import sys, re, os, initdutil File "/usr/lib/lsb/initdutils.py", line 18 raise ValueError, 'need a file or string' ^ SyntaxError: invalid syntax run the following command: sudo sed -i "s/python3/python/" /usr/lib/lsb/install_initd ----

This error is a known Ubuntu bug.

Ubuntu 20.04

Ubuntu 18.04

Agent platform notes

This section lists agent platform notes. You can drive automation on target machines by either installing agents natively or by running them remotely using proxy agents.

Pure agent platforms

All server platforms support pure agents; see their notes here. Consult the table below for additional pure agent platforms.

Platform Notes

macOS X 10.4 (Tiger) and later (Intel architecture)

No notes.

SUSE Linux Enterprise Server 12.3

Run zypper install libstdc++6-32bit before installing agents on a 64-bit machine. This command installs the SUSE 32-bit libraries required by the CloudBees CD/RO executable file.

Proxy agents for other platforms

A proxy agent is a CloudBees CD/RO agent that channels to a proxy target, which lets you drive automation in an agentless fashion. A proxy agent is an agent on a supported Windows or Linux platform that you use to take actions on any platform that is not listed above. For example, you can use a proxy agent to automate actions on an IBM z Systems mainframe running z/OS or Linux OS.

You can use a proxy agent to communicate with any target platform that can run commands via an SSH protocol. For details, refer to Configure an environment proxy server.