Compare releases

Compare releases and check for compatibility between your existing Octopus Server and new releases.

What's new

These are the most important features you'll get by upgrading from 2.1.3.1223 to 2.3.1

Octopus 2.3

Highlights of 2.3

  • Prompting for variables at deployment time
  • Deploy to specific machines
  • Interesting mode for task output
  • Audit log filtering
  • Task cancellation and performance improvements

Read our blog post about the new features

Octopus 2.2

No highlights for 2.2

Octopus 2.1

Highlights of 2.1

  • Built-in NuGet feed
  • Guest account log-in support
  • Variable editor improvements
  • Auditing improvements

Release notes

These are the features and fixes you'll get by upgrading from 2.1.3.1223 to 2.3.1.

Changes in Octopus Server 2.3.1

  • 349 - Active process management
  • 699 - Apply retention policies does not finish
  • 642 - Better expand/collapse behavior for Task Output, and "Interesting" mode
  • 714 - Check for more duplicate issues during import from 1.6
  • 686 - Clean actors when repairing DB
  • 551 - Concurrent package downloads compete for file access in the package cache
  • 671 - Custom expression on NuGet Package ID field in process step doesn't get replaced when creating a release
  • 529 - Custom fields for NuGet feeds does not let me enter a variable
  • 717 - Ensure that environments that the user can't see aren't removed from the environment list when editing steps
  • 713 - Ensure we don't run custom scripts when the feature is disabled
  • 673 - Fail running tasks when restoring backups
  • 701 - Filter audit events
  • 563 - Generic template-based file transformation
  • 710 - Improve performance of task output and dashboard rendering
  • 695 - Keep focus on manual comments field when refreshing deployment
  • 640 - Keep horizontal scroll position on dashboard
  • 639 - Large package uploads degrade over time
  • 698 - Migrate OctopusWebSiteName
  • 716 - Only allow editing variable sets/deployment processes if editing the latest version
  • 573 - Project Viewers cannot submit manual steps even in an appropriate team
  • 674 - Promote To and Try Again should remember previous skipped steps
  • 227 - Prompted variables
  • 715 - Redirect after login
  • 721 - Select specific machines to deploy to
  • 685 - Select/deselect all link on skip steps for deployments
  • 694 - Standardise how collections of paths are represented in variables
  • 589 - Support IIS 8/8.5 Performance Enhancements
  • 474 - Support large numbers of projects in the drop-down project list
  • 712 - TeamCity create/deploy release runner does not fail if deployment fails
  • 720 - When tasks are queued, show a list of tasks they are queued behind Please read this guide when upgrading from Octopus 2.0.

Changes in Octopus Server 2.2.1

Highlights of 2.2

  • Ad-hoc PowerShell console
  • Define Deploy.ps1 scripts in Octopus

    Changes from 2.1.3 to 2.2.1

  • 675 - Full screen editor for PowerShell scripts

  • 672 - Deploy.ps1 scripts can be defined in Octopus rather than embedded in packages
  • 670 - Email step CC binding bug fix
  • 668 - Various license encoding issues
  • 652 - Fix excessive web UI HTTP traffic when browsing
  • 646 - IIS bindings support duplicate copies of a certificate in the store
  • 627 - Library variable set scoping/resolving improvements
  • 605 - FTPS timeout tweaks
  • 601 - Windows Services and custom installation directory work together
  • 598 - Releases for the same project can be created simultaneously
  • 542 - Process step renaming issue fixed
  • 540 - Project overview and release details page now auto-refresh
  • 539 - Large NuGet package sizes are shown correctly
  • 535 - IIS convention now allows HTTP/HTTPS bindings to be bound
  • 465 - Reorder environments always updates dashboard
  • 176 - Show master key improvements for remote desktop users

Changes in Octopus Server 2.1.3.1223

Highlights of 2.1

  • Built-in NuGet feed
  • Guest account log-in support
  • Variable editor improvements
  • Auditing improvements

    Changes from 2.1.2 to 2.1.3

  • 650 - MSI installers ensure old versions are uninstalled

    Changes from 2.1.1 to 2.1.2

  • 634 - MSI installers are now scoped to all users

  • 647 - Incorrect permission check for Promote button
  • 643 - Ensure PowerShell scripts are all UTF8
  • 638 - Octo.exe and TeamCity fixes and improvements

    Changes from 2.0 to 2.1.1

  • 629 - Support for guest account log-in

  • 621 - Maintain disabled status for users migrated from 1.6
  • 614 - Migrate the environment associated with 1.6 manual steps
  • 613 - Fixed binding of the "require packages" check-box when editing steps
  • 612 - Suppress error logs generated by disabled polling tentacles; log incoming IPs more prominently
  • 611 - Exclude machines without environments when migrating from 1.6
  • 597 - Escape command-line arguments properly from configuration wizards, fixing support for AD DOMAIN\user syntax for admin usernames
  • 586 - More robust PowerShell prerequisite detection
  • 583 - List common arguments in command-line help
  • 575 - Hide the change password function when AD authentication is enabled
  • 552 - Prevent restarts of the Tentacle process from blocking queued deployments
  • 549 - Provide a Tools UI for selecting non-default Server instances
  • 545 - UI for skipping already-installed packages with project-based setting to choose force/skip default
  • 530 - Fixed escaping of HTML characters when rendering variable values in the editor
  • 457 - Filtering and sorting in the variable editor
  • 423 - Block migration from 1.6 properly when invalid step names are present
  • 380 - Fixed layout of variable editor text input on scaled displays
  • 310 - Create projects by cloning existing projects
  • 275 - Pre-select the target environment properly when try again is used
  • 251 - Built-in NuGet feed
  • 109 - Improved execution plan accuracy for deployments without package acquisition
  • 71 - Show changes to documents in audit events