Changes in 2018.1
See our release blog post for more details.
This January release of Octopus Deploy is primarily a security release driven by Octopus Cloud and will also benefit each of our customers running Octopus Deploy on-premises. We highly recommend upgrading.
You'll also notice our new versioning strategy: what would normally have been Octopus
4.2 is actually
2018.1. Read more about why we changed.
- When installing Octopus Server and using a Custom Windows Account to run the service, the installation wizard will configure SQL Server correctly so the Custom Windows Account can access the database
- Steps may now be explicitly configured to run before or after package acquisition
- The built-in worker, which executes deployment steps and scripts on the Octopus Server, can now be configured to run using a different, lower-privileged user account
- Fix for infrastructure overview not correctly flowing tag sets from associated tenants
- Import using the Octopus migrator finds the correct deployment process for scripts from similarly named projects
- Existing orphaned channels and releases are removed from the database
- The check to see whether a step template is in use is now much quicker
- Environments, channels and tags now cannot be deleted if they are used by a disabled step in a project's current process
- Package notes are fetched in bulk and in async, meaning a release can be deployed without all notes being downloaded first
- The installed version of Octopus Server is now tracked to help us provide support when data issues occur and is a precursor to raising and event on upgrade
Auto machine removal now happens as part of health checks. Minor breaking change API endpoint for machine removal logs is removed and machine removal logs are no longer stored on the Octopus server
All of the usual steps for upgrading Octopus Deploy apply.