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 4.0.11 to 4.1.0
Octopus 4.1
Changes in 4.1
See our release blog post for more details.
New Features
This December release of Octopus continues the support for Java that was introduced back in 3.17, with the ability to export certificates as Java KeyStores, as well as configuring certificates directly within existing Tomcat 7+, WildFly 10+ and Red Hat JBoss EAP 6+ application servers. This release also allows Maven repositories to be configured as external Octopus feeds, meaning Octopus can now consume Maven artifacts as part of a deployment.
Improvements
- Maven repositories as external feeds
- Deployment of Java keystores and configuration of certificates in WildFly, JBoss EAP and Tomcat
- Directories for task logs, artifacts and the package repository are now store as relative paths
Breaking Changes
There are no breaking changes in this release.
Upgrading
All of the usual steps for upgrading Octopus Deploy apply.
Octopus 4.0
Changes in 4.0
New Features
- Modern UI
- New Variable Editor
- New Infrastructure dashboard
- New Deployment page
- New Configuration API and UI
Breaking Changes
- Octopus UI supports now only the latest versions of major web browsers: Internet Explorer 11, Edge, Firefox, Chrome and Safari
- By default Octopus will only attempt to run a step on up to
10deployment targets at the same time, instead of attempting to run on every matching deployment target simultaneously - Removed the
SynchronizationStatusandIndexingStatusproperties returned by the/api/serverstatus/nugetAPI - The
NancyCookie AuthCookieService.CreateAuthCookie()used by custom authentication providers has been replaced withNancyCookie[] AuthCookieService.CreateAuthCookies() - The
--thumbprint-onlyoption has been removed from theOctopus.Server.exe show-thumbprintcommand since it is no longer needed Octopus.Server.exe regenerate-certificatehas been replaced withOctopus.Server.exe new-certificate- Removed previously deprecated
Octopus.Server.exe configureoptions--masterKey,--storageConnectionStringand--webAuthenticationMode. - Authentication provider information is now treated as a resource and served through it's own API
- The
get_octopusvariablebash function now returns an empty string if the variable does not exist - Removed the
/api/letsencryptconfiguration/disableAPI - Removed
ResourceCollection.IsStale - Removed unused properties from the
BuiltInFeedStatsAPI - Removed the
Page.Nentries from theLinkslist of collection responses and replaced them with some alternatives - Auto deploy now always re-deploys the most recent successful deployment
- Root document in Octopus API now returns all links
Upgrading
This release contains a few post-install data fixes that may take some time (depending on the size of your DeploymentProcess and User 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.
As always, read the upgrade guide for more details on upgrading to Octopus 4.0.
Release notes
These are the features and fixes you'll get by upgrading from 4.0.11 to 4.1.0.
Changes in Octopus Server 4.1.0
- 3569 - Added event group
MachineHealthChanged, replacing the event category of the same name - 3652 - Task log, package feed and artifacts folders are now shown in the
show-configurationcommand and in the settings UI - 3846 - Task log, package feed and artifacts folders are stored as relative to the Home directory when they can be, to make moving the folder structure easier
- 3943 - Add support for exporting certificates for Java app servers
- 3944 - Add support for Maven repos as external feeds
- 4023 - F# and ScriptCS support fixed in Azure script steps
- 4030 - Fixed an API exception from occurring when a variable name was null
- 4033 - Fix for audit screen’s default date range not including today
- 4034 - Fix for maintenance mode banner’s transparency problems
- 4035 - All SQL Server and Database management is now performed through a single component for consistency
Changes in Octopus Server 4.0.11
- 3954 - Added the ability to resize columns in the variable editor
- 4010 - Getting started no longer crashes Octopus if the first release is not on one of the first 5 created projects
- 4015 - Introduce a delay between connection retries if the connection to the Tentacle is refused as the Tentacle might not be ready to accept connections just yet. Many thanks to @frese for the contribution!
- 4016 - Updating project overview to include wildcard for finer-scoped EnvironmentView permissions
- 4017 - Removed unnecessary word-breaking CSS that was causing the design to break in various scenarios
- 4020 - Update the mouseover popup on scheduled tasks to display the precise scheduled time, and display the scheduled task time in the tasks table
- 4024 - Added missing option for re-deploying already installed packages
- 4026 - Fix for showing you an error when you have 2 certificates variables with same name and both are missing from the library