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 3.14.15926 to 3.15.8

Octopus 3.15

Changes in 3.15

New Features

This month, we bring you some much requested improvements to multi-tenant deployments, as well as Octopus Server integration with Let's Encrypt and more!

The way machines, accounts and certificates participate in tenanted-deployments can now be explicitly specified. This includes allowing un-tenanted projects to be deployed to tenanted machines. This has been a long-standing gripe with tenanted deployments which we're very happy to resolve.

Our new integration with Let's Encrypt means you can setup an SSL certificate for your Octopus Portal and it will automatically be renewed when it expires. No need to worry about buying a certificate or manually reconfiguring your server.

Read the full post on the Octopus blog.

Improvements

  • If you're automating the setup of the Octopus Server or Tentacles, you'll be happy to hear that we've put some solid effort into cleaning up our console logging. It will now be much easier to get the information you need without having to do string parsing.
  • Granting Edit permissions now automatically assigns View permissions. It always helps to be able to see what you're changing.

Breaking Changes

  • Console output has changed (for the better!), so we advise testing any automation before upgrading to this version.
  • Octopus.Client version 4.19.0 contains API changes corresponding with the multi-tenant deployment participation change, a minor breaking change for anyone using the MultiTenantDeploymentMode on Project resources via the client.

Upgrading

This release contains a post-install data fix that may take some time (depending on the size of your Events table), so please ensure you allow time for this to complete. If you are running the watchdog service, please ensure this is stopped during the upgrade.

As always, read the upgrade guide for more details on upgrading to Octopus 3.15.

Octopus 3.14

Changes in 3.14

New Features

We are excited to announce the Octopus Deploy plugin for Atlassian Bamboo continuous integration server.

This includes build tasks to make it easy to integrate your build and deployment pipelines.

  • Package applications for deployment
  • Push packages to Octopus
  • Create Octopus releases
  • Deploy Octopus releases

Improvements

Breaking Changes

Octopus Tentacle 3.14.15: Octopus Tentacle 3.14.15 is not backwards compatible with Octopus Server versions less than 3.14.15. This has been fixed as of Octopus Tentacle 3.14.159.

Octopus Server configuration automation: If you are using scripts to automate your Octopus Server installation, please test these scripts with Octopus Server 3.14.x. We have made some changes to simplify configuration of your Octopus Server, but weren't able to maintain 100% backwards compatibility with some of the more obtuse scripts we tested. If you encounter any problems, please look at the scripts generated when you use the Octopus Server wizard.

SQL Database schema upgrades: It may also be worth noting we have adjusted the SQL database schema upgrades so they can be run at the time, and by a user account, which best suits your scenario:

  1. Automatically after the installer completes (new behaviour) - this runs the schema upgrades as the user account who started the installer - falls back to the existing behaviour if the installing user cannot access the SQL database
  2. Automatically during the Octopus Server startup (just like before) - this runs the schema upgrade as the user account who started the Octopus Server
  3. Automatically when executing the Octopus.Server.exe configure command for a setting which is stored in the database (just like before) - this runs the schema upgrade as the user account who started the Octopus Server
  4. Manually by executing the brand new Octopus.Server.exe database --upgrade command - this will run the schema upgrades as the user account who started the command

This may not affect many customers, but enables some advanced scenarios where you can grant limited privileges to the Octopus Server account, and grant schema change privileges to a special account used for installation.

SQL Error 4060 - Cannot open database "OctopusDeploy" requested by the login. The login failed.

If you see an error message like this after the installer completes, you can start the Octopus Server just like before and let it perform the schema upgrades.

Upgrading

Read the upgrade guide for more details on upgrading from your current version to Octopus 3.14.

Release notes

These are the features and fixes you'll get by upgrading from 3.14.15926 to 3.15.8.

Changes in Octopus Server 3.15.8

  • 3522 - Add audit events when a package is deleted from the built-in repository and keep 1 weeks worth of package repository retention logs
  • 3630 - The --console switch is no longer required by scripts automating the Octopus or Tentacle command-line interface, but is still supported for starting either service interactively if so desired
  • 3665 - Fixed a bug that would sometimes result in a null reference exception when setting a password in a step
  • 3675 - Life Cycle listing in the Library will now be available to those with permission LifecycleView, it used to require LifecycleEdit
  • 3678 - Fixed a bug which was preventing the task list from being filtered by Server Node after upgrading to Octopus 3.15.x
  • 3680 - Corrected Azure account variables masking in log
  • 3681 - Add an audit event when the server retention policy deletes a release
  • 3686 - Ensure 'restart required' message is shown for all relevant configure commands
  • 3687 - Improve error message when Docker feed test cant connect successfully

Changes in Octopus Server 3.15.7

  • 3629 - You can now filter audit events for specific tenants
  • 3666 - Fixed a problem which could cause a SQL Connection leak when synchronizing Active Directory groups under certain circumstances
  • 3669 - Fixed a problem where certificate variables were not being scoped by tenant tags
  • 3671 - Default value of sensitive project variable templates is now preserved between updates
  • 3762 - Using our production certificate when signing the Tentacle files in TeamCity
  • 3674 - Fix for ids filtering in projects, tenants and library-variable-sets API

Changes in Octopus Server 3.15.6

  • 3547 - Avoid requirement to load project information on tenant project variables screen
  • 3613 - Project Variable Templates are now also cloned along with the other project properties and data
  • 3622 - Adding ‘ids’ filtering to the API (added to CustomQuery and Index responders)
  • 3645 - Updated Let's Encrypt integration to support specific IP certificate bindings
  • 3651 - Default value of sensitive variable templates is now preserved between updates
  • 3659 - Handle Let's Encrypt http challenge when ForceSSL is enabled and https is configured on a custom port
  • 3660 - Fixed a problem where the project settings page took a long time to load on large installations after installing any Octopus versions between 3.14.15926 and 3.15.5
  • 3663 - Update the ForceSSL redirection to redirect from HTTP -> HTTPS before redirecting the the /app endpoint

Changes in Octopus Server 3.15.5

  • 3533 - Project release filter now searches all versions
  • 3594 - Lifecycle must have at least one phase that is not optional
  • 3615 - Both API and UI for Library Variable Set enforce now the same scoping rules
  • 3644 - Fixed a problem causing intermittent System.AccessViolationException errors when using the built-in Octopus Certificate features
  • 3657 - The permissions for cancelling a task have been simplified, so now you only require the TaskCancel permission in order to cancel a running task

Changes in Octopus Server 3.15.4

  • 3649 - Fixed missing Microsoft.Threading.Tasks error when setting up or health checking Azure steps
  • 3654 - Prevent a potential security vulnerability (CVE-2017-11348) in the Built-In package repository by validating supplied PackageId’s according to the same rules as NuGet. .

Changes in Octopus Server 3.15.3

  • 3096 - First steps in a deployment process can now have run conditions
  • 3639 - Corrected "learn more" link for the Let's Encrypt integration
  • 3643 - Improved validation messages around Let's Encrypt bindings and no longer prevent configuration when using reverse proxy

Changes in Octopus Server 3.15.2

  • 3642 - Windows Service step no longer double escapes additional parameters

Changes in Octopus Server 3.15.1

  • 3505 - Backslash character in windows service password are now escaped
  • 3513 - Quotes around window service exe path were missing
  • 3515 - Start-Service was treating [ as a special character and was unable to start the service
  • 3540 - Passwords with $ characters in Windows Service deployments are now escaped properly
  • 3587 - Corrected VariableEdit permission description
  • 3631 - Fix JS bug introduced in 3.15.0 causing portal loading issues in IE11
  • 3632 - Resolved spurious 'No enabled deployment targets' warning on tenanted deployment previews

Changes in Octopus Server 3.15.0

  • 2722 - Enable untenanted projects to be deployed to tenanted deployment targets
  • 3428 - Acquire package and retention policy steps now show step number and name in variables
  • 3570 - Unscoped variables deleted when user doesn't have VariableViewUnscoped permission
  • 3597 - Added support for managing the Portal SSL certificate using Let’s Encrypt
  • 3598 - Resolved issue with Azure Service-Principal accounts not being available for selection as value of tenant variable template
  • 3605 - The command-line interface for Octopus and Tentacle will now warn you if a service restart is required after certain configuration changes
  • 3606 - Clean up corrupt entries in the events table left behind by a previously resolved issue
  • 3609 - Migrator now maps TenantId when migrating Deployments
  • 3610 - Improved command-line interface for Octopus and Tentacle
  • 3612 - Prevent automatic Tentacle upgrades from restarting the host machine
  • 3614 - Bugfix: Release filtered dashboard does not show environments that deployment can be progressed to
  • 3620 - Certificates with long IDs can now be assigned as Tenant Variable values without throwing a StringTooLongException

Changes in Octopus Server 3.14.15926

  • 3520 - Advanced project settings are shown by default after a users first successful deployment
  • 3558 - Added Support to override Azure Service Management (Storage) Endpoint Suffix
  • 3575 - Tentacle will now ignore partially downloaded packages that are a result of network failure or deployment cancellation
  • 3584 - Improved UI to make it clearer that steps run ‘on behalf’ of roles are optional
  • 3601 - Cloud Service Storage account list handles Azure service management endpoint override correctly
  • 3607 - Resolved an exception starting Octopus Server when the current node name contains certain characters