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 2019.11.3 to 2019.12.6
Octopus 2019.12
Highlights
Operations Runbooks, Jenkins plugin, PowerShell Core support, improved build server integration and more!
- Operations Runbook platform for automating routine maintenance and emergency operations tasks. Runbook examples include infrastructure provisioning, database management, and website failover and restoration.
- Official Octopus Deploy Jenkins plugin enabling teams to integrate their Jenkins builds with Octopus Deployments
- Built-in PowerShell Core support for both Windows and Linux platforms
- Improved build information and work item tracking
- Package metadata has been renamed to Build Information and promoted to a top level section in the Octopus Library.
- Added support for deployment change templates so you can customize the structure of your deployment changes.
Read our blog post to learn more.
Breaking changes
This release includes the following breaking changes.
Octopus API and Octopus.Client
The Octopus API has changed as a part of this release, versions of Octopus.Client before 8.0.0 can not create scheduled triggers on an Octopus Server where the version is older than 2019.11.0.
PowerShell Core
PowerShell Core support has introduced a change where running PowerShell scripts against non-Windows targets no longer silently ignores .ps1 files. Octopus will now attempt to execute .ps1 files on deployment targets. If PowerShell Core is installed on those targets, this may change the behaviour of your deployments. If PowerShell Core is not installed on those targets, the deployment will fail.
Build Information
Our build information change involved renaming resources from the API through to the database. This is generally backwards compatible, however anyone using our GitHub issue tracker will need to ensure they upgrade their Octopus Server if they upgrade their Azure DevOps extension, TeamCity plugin, or Bamboo plugin.
Octopus 2019.11
Highlights
Official Jenkins Plugin and Operations Runbooks
- Official Octopus Deploy Jenkins plugin enables teams to integrate their Jenkins builds with Octopus deployments.
- Operations Runbook platform helps teams automate routine maintenance and emergency operations tasks like infrastructure provisioning, database management, and website failover and restoration.
- Familiar configuration process for anyone who has configured a deployment process.
- The ability to execute runbooks directly against infrastructure on-demand or on a schedule (nightly, weekdays, once a month, etc.) as per your team’s needs.
- Runbooks can be parameterized with prompted variables.
- You can make changes to your runbooks with confidence, and only publish them after they have been safely tested.
- Runbooks are managed and executed by Octopus, so this means there’s a complete audit trail that can be reviewed at a later date, making it easy to see what happened, when and why, and if anything needs to be changed.
- You can give your entire team permission to execute your runbooks, without assigning everybody on the team permissions for the infrastructure the runbooks will execute against.
Breaking changes
Octopus API and Octopus.Client
The Octopus API has changed as a part of this release, versions of Octopus.Client before 8.0.0 can not create scheduled triggers on an Octopus Server where the version is older than 2019.11.0.
Release notes
These are the features and fixes you'll get by upgrading from 2019.11.3 to 2019.12.6.
Changes in Octopus Server 2019.12.6
Changes in Octopus Server 2019.12.5
- 6201 - Fixed an issue where pushing a package results in a SQL timeout if you have many large deployment processes
Changes in Octopus Server 2019.12.4
- 6188 - Fix DateTime overflow and year skip in db upgrade schedule conversion
Changes in Octopus Server 2019.12.3
- 6169 - Improved swagger documentation to ensure parameters match the path more accurately
- 6170 - External group/role chips for teams now show ids on hover
- 6171 - Fixed layout issue on Usage tab for Library Variable Sets, Lifecycles and Script Modules
- 6172 - Corrected swagger operationid's to be unique
- 6173 - Enabled issue trackers to use the web proxy configured in Octopus
- 6174 - Fixed issue where sensitive step parameters were cleared when updating step template in a deployment process
- 6175 - Clear sensitive variable values when re-running a step template run so it doesn't look like the value is set
- 6176 - Issue tracker connectivity tests can now execute even when the extension itself is disabled
- 6177 - TFVC ChangeSets are now rendered as links in the Build information
- 6178 - Improved responsiveness of the tenants list screen with missing variables
- 6181 - Fix issue where variables page would crash at certain screen sizes
Changes in Octopus Server 2019.12.2
Changes in Octopus Server 2019.12.1
- 6124 - Scheduled triggers for Operations Runbooks that have prompted variables no longer throw a
NullReferenceException - 6129 - Drop experimental header check on project/summaries to avoid issues with proxies
- 6131 - Fix an issue where Octopus Server would user the tar extractor for tar.gz resulting in Bad GZIP header error messages
- 6132 - Download helm charts directly from a helm repository instead of relying on the helm executable
Changes in Octopus Server 2019.12.0
This LTS roll up release includes all bug fixes and features up until 2019.11.3
- 5769 - Disable adding a new project in the UI when there are no Project Groups or Lifecycles
- 6061 - The target limit specified in the license is enforced now
- 6073 - Fix React Error in container within Kubernetes step
- 6083 - External groups are now indicated on users' teams lists
- 6086 - Fixed layout issue on the User Role tab on the Team Edit page
Changes in Octopus Server 2019.11.3
- 5769 - Disable adding a new project in the UI when there are no Project Groups or Lifecycles
- 6061 - The target limit specified in the license is enforced now
- 6073 - Fix React Error in container within Kubernetes step
- 6083 - External groups are now indicated on users' teams lists
- 6086 - Fixed layout issue on the User Role tab on the Team Edit page