Compare releases

Compare releases

Find out what's new in the latest Octopus Deploy release, or compare the latest release to what you're currently running to see what's changed.

Highlights

These are the most important features you'll get by upgrading from 1.6.3.1723 to 2.0.13.1100

Octopus 1.6

No highlights for 1.6

Octopus 2.0

#

Details

Changes in Octopus 1.6.3.1723

  • Faster Azure package uploads
  • Increase private key size of Octopus X.509 certificates to 2048 bytes
  • Fixes to Set-OctopusVariable when using long variable names

Changes in Octopus 2.0.5.933

Octopus Deploy 2.0 has been 6 months in the making, and a lot has changed since Octopus 1.6. Octopus 2.0 is a side-by-side upgrade; please view the upgrade guide for details.

Changes in Octopus 2.0.6.950

Octopus Deploy 2 Release Candidate 3.

Changes in Octopus 2.0.7.966

Fixes and improvements since RC3: - 408 - Ignore missing scope entities when migrating variables from Octopus 1.6 - 410 - Fix certificate generation regression - 403 - Migrate Retention Policies from Octopus 1.6 - 412 - Succeed when downloading a package on Tentacles if none require it - 413 - Fix migration of FTP steps from Octopus 1.6 - 400 - Fix Tentacle startup on 32-bit architectures - 419 - Generate and save Tentacle certificate at installation to avoid endless regeneration - 424 - Save Project Group Description field - 411 - Show Project Disable checkbox - 394 - Handle hostnames starting with api - 405 - Allow backup intervals >= 24h - 407 - UI fixes for rolling batch size - 416 (partial) - Recreate indexes on Restore of backup to avoid race condition at startup

Changes in Octopus 2.0.8.977

Since RC4: - 427 - IIS web site feature SSL cert thumbprint now required to prevent failure at deployment - 425 - Slashes in command-line args now properly escaped, fixing installation failures - 423 - Step names now properly validated before migration from 1.6 - 416 - Fixed check for default project group causing failure to start up after restoring a backup - 415 - Fixed several issues preventing AD authentication being set up or used - 414 - Allow a specific set of machines to be targeted when deploying a release via the API or Octo.exe - 397 - Don't show the Invite button for users when AD authentication is in use - 384 - Better names/descriptions for IIS deployment features, to avoid confusion - 365 - Repair RavenDB Storage... option in Octopus Manager Important, scripted Tentacle installation has changed in this version, the new-certificate command is now required.

Changes in Octopus 2.0.9.1015

Since RC5: - 476 - Preserve the current environment selection in Firefox during background refresh - 471 - Fixed crash in Tentacle.exe when empty log output is written - 470 - Pre-validate usernames for uniqueness when migrating from 1.6 - 469 - Fix bug preventing machine discovery if the endpoint mapped to multiple existing machines - 461 - Migrate the Environments property from 1.6 for email steps - 459 - Show the task log properly when team permissions are environment-restricted - 452 - Prevent on-dashboard releases being removed by rentention policies when migrated from 1.6 - 449 - Prevent sensitive variables leaking into logs via the "Windows Service" feature - 439 - Show more variables in the binding helper dropdown, and exclude deprecated/legacy items - 438 - Fixed issue preventing SSL bindings being created for the Octopus Web UI - 436 - Fixed bug preventing environments being selected when registering polling Tentacles - 435 - Apply authentication settings from the "IIS web site" feature to applicationHost.config rather than web.config - 434 - Fixed Tentacle.exe register-with crash with NullReferenceException - 432 - Preserve the associated NuGet package versions when releases are migrated from 1.6 - 429 - Provide a timeout for FTP step file transfers - 428 - Fixed race condition potentially causing wrong server thumbprint to be displayed - 426 - Provide Octopus.Action.Package.SkipIfAlreadyInstalled to regain old non-forced deployment behaviour where required - 422 - Problems detecting the latest version of a package on some NuGet servers (esp. TC8) - 401 - Support Host header bindings for the Octopus Web UI - 317 - TRACE/DEBUG logging is off by default Important notes: two issues have been reported relating to Active Directory authentication in this version. Active Directory accounts migrated from a 1.6 installation are not usable and need to be re-created. Authentication across multiple Active Directory domains is also unsupported in this version.

Changes in Octopus 2.0.9.1020

Since RC6: - 484 - Fixed display of Add Environment button - 462 - Handle authentication of users not in the current computer's domain - 456 - Convert usernames to UPNs when migrating from 1.6 Looking for RC8/2.0.10? - an authentication bug in 2.0.10 makes the build unsuitable for use at this time; a patched replacement is currently in testing.

Changes in Octopus 2.0.10.1059

Important Note: This build extends our Active Directory authentication support using .NET's LDAP implementation; this will accept invalid credentials if the Guest account is enabled on the domain. Future builds will disable LDAP authentication by default, see this issue for details. Since RC7: - 513 - Don't automatically start Windows services when their start-up type is Manual - 512 - Fixed display issues when environments are excluded from the dashboard - 502 - Increase the timeouts on the 1.6 database import during migration - 496 - Fixed display of Project screen tabs when permissions are restricted - 492 - Reorder IIS Web Site creation steps to avoid some configuration errors - 491 - Exclude duplicate endpoints when upgrading Tentacles - 490 - Short pause to account for App Pool creation during IIS Web Site configuration - 489 - Accept PowerShell v4 as fulfilling the PowerShell prerequisite check - 485 - Fixed display of available upgrade when its version is equal or less than the current installed version - 483 - Allow a custom UPN suffix to be specified when migrating Active Directory users from 1.6 - 481 - Run Health Checks at 60 minute (rather than 5 minute) intervals - 467 - Automatically select the Specific Version radio button when version numbers are typed or selected - 463 - Improve Task Log rendering for large deployments - 462 - Support Active Directory authentication across multiple domains - 426 - Support for the Octopus.Action.Package.SkipIfAlreadyInstalled variable to regain 1.6 non-forcing deployments - 390 - Define $OctopusParameters and other PowerShell variables in the global scope

Changes in Octopus 2.0.10.1066

Important note for upgrades: Default installation paths have changed in this version; either choose your existing installation folder in the Windows Installer dialog, or, after installing the Octopus Server run: Octopus.Server.exe service --stop --reconfigure --start This command is also required when switching between 32- and 64-bit installations, replacing Octopus.Server.exe with Tentacle.exe in the case of Tentacle installs; see this issue for more information. Since RC8: - 544 - Fixed Active Directory Authentication bug introduced in RC8 permitting invalid passwords (users of 2.0.10.1059 are advised to upgrade from this version) - 358 - Installers now default to a non-version-specific path; separate MSI for 64-bit only installations Since RC7: - 513 - Don't automatically start Windows services when their start-up type is Manual - 512 - Fixed display issues when environments are excluded from the dashboard - 502 - Increase the timeouts on the 1.6 database import during migration - 496 - Fixed display of Project screen tabs when permissions are restricted - 492 - Reorder IIS Web Site creation steps to avoid some configuration errors - 491 - Exclude duplicate endpoints when upgrading Tentacles - 490 - Short pause to account for App Pool creation during IIS Web Site configuration - 489 - Accept PowerShell v4 as fulfilling the PowerShell prerequisite check - 485 - Fixed display of available upgrade when its version is equal or less than the current installed version - 483 - Allow a custom UPN suffix to be specified when migrating Active Directory users from 1.6 - 481 - Run Health Checks at 60 minute (rather than 5 minute) intervals - 467 - Automatically select the Specific Version radio button when version numbers are typed or selected - 463 - Improve Task Log rendering for large deployments - 462 - Support Active Directory authentication across multiple domains - 426 - Support for the Octopus.Action.Package.SkipIfAlreadyInstalled variable to regain 1.6 non-forcing deployments - 390 - Define $OctopusParameters and other PowerShell variables in the global scope

Changes in Octopus 2.0.11.1080

Upgrade information: after installing to a new Program Files path, or switching between the x86 and x64 installers, it may be necessary to reinstall the Windows service using the button in the Octopus Manager application. Since RC9: - 570 - Reset trust when reinstalling Tentacle via the Tentacle Manager - 565 - Don't treat the Machine Name as a hostname when registering polling Tentacles - 561 - Reinstall service option in the manager applications to recover from path changes - 555 - Drop the broken "launch" checkbox on the final page of the server installer - 548 - Resolve Active Directory users to UPNs when adding manually - 547 - Permissions tweak to better support environment-scoped permissions - 528 - Fixed breadcrumbs in the Library Variable Set screen - 510 - Preserve the old installation path during upgrades - 503 - Fixed item-count retention policy bug that would delete current releases

Changes in Octopus 2.0.12.1092

Installation instructions are available on the documentation page. Upgrading from Octopus 1.6: - New license keys are required for Octopus 2.0; visit the license upgrade page to check eligibility for free upgrades or discounted upgrade pricing. - Octopus 2.0 is not an in-place update to 1.6; it is important to read the migration guide before installing Octopus 2.0 on a production Octopus 1.6 server. Upgrading from 2.0 Release Candidates - A license or trial key is now required for editions other than Community; see http://octopusdeploy.com/purchase for editions and pricing. - After installing to a new Program Files path, or switching between the x86 and x64 installers, it may be necessary to reinstall the Windows service using the Octopus Manager application. - Users of Active Directory authentication and early RC builds may need to re-create the Octopus Server instance (using the Octopus Manager application) to establish the identity of the Administrator (see: #594). Since 2.0 RC10: - 346 - Removed the RC usage time limit - 513 - Don't start installed services that have "Manual" start-up type

Changes in Octopus 2.0.13.1100

Installation instructions are available on the documentation page. Upgrading from Octopus 1.6: - New license keys are required for Octopus 2.0; visit the license upgrade page to check eligibility for free upgrades or discounted upgrade pricing. - Octopus 2.0 is not an in-place update to 1.6; it is important to read the migration guide before installing Octopus 2.0 on a production Octopus 1.6 server. Upgrading from 2.0 Release Candidates - A license or trial key is now required for editions other than Community; see http://octopusdeploy.com/purchase for editions and pricing. - After installing to a new Program Files path, or switching between the x86 and x64 installers, it may be necessary to reinstall the Windows service using the Octopus Manager application. - Users of Active Directory authentication and early RC builds may need to re-create the Octopus Server instance (using the Octopus Manager application) to establish the identity of the Administrator (see: #594). Since 2.0.12: - 602 - Removed license check at startup