Cloud customer?
Start for Free >
Upgrade in MyJFrog >
What's New in Cloud >





Working with an older version? JFrog Artifactory 6.x | JFrog Xray 2.x | JFrog Mission Control 3.x | JFrog Distribution 1.x |


Skip to end of metadata
Go to start of metadata

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:

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

JFrog Subscription Levels

SELF-HOSTED
ENTERPRISE+
Page Contents

Upgrading to Version 1.x

Upgrade to 1.20.7 or later in Ubuntu

If you use Ubuntu, and if PostgreSQL was previously installed on your machine by the Pipelines installer, you need to remove the files since it was not installed using a package manager. For more information, see Upgrading to Pipelines 1.20.7 or later in Ubuntu.

Before you upgrade, ensure that the operating system version that you use is supported. See System Requirements for detailed information on operating system support.

  1. 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
  2. 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.

  3. 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 to Pipelines 1.20.7 or later in Ubuntu

If you use Ubuntu, and if PostgreSQL was previously installed on your machine by the Pipelines installer, you need to remove the files since it was not installed using a package manager. You can proceed with the upgrade after you remove these PostgreSQL files.

You can run the following script to remove these files.

rm -rf /usr/local/bin/clusterdb \
/usr/local/bin/createdb \
/usr/local/bin/createlang \
/usr/local/bin/createuser \
/usr/local/bin/dropdb \
/usr/local/bin/droplang \
/usr/local/bin/dropuser \
/usr/local/bin/ecpg \
/usr/local/bin/initdb \
/usr/local/bin/oid2name \
/usr/local/bin/pg_archivecleanup \
/usr/local/bin/pg_basebackup \
/usr/local/bin/pg_config \
/usr/local/bin/pg_controldata \
/usr/local/bin/pg_ctl \
/usr/local/bin/pg_dump \
/usr/local/bin/pg_dumpall \
/usr/local/bin/pg_isready \
/usr/local/bin/pg_receivexlog \
/usr/local/bin/pg_recvlogical \
/usr/local/bin/pg_resetxlog \
/usr/local/bin/pg_restore \
/usr/local/bin/pg_rewind \
/usr/local/bin/pg_standby \
/usr/local/bin/pg_test_fsync \
/usr/local/bin/pg_test_timing \
/usr/local/bin/pg_upgrade \
/usr/local/bin/pg_xlogdump \
/usr/local/bin/pgbench \
/usr/local/bin/pltcl_delmod \
/usr/local/bin/pltcl_listmod \
/usr/local/bin/pltcl_loadmod \
/usr/local/bin/postgres \
/usr/local/bin/postmaster \
/usr/local/bin/psql \
/usr/local/bin/psql.bin \
/usr/local/bin/reindexdb \
/usr/local/bin/vacuumdb \
/usr/local/bin/vacuumlo \
/usr/local/lib/libcom_err.so.3 \
/usr/local/lib/libcrypto.so.1.0.0 \
/usr/local/lib/libcurl.so \
/usr/local/lib/libcurl.so.4 \
/usr/local/lib/libcurl.so.4.5.0 \
/usr/local/lib/libecpg.a \
/usr/local/lib/libecpg.so \
/usr/local/lib/libecpg.so.6 \
/usr/local/lib/libecpg.so.6.7 \
/usr/local/lib/libecpg_compat.a \
/usr/local/lib/libecpg_compat.so \
/usr/local/lib/libecpg_compat.so.3 \
/usr/local/lib/libecpg_compat.so.3.7 \
/usr/local/lib/libedit.so.0 \
/usr/local/lib/libgssapi_krb5.so.2 \
/usr/local/lib/libiconv.so.2 \
/usr/local/lib/libk5crypto.so.3 \
/usr/local/lib/libkrb5.so.3 \
/usr/local/lib/libkrb5support.so.0 \
/usr/local/lib/liblber-2.4.so.2 \
/usr/local/lib/libldap-2.4.so.2 \
/usr/local/lib/libldap_r-2.4.so.2 \
/usr/local/lib/libncurses.so.5 \
/usr/local/lib/libpango-1.0.so \
/usr/local/lib/libpango-1.0.so.0 \
/usr/local/lib/libpango-1.0.so.0.1700.0 \
/usr/local/lib/libpangocairo-1.0.so \
/usr/local/lib/libpangocairo-1.0.so.0 \
/usr/local/lib/libpangocairo-1.0.so.0.1700.0 \
/usr/local/lib/libpangoft2-1.0.so \
/usr/local/lib/libpangoft2-1.0.so.0 \
/usr/local/lib/libpangoft2-1.0.so.0.1700.0 \
/usr/local/lib/libpangox-1.0.so \
/usr/local/lib/libpangox-1.0.so.0 \
/usr/local/lib/libpangox-1.0.so.0.1700.0 \
/usr/local/lib/libpangoxft-1.0.so \
/usr/local/lib/libpangoxft-1.0.so.0 \
/usr/local/lib/libpangoxft-1.0.so.0.1700.0 \
/usr/local/lib/libpgcommon.a \
/usr/local/lib/libpgport.a \
/usr/local/lib/libpgtypes.a \
/usr/local/lib/libpgtypes.so \
/usr/local/lib/libpgtypes.so.3 \
/usr/local/lib/libpgtypes.so.3.6 \
/usr/local/lib/libpq.a \
/usr/local/lib/libpq.so \
/usr/local/lib/libpq.so.5 \
/usr/local/lib/libpq.so.5.8 \
/usr/local/lib/libsasl2.so.3 \
/usr/local/lib/libssl.so.1.0.0 \
/usr/local/lib/libuuid.so.16 \
/usr/local/lib/libxml2.so.2 \
/usr/local/lib/libxslt.so.1 \
/usr/local/lib/libz.so.1 \
/usr/local/lib/pkgconfig \
/usr/local/lib/postgresql


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

Before you upgrade, ensure that the operating system version that you use is supported. See System Requirements for detailed information on operating system support.

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.

  • No labels
Copyright © 2022 JFrog Ltd.