Upgrading your Inedo Product
  • 30 Jun 2022
  • 2 Minutes to read
  • Dark
  • PDF

Upgrading your Inedo Product

  • Dark
  • PDF

Article Summary

ProGet, BuildMaster, and Otter will never automatically update themselves. You are in complete control of when and how often you upgrade, and you can just as easily downgrade if needed. This lets you eliminate the "surprise" from unwanted new features and drastically reduce the impact of changes or bugs (regressions).

Although it's really easy to upgrade your Inedo product, that doesn't mean you should upgrade as soon as a new version is available. This article gives guidance on how and when you should upgrade.

Looking for Product-specific Upgrade Guidance?

We've put together a guide for each product that has the recommended upgrade paths for major versions.

When should I upgrade my Inedo Product?

Before updating to a newer version, you should weigh the costs associated with the update process against the value and benefits of the new features or bug fixes added. To help you do this, we have two categories of releases.

Maintenance Releases (e.g. 6.0.4 to 6.0.5)

Best Practice: Upgrade at least Quarterly

Maintenance releases are low risk and contain only backward-compatible enhancements, bug fixes, and security patches.

We publish maintenance releases of each product at least twice a month, and most of the changes are very small and impact only a handful of customers. We will occasionally ship "preview" features in maintenance updates, but only if it can be done safely and if it's clearly marked in the product as a preview.

Individual changes are carefully documented on our public issue tracker and follow our rigorous Change Management Process. Users may even request source code access to see exactly what changed.

However, lots of small, low-risk changes add up over time, so we recommend upgrading at least once per quarter to minimize the risk of regression.

Major Releases (5.0 to 5.1, or 5.3 to 6.0, or 7.0 to 2022)

Best Practice: Carefully Read Upgrade Notes

A major release typically implements a brand new feature or overhauls an existing one, and is inherently riskier than a maintenance release.

Each major release is a bit different, and may include:

  • backward-incompatible API changes
  • SDK changes that may require custom extensions to be recompiled
  • major database schema changes
  • major UX changes
  • major functionality updates
  • platform/system requirement changes
  • all bug fixes up to and including the new major version

Because of the major changes that may be introduced, you should always carefully read the upgrade notes performing a major update. These can be found under the Installation & Maintenance section of each product, in the documentation.

In most cases, you should schedule a specific time slot away from crucial deployments in order to perform a major update. Many users even set up separate instances in order to explore functionality before rolling out the update to their production instance.

How to Upgrade

Before upgrading your Inedo product, we recommend performing a back-up, just in case something goes wrong and you need to rollback. This is especially important when performing a major upgrade.

Performing the upgrade itself is generally very easy.

Upgrading on Windows Servers

The easiest way to manage your product installation on Windows is with Inedo Hub. This is a lightweight Windows application that's used to install, update, and otherwise service the Inedo products on your server.

HOWTO: Upgrade using the Inedo Hub

Upgrading on Linux Servers

Inedo products running on Linux using Docker containers, and can be upgraded by installing and running a new version of the container image.

Upgrading Docker Containers

You can also run ProGet through Docker Compose or Kubernetes, which will follow the same upgrade principles.

Was this article helpful?