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.3.5 to 3.3.27
Octopus 3.3
New Features in 3.3
- Script-steps can source the script from a package
- Script-steps can execute on the Octopus server without requiring a Tentacle
- Server-based steps (i.e. email, manual-intervention, and the new server-script steps) can be child steps
- Support for zip and tar packages
- OctoPack.js + gulp and grunt wrappers Guide for deploying Node.js
- Azure Service Principal account type
- Azure Resource Group Template step type
- ASP.NET 5 (Sorry, ASP.NET Core) JSON configuration support
- Breaking change: Sensitive Properties have changed to resolve a number of issues on deployment steps and templates, affecting octo.exe, Octopus.Client and the TeamCity plugin (see below for more details)
Read our blog post announcing 3.3
Please Note: you will need to upgrade octo.exe
, Octopus.Client
and the TeamCity plugin when upgrading to Octopus Deploy 3.3
Breaking Change: Sensitive Properties
As part of this release we have resolved a number of minor issues with sensitive properties on deployment steps and step templates. The issues resolved include:
- Windows Service Custom account and password properties no longer retained when switching account types (#2264).
- Sensitive fields in steps can now be cleared/reset (#2311)
- Username/password fields on IIS and Windows Service features will remain visible if account-type/identity is bound to a variable (#2333)
- Sensitive fields now use a consistent UI control across the entire portal.
Breaking Change
This introduces a breaking change to our API, and will affect those using the following endpoints:
/api/deploymentprocesses
/api/actiontemplates
It also affects octo.exe, Octopus.Client and the TeamCity plugin. If you are using any of these components please upgrade them when upgrading to Octopus Deploy 3.3.
See Sensitive Property API Changes in Release 3.3 for more details.
Upgrading
Read the upgrade guide for more details on upgrading from your current version to Octopus 3.3.
Please upgrade octo.exe, Octopus.Client and the TeamCity plugin when upgrading to Octopus Deploy 3.3.
Release notes
These are the features and fixes you'll get by upgrading from 3.3.5 to 3.3.27.
Changes in Octopus Server 3.3.27
Changes in Octopus Server 3.3.26
Changes in Octopus Server 3.3.25
- 2330 - When registering Tentacles, we now have validation to ensure the Tentacle+Server versions are compatible
- 2441 - Added ability to handle long (> 100 characters) paths in .tar files
- 2526 - Added a new permission AuditView to view audit log page (instead of requiring AdministerSystem permission)
- 2536 - Added Azure Key Vault support to Azure Resource Group step
- 2585 - Prevent [enter] on bound fields from showing the variable pop-up
- 2596 - Refresh views to fix schema integrity check failing for some customers
- 2611 - Show configuration menu for users who have audit/team permissions
- 2614 - Handle absolute paths in config transforms
- 2624 - Add additional logging to Tentacle to help diagnose startup issues
Changes in Octopus Server 3.3.24
- 2499 - Clarify help text for skipping previously deployed packages
Changes in Octopus Server 3.3.23
- 2302 - OctoStache update to include variable use in indexer and conditional comparison changes (see issue for usage)
- 2323 - Filter environments shown on the Promote button according to the users permissions
- 2337 - Don't alter variables when sanitizing entered hostnames for IIS bindings
- 2453 - Octopus now supports substituting objects, arrays, boolean and numeric values in JSON files
- 2492 - Octopus now supports substituting properties with colons in their name in JSON files
- 2554 - Azure Web App step now supports specifying Resource Group
- 2573 - Fix running Powershell tasks blocking the Tentacle port if Tentacle restarts
- 2599 - Fix Calamari saving ASCII files as UTF-8 with a BOM when doing substitutions on Linux
- 2604 - Block deletion of Environments that have deployment steps scoped to them, rather than removing the steps
Changes in Octopus Server 3.3.22
Changes in Octopus Server 3.3.21
- 2296 - Allow the Deployments API endpoint to be filtered by ChannelId and return ChannelId in the result
- 2418 - Retention policies now retain the correct number of undeployed Releases for each individual Channel
- 2495 - Fail deployment when an included Script Module has a syntax error
- 2502 - Added ability to pass parameters to custom script files
- 2524 - Fixed an issue with Halibut that would cause Polling Tentacle upgrades to stall/freeze under certain conditions
- 2545 - Set
Octopus.Action.PowerShell.ExecuteWithoutProfile
totrue
on a project to not run the Tentacle service account's PowerShell profile script when running PowerShell script steps - 2569 - Updates to the 'Configure dashboard’ screen to be more user-friendly with long project names
- 2571 - Show projects with running deployments on the dashboard even if they are beyond the 50 project limit
- 2574 - Release and Task screens correctly retain the page selections for lists (e.g. Artifacts and History)
- 2577 - The Octopus VSTS plugin now correctly logs deployment progress when
Show Deployment Progress
is checked - 2580 - Removed the time limit for Azure deployment retries, and set it to always retry 3 times
- 2589 - Tasks that are canceled whilst waiting for other tasks to complete will now cancel when requested
Changes in Octopus Server 3.3.20
- 1872 -
Octopus.Deployment.Error
now contains better information if a parallel step fails - 2332 - Run the Octopus installer from the command line with
RUNMANAGERONEXIT=no
to prevent the Octopus Manager from running - 2527 - Add a note to Azure account selection when a particular Azure account type is required
- 2548 - Always show projects with failing deployments on the dashboard and allow the limit to be changed
- 2557 - Octopus displays a message if queuing a system integrity check fails due to permissions
- 2563 - System integrity check now ignores objects in the sys schema
- 2564 - Ensured all database tables are in the dbo schema even when the creating user has a different default schema
- 2566 - Fixed the population of the events list on the deployment status page
- 2567 - Logged a warning when the result of an XML config transform results in a file without a root node
- 2568 - Made the temporary file creation and deletion on deployment more robust
Changes in Octopus Server 3.3.19
Changes in Octopus Server 3.3.18
- 2475 - Offline deployments now honour retention policies
- 2520 - Prevent Releases being created when a Project is disabled
- 2530 - Calamari fixes for file encoding during variable substitution
- 2533 - Octo.exe now ensures that packageversion, if specified, is a semantic version
- 2542 - Added additional transaction logging to help investigate potential SQL deadlock situations
- 2543 - Calamari no longer crashes if Mono fails while finding earlier packages
- 2544 - Added a system integrity check task that does some basic data and schema validation
- 2546 - Removed performance bottleneck when evaluating variables after all machines have completed a step
- 2553 - Database schema fix for potentially incorrect column length
- 2555 - Fixed an issue where the server would not close SQL connections
Changes in Octopus Server 3.3.17
Changes in Octopus Server 3.3.16
Changes in Octopus Server 3.3.15
Changes in Octopus Server 3.3.14
Warning: Some upgrade scripts in this release may take some time to run. Please account for this when you choose your upgrade window.
- 2347 - Allow Markdown formatting for NuGet package release-notes
- 2400 - Added example of relative path for script file location in package to on-screen documentation
- 2424 - Prevent Octopus working files (e.g.
variables.json
,bootstrap.ps1
, etc) from syncing during Azure deployments. - 2433 - List all Script Modules rather than only the top 30
- 2461 - Allow editing of window size for subsequent parallel steps
- 2472 - Limited the number of projects shown on the dashboard to 50 and added a group and project filter if there are more than 50 projects
- 2503 -
octo.exe
now handles cases where there are more than 30 channels in a project (and a few other cases where we neglected to paginate properly) affectingcreate-channel
,create-release
,deploy-release
,delete-releases
,export
andimport
- 2504 - The breadcrumb link on Configuration pages now redirects to the correct page
- 2505 - Modified the dashboard query to resolve timeouts
- 2510 - Fixed a regression where packages only required on the server in one step, but required on a machine in another step were not being downloaded to the server
- 2511 - Fail cleanly if environment handed to octo.exe clean-environment is not found
- 2515 - Added
poll-server
command to Tentacle to configure polling multiple servers - 2518 - You can now set the
Octopus.Action.PowerShell.CustomPowerShellVersion
variable, and your PowerShell scripts will be invoked with the-version
flag
Changes in Octopus Server 3.3.12
- 2351 - Changed Audit filter behaviour to include results that matched all filters provided
- 2371 - Extended
octo.exe delete-releases
command to accept one or more--channel
parameters - 2373 - Fixed the setting of the
Octopus.Tentacle.Agent.InstanceName
andOctopus.Tentacle.Agent.ProgramDirectoryPath
variables and added theTentacleProgramDirectoryPath
Environment Variable - 2382 - Improved the documentation for the
--environment
option fortentacle.exe register-with
command - 2383 - Correctly show port number for listening Tentacles in the Tentacle Manager and updated path information to hyperlinks
- 2444 - Unnecessary call to /api/reporting/ when rendering /#app/projects
- 2485 - Fixed semaphore access when running multiple instances of Tentacle as different users
- 2489 - Fixed the visibility of the paging control on the User Roles page
- 2493 - Added
octo.exe create-channel
command to make it easier to create channels from build servers for per-branch channels (like feature branches) - 2494 -
octo.exe create-release
command extended to automatically select the best channel for the release, or fail with details on how to create it successfully
Changes in Octopus Server 3.3.11
- 2342 - Guest user not automatically being added to Everyone
- 2409 - Long variables overlay history in release page
- 2436 - Environment restriction from team membership should not override access granted by Administrators membership
- 2459 - Same package in multiple steps downloads package multiple times on Tentacle
- 2464 - Pushing a package with NuGet 3.4 causes a 500 error
- 2465 - The packages api ignores the take and skip parameters
- 2474 - Bug fixes to importer when encountering key-collisions and updating validation logic for frozen deployment processes and variable sets.
- 2481 - Fixed issue with upgrader failing when there are orphaned channels
- 2483 - Tentacle.exe to allow TLS 1.2 comms
- 2484 - Related to 2417 we will automatically fix broken channel references in cloned projects, by linking to a channel with the exact same name, and delete any references which cannot be fixed automatically so you can fix them yourself
Changes in Octopus Server 3.3.10
Changes in Octopus Server 3.3.9
- 2191 - Fixed issue with the client deserializing VariableValues sent from pre-3.1.6 servers
- 2462 - Improved the date bounds checking when determining the creation date of a nupkg or zip archive
- 2466 - Note in the Version validation error message that pre-release tags starting with a number are not allowed
- 2467 - Service deployment fail if directory or service name contains spaces
Changes in Octopus Server 3.3.8
- 2300 - Add new variable
Octopus.Action.Package.InstallationDirectoryPath
as replacement forPackage.InstallationDirectoryPath
- 2438 - Switching a script step from "script in package" to "inline script" should not attempt to download the package
- 2443 - Add support for "No Managed code" for App Pool .NET CLR
- 2446 - Allow parallel SSH tasks to take place on targets with different fingerprints.
- 2451 - Audit event references should be mapped to to the new IDs
- 2452 - When steps are deleted or renamed, the channel rule references to them should update
- 2457 - Bugfix for variables grid not expanding to full width
- 2460 - 3.3.7 Upgrade fails on script steps with sensitive variables
Changes in Octopus Server 3.3.6
- 2434 - Allowing packages deployed to SSH targets to exceed 2GB in size