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 2018.2.8 to 2018.3.4
Octopus 2018.3
Changes in 2018.3
See our release blog post for more details.
New Features
This month, we've greatly improved our support for infrastructure as code unlocking some incredible deployment automation and infrastructure automation scenarios. Octopus 2018.3 introduces support for GitHub repositories as feeds and first class terraform support as well as some awesome smaller features like Highlight Messages and Artifacts and . Read on for all the exciting details!
Upgrading
This release contains a few post-install data fixes that may take some time (depending on the size of your DeploymentProcess and Events tables), 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.
All of the usual steps for upgrading Octopus Deploy apply.
Octopus 2018.2
Changes in 2018.2
See our release blog post for more details.
New Features
Octopus 2018.2 brings a number of exciting new features including the much requested step to deploy a release, the ability to deploy AWS CloudFormation templates, delete existing CloudFormation stacks, and run scripts with the AWS CLI.
Breaking Changes
If you are using an older version of Octopus.Client.dll to access /api/feeds/all then this will now error. You will need to update to >= 4.30.7 of Octopus.Client. The reason for this is that we have added a new feed type for releases of Octopus projects, to support the new Deploy Release step.
In anticipation of some upcoming new feed types we have hit the point where we were forced to revisit how we expose the packages API for external feeds, and how we store cached packages for deployments. Unless you are hitting the Octopus API directly to search through your external feeds or rely on specific naming of the cached packages, then there should be almost no impact to you. One side effect of the change to package cache names is that the current packages cache on the server and tentacles will be no longer checked so new deloyments will use the new package names. More details about these changes are available in the GitHub tickets "Packages API does not meet the requirements of our expanding feed types #4114" and "Modify the cache naming format to allow for new feed formats #4211".
Upgrading
All of the usual steps for upgrading Octopus Deploy apply.
Release notes
These are the features and fixes you'll get by upgrading from 2018.2.8 to 2018.3.4.
Changes in Octopus Server 2018.3.4
Changes in Octopus Server 2018.3.3
- 4269 - Sort deployment targets by name during rolling deployments so the deployment order is deterministic
- 4309 - Fixed an issue where the tenants page may sometimes fail to load when there is a large number of projects
- 4366 - Fixed exception when downloading packages with 4 part version numbers on SSH targets without mono
- 4367 - Fix for errors incorrectly showing user lacks VariableEdit if that permission was scoped to Projects
- 4368 - Permanently enabled the Docker and Browser Caching features, and multi-tenancy is enabled when a tenant is first created
- 4370 - Increased network timeouts when interacting with Tomcat from 30 to 60 seconds
- 4371 - Terraform steps now include a field to allow a workspace to be defined
Changes in Octopus Server 2018.3.2
- 4369 - Fixed a bug where the dashboard would repeatedly request all releases from the Octopus server, and adversely impact performance
Changes in Octopus Server 2018.3.1
- 4119 - Fixed problem with Variable Editor creating values that can't be saved
- 4218 - Audit log filtering would error in some cases and this is fixed now
- 4234 - Ensuring we can render old releases in project overview
- 4264 - A new log level
Highlighthas been added that highlights the message in the log and shows it on the Task Summary tab - 4275 - Fixed a bug where in some situations, the read only table of variables would extend beyond the available screen width
- 4300 - Added an upgrade script to clean up orphaned channel version rules
- 4307 - Fixed subscriptions and web hooks that were not firing for users who had scoped permissions
- 4308 - Fixed issue when upgrading a system with an
Octopus Managersteam - 4312 - Fixed issue with the AzureAD authentication provider sometimes getting a signature error while validating tokens
- 4314 - Release page navigation links now work regardless of whether the current URL contains a trailing slash
- 4316 - Open markdown links in a new window
- 4322 - Fixed a bug where the tenant tags would be pre-filled on the create deployment page if you had navigated to a create deployment url for deploying to specific tenants
- 4326 - Stop showing a delete option in the UI if you don't have access to view a particular user
- 4332 - Additional error logging is generated for network errors when deploying CloudFormation templates
- 4333 - Fixed error in queueing tasks when 1000's of tasks are ready to run
- 4336 - Add
#{else}to the existing#{if}statement in the variable substitution syntax - 4337 - Artifacts now appear under the step heading on the Task Summary page
- 4339 - Add terraform apply and destroy steps
- 4344 - Cloudformation dynamic variables form does not recognise specilised lists
- 4345 - Cloudformation step will exit early if there are nested stacks
- 4347 - Fixed a bug where the environments filters would disappear if no environments matched the current filter
- 4351 - Fixed an issue where searching through certificates might fail for some types of certificates
- 4352 - Removed redundant call to /api/projects/all from getting-started component
- 4353 - Fixed metrics logging to not use quotes around numbers
- 4356 - Added a field to allow additional files to have variable substitution applied to them from Terraform packages
- 4357 - Additional file extensions are now downloaded from Maven repositories
- 4358 - Null reference exception removed when the AWS region is incorrect
- 4359 - Fix for the error about missing EventView permission on the release page when it is scoped to Projects