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 supportedplatforms, browsers and other requirements, and thesystem architecture.

重要的

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 yoursystem.yamland database backups are up to date.

Upgrade Steps

The upgrade procedure involves the following main steps:

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

JFrog子scription 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, seeUpgrading to Pipelines 1.20.7 or later in Ubuntu.

Before you upgrade, ensure that the operating system version that you use issupported. SeeSystem Requirementsfor detailed information on operating system support.

Extract the installer from the downloaded.rpm,. deb, or.tar.gzfile.

Linux Archive (tar.gz)

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

RPM

$ sudo rpm -Uvh pipelines-.rpm

Debian

$ sudo dpkg -i pipelines-.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 thesystem.yaml. If you are planning to use a newly supported operating system or just want to update the default version used for a language, thePipelines System YAMLdocumentation has more information on how to update yoursystem.yamlwith the new defaults.

The image versions that are used by default in new installations with the new Pipelines version may be found in thescripts/configs/system.full-template.yamlandscripts/configs/system.basic-template.yamlin the installer. If the.rpmor. debinstaller was used, this will be/opt/jfrog/pipelines/installer/scripts/configs/system.full-template.yaml.
Runtheupgradecommand to upgrade Pipelines.This assumes that you installed Pipelines withsudo. 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:///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射频/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