Upgrading Pipelines

Overview

The procedure to upgrade Pipelines depends on your installation type. We strongly recommend reading through this page before proceeding with your upgrade.

Before you upgrade Pipelines please refer to additional information on supported platforms, browsers and other requirements, and the system architecture.

Important

Make sure to use the same upgrade method (Linux Archive, Docker, Helm, RPM, Debian, etc.) as the one you initially used to install Pipelines.

To ensure you can restore Pipelines in case you encounter any issues during the upgrade process, we strongly recommend that you make sure your system.yaml and database backups are up to date.

Upgrade Steps

The upgrade procedure involves the following main steps:

Download Pipelines (Docker Compose, RPM, Debian).
Upgrade Pipelines according to the installer distribution type.

JFrog Subscription Levels

SELF-HOSTED

_ENTERPRISE+

Page Contents

Upgrading to Version 1.x

Extract the installer from the downloaded .rpm, .deb, or .tar.gz file.

Linux Archive (tar.gz)

$ mkdir -p installer && tar -C installer -xvzf pipelines-<version>.tar.gz 
$ cd installer/pipelines-<version>

RPM

$ sudo rpm -Uvh pipelines-<version>.rpm

Debian

$ sudo dpkg -i pipelines-<version>.deb

Now may be a good time to update the default images used for steps in Pipelines. To avoid changing Pipelines that already exist, the defaults are not updated automatically but may instead be updated through the system.yaml. If you are planning to use a newly supported operating system or just want to update the default version used for a language, the Pipelines System YAML documentation has more information on how to update your system.yaml with the new defaults.

The image versions that are used by default in new installations with the new Pipelines version may be found in the scripts/configs/system.full-template.yaml and scripts/configs/system.basic-template.yaml in the installer. If the .rpm or .deb installer was used, this will be /opt/jfrog/pipelines/installer/scripts/configs/system.full-template.yaml.
Run the upgrade command to upgrade Pipelines. This assumes that you installed Pipelines with sudo. If Pipelines was installed as a different user, that user should perform the upgrade.
```
$ sudo pipelines upgrade
```

When the upgrade is complete, you can access Pipelines through the JFrog Platform at: http://<jfrogUrl>/ui/.

Upgrading Pipelines Chart Version 1.x to 2.x and Above

Due to breaking changes in the RabbitMQ subchart (6.x to 7.x chart version when rabbitmq.enabled=true) and PostgreSQL subchart (8.x to 9.x chart version when postgresql.enabled=true), you will need run the following manual commands (downtime is required).

For more information about the breaking changes in RabbitMQ, click here.

For the Pipelines chart, refer to the Pipelines Changelog.

Important

Make sure all existing Pipelines build runs are completed (i.e., the RabbitMQ queues are empty) when you begin an upgrade.

Note that the RabbitMQ password configuration in the values.yaml file has changed from rabbit.rabbit.password to rabbit.auth.password.

kubectl --namespace <namespace> delete statefulsets <release_name>-pipelines-services
kubectl --namespace <namespace> delete statefulsets <release_name>-pipelines-vault
kubectl --namespace <namespace> delete statefulsets <release_name>-postgresql
kubectl --namespace <namespace> delete statefulsets <release_name>-rabbitmq
kubectl --namespace <namespace> delete pvc data-<release_name>-rabbitmq-0

helm upgrade --install pipelines --namespace <namespace> jfrog/pipelines

It is recommended that, after upgrading Pipelines, you re-initialize all static nodes to take advantage of new features.

Content

Space Tools