How to Hold CloudBees Core Package Version During OS Patching

2 minute readKnowledge base

Issue

During routine system-level updates (apt upgrade, yum update, dnf upgrade), package managers may automatically upgrade CloudBees CI packages, such as cloudbees-core-oc or cloudbees-core-cm. This can cause unintended version changes if you intend to maintain a specific CloudBees CI release independent of OS patch operations.

Environment

Resolution

This procedure will prevent CloudBees CI package upgrades while other OS packages may still be updated normally.

Debian / Ubuntu (apt)

  • Identify installed CloudBees CI packages (e.g., cloudbees-core-oc, cloudbees-core-cm).

  • Lock the package version using apt-mark:

sudo apt-mark hold cloudbees-core-oc
sudo apt-mark hold cloudbees-core-cm
▼

  • Confirm hold status:

apt-mark showhold
▼

Side note: In order to unlock the version of the product, you can run the following instructions:

sudo apt-mark unhold cloudbees-core-oc
sudo apt-mark unhold cloudbees-core-cm
▼

RHEL / CentOS / Fedora / Amazon Linux (yum / dnf)

Version locking with yum Plugin: yum-versionlock

If you have already installed yum Plugin: yum-versionlock, you can run the following command to hold CloudBees CI packages from being automatically upgraded:

sudo yum versionlock cloudbees-core-*
▼

If you don’t have the previously mentioned yum plugin, you can use direct package exclusion, which can be applied with the following steps:

  • Edit /etc/yum.conf or /etc/dnf/dnf.conf and add:

exclude=cloudbees-core-*
▼

  • Alternatively, this can be applied directly to the update/upgrade command:

sudo yum update --exclude=cloudbees-core-*
# or
sudo dnf upgrade --exclude=cloudbees-core-*
▼

OpenSUSE / Suse

OpenSUSE manages package upgrades via zypper. You can add CloudBees CI packages to the zypper exclude list (consult your distro version for syntax).

sudo zypper al cloudbees-core-*
▼

References