Internet Explorer is no longer supported. Many things will still work, but your experience will be degraded and some things won't function. Please use a modern browser such as Edge, Chrome, or Firefox.

Upgrading your Inedo Product

view on GitHub

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.

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. 2022.14 to 2022.15)

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 (e.g. 2022 to 2023, or 7.0 to 2022)

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.

Upgrade Notifications

Your Inedo product will notify you of new version releases, but if you're using an offline version then you will not be notified of the latest version releases. This means that bug fixes and important security patches may go unnoticed.

Instead, visit your MyInedo page and select "Upgrade Guidance & Change Notes" in the Downloads tab or visit our Public Isue Tracker to view information on new releases and fixes.

Upgrade_Guidance_Changle_Notes
We recommend visiting your MyInedo page regularly and viewing change logs to check if in-software update notifications bring changes applicable to your use case, and to make sure that your software is secure and optimized.

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.

Viewing Upgrade Guidance

If you're having difficulties upgrading your Inedo product, or don't know where to start, you can view upgrade guidance on MyInedo, to determine the recommended route to your intended product version, and the risks involved. This is useful when upgrading from an older product version where a direct upgrade is not possible.

How to View Upgrade Guidance

On your MyInedo page, choose your Inedo product, current version, and chosen upgrade version, then select "Get Upgrade Guidance".

Upgrade_Guidance

You can view our recommended steps for upgrading, specific to your version transition. This provides an assessment of risk, and links to Inedo Documentation pages with further instructions on upgrading based on your situation.

Upgrading can be a straightforward process, such as moving from ProGet version 2024.25 to version 2024.9:

Upgrade_Recommended

In this case, follow the steps on the Upgrading your Inedo Product page to upgrade.

In some cases, multiple steps may be required. Refer to our guidance for detailed instructions:

Upgrade_Not_Possible

In this case, the first step requires upgrading to a different version of ProGet. Visit the Upgrading to ProGet 5.2 page for detailed instructions on upgrading.

We may recommend upgrading to the latest version, for security and stability reasons, particularly when transitioning between two older versions of software:

Upgrade_Not_Recommended
Select See Guidance for detailed Inedo Documentation pages explaining how to upgrade, notable improvements and changes, and common issues / risks encountered.

Change Notes

Despite a risk assessment being provided alongside your recommended upgrade path, it's good practice to note the changes in each maintenance release up to your intended version, visible on the same page.

Change_Notes
Words such as fix can help you pinpoint changes that could resolve issues you might be experiencing. Add and similar words help you spot changes that may improve your workflow.

Use these change notes to determine if there are any fixes, implemented features, or compatibility issues, that could result in a rollback.

Viewing Change Logs

When you want to view change notes in detail to identify where an issue is stemming from after an upgrade or to search for the version in which a patch or feature you were anticipating was released, you can view our detailed change logs. The easiest way to do so is by clicking "Explore Detailed Change Logs". This lets you view the history of changes across all Inedo products.

Explore Detailed Change Logs

You can filter the change logs by count, product, and version to quickly locate changes in your product.

Detailed Change Log Filters

Using our Public Issue Tracker to View Details

Each update links to our Public Issue Tracker with more detailed information on the change.

YouTrack

You can view the complete timeline of the issue, including when it started, when it was resolved, and the release version it was addressed.

If the log shows the state as "completed", this lets you know the change has been implemented in a particular release.