Upgrading TeamForge Orchestrate

This section provides steps for upgrading TeamForge Orchestrate installations to the latest release.

Upgrade Overview

The upgrade process varies for single host and multi host installations of Orchestrate. As such, this section contains separate documentation for each:

Data loss potential during upgrades

While we have designed the upgrade process to minimize data loss, there is still a chance that Orchestrate misses data from sources during an upgrade.

During normal operation, adapters communicate source data (such as builds and commits) directly with RabbitMQ, the message queue layer between your data sources and Orchestrate. Orchestrate then consumes these messages from the queue as fast as it can. Disruption to RabbitMQ or the database layer (MongoDB) may lead to data loss as follows:

Risk from these two scenarios can be mitigated by upgrading MongoDB and RabbitMQ components at times of low traffic ( i.e., after work hours).

Backup your data

Before upgrading, it is a good idea to backup TeamForge Orchestrate system and data, see Backup and Restore.