Upgrading to Version 1.x
Extract the installer from the downloaded
- 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.yamlwith the new defaults.
The image versions that are used by default in new installations with the new Pipelines version may be found in the
system.basic-template.yamlin the installer. If the
.debinstaller was used, this will be
upgradecommand 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.
When the upgrade is complete, you can access Pipelines through the JFrog Platform at:
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.
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
It is recommended that, after upgrading Pipelines, you re-initialize all static nodes to take advantage of new features.