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 2.2.1 to 3.4.10
Octopus 3.4
New Features in 3.4
- Multi-tenant deployments
- Improved support for elastic and transient environments
- Cloud Region deployment targets
- Proxy support for Tentacle communications
- Support for F# custom scripts
- SemVer 2 support
- Support for NuGet v3 external package repositories
- Deprecation notice: We are deprecating the Azure Cloud Service and Azure Web App deployment targets. See below for more details.
- Deprecation notice: We are deprecating the
MachineResource.Status
property in favour of the newMachineResource.HealthStatus
property. See below for more details. - Breaking change: We have patched Tentacle to fix a bug when registering new machines with Octopus 3.4. See below for more details.
- Breaking change: We have changed the HTTP Status Code returned when you attempt to push a duplicate package to the built-in package repository. See below for more details.
- Breaking change: Octopus Server now requires a minimum .NET version of 4.5.1. We have changed the minimum required version for the server to enable the SQL connection resiliency features in ADO.NET. The Octopus Tentacles retain their current minimum .NET version.
- Breaking change: If you are using TeamCity NuGet feeds you will need to upgrade to TeamCity 9.0 or newer (Recommend latest due to continual improvements in NuGet feed) or switch to using the Octopus built-in repository. This is due to upgrading our NuGet dependencies to v3 which aren't compatible with the custom v1 feed provided by TeamCity 7.x-8.x. We recommend upgrading to the latest TeamCity version and enabling the v2 NuGet feed API.
- Breaking change: The way pre-release versions are handled in Channel version rules has changed. Previously pre-release versions were treated as greater than the release version. This has now been corrected, and pre-release versions are considered less than release versions. e.g. the version rule
(,1.0]
would have previously excluded1.0.0-alpha
. It will now include it. - Breaking change: The property
PackageSizeBytes
has been moved fromPackageResource
toPackageFromBuiltInFeedResource
. - Breaking change: The property
Octopus.Action.Package.NuGetPackageId
andOctopus.Action.Package.NuGetFeedId
on deployment steps has been changed toOctopus.Action.Package.PackageId
andOctopus.Action.Package.FeedId
to reflect our extended packaging options. Steps that have the old property names will have the values be synchronised with the new properties, however new steps will only set the new properties. - Breaking change: The property
ActivityLog
onTaskDetailsResource
has been renamed toActivityLogs
- Breaking change: The logic for
ScopeSpecification
inOctopus.Client
has moved toScopeScenario
Octopus 3.4 and snapshots - nothing has changed
We recently posted a request for comments on removing snapshots. Don't worry, we haven't changed anything. Deployment snapshots in Octopus 3.4 work just like they did in earlier releases.
You cannot create new Azure Cloud Service nor Azure Web App deployment targets
Starting in Octopus 3.4 you will no longer be able to create new Azure Cloud Service nor Azure Web App deployment targets. Don't worry, you will be able to view and edit any existing Azure deployment targets, and begin migrating them over to the replacement Azure Cloud Service and Azure Web App deployment steps. Here is a guide to help you migrate.
In a future release of Octopus Deploy we will cease support for the Azure Cloud Service and Azure Web App deployment targets, giving you plenty of notice before doing so.
Please note that Azure Cloud Services and Azure Web Apps are still fully supported; we are just changing the way they are implemented.
Changes to health check results
We have introduced a new property MachineResource.HealthStatus
for elastic and transient environments which can be either Healthy
, Unhealthy
, Unavailable
, HasWarnings
and Unknown
. You can continue to use the existing MachineResource.Status
in Octopus 3.4, but we have marked the Status
property as Obsolete
and will be removing it in a future release. The states NeedsUpgrade
and CalamariUpgrade
that were previously overloading the MachineResource.Status
property should now be determined by the pre-existing MachineResource.Endpoint.TentacleVersionDetails.UpgradeSuggested
and MachineResource.HasLatestCalamari
properties respectively.
Registering new Tentacle Instances with Octopus 3.4
Registering a brand new Tentacle instance with Octopus 3.4 will fail if you are using an older version of Tentacle. This happens because old Tentacle doesn't understand Cloud Regions and couldn't deserialize them. We have patched Tentacle to be more resilient to these kinds of changes in the future.
Note: This issue only affects registering new Tentacle Instances with your Octopus Server. Existing Tentacles will continue to work as per normal. Registering a new Tentacle instance on an existing server where Tentacle has previously been installed will also fail until the Tentacle is upgraded to one of the below versions.
- Registering 3.0.x Tentacles (used for older .NET 4.0-only servers): please download Tentacle 3.0.26 which has been patched to work with Octopus 3.4.
- Registering a newer version of Tentacle: please start using the a 3.4.x Tentacle release (we recommend the latest).
Changes to built-in repository error codes
When you push a duplicate package to the built-in package repository we will now respond with HTTP status code 409 Conflict
instead of 400 Bad Request
. Clients like nuget.exe
would only show the HTTP status code, dropping the reason Octopus returned explaining why it was a bad request. Using 409 Conflict
for this situation should make it easier to diagnose. Refer to this GitHub Issue for more information.
Upgrading
Read the upgrade guide for more details on upgrading from your current version to Octopus 3.4.
Using TeamCity NuGet feeds? You will need to upgrade your TeamCity server to v9.0 or newer and enable the NuGet v2 API. Octopus 3.4+ no longer supports the custom NuGet v1 feeds from TeamCity 7.x-8.x. We recommend upgrading to the latest TeamCity version available due to continual improvements in their NuGet feed - or switch to using the Octopus built-in repository.
Want to use SemVer 2 for packages or releases? You will need to upgrade OctoPack and/or octo.exe to 3.4 or newer.
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.
Octopus 3.2
Highlights and new Features of 3.2
Octopus Deploy 3.2 is all about Channels and is a highly-compatible feature release with no breaking changes. Channels is the name we've given to the feature originally discussed in our RFC on Branching.
Build servers build. Octopus deploys.
We decided it was important to drive a distinction between source code branches, which build servers care about, and deployment, which is where Channels come in.
- Read the blog post
- Read the documentation
- Look at the walkthrough
- Try out Channels as a Guest on our demo server
Read the upgrade guide for more details on upgrading from your current version to Octopus 3.2.
Octopus 3.1
Highlights and new Features of 3.1
- Azure support revisited - blog post
- TLS 1.2 (Requires Tentacle 3.1) - blog post
- Reporting - blog post
- Breaking change: Due to the dependency on .NET 4.5 Octopus Server and Tentacle 3.1 are no longer supported on Windows Server 2003 or Server 2008 SP1 - more information
Read the blog post for more details on the changes and features introduced in Octopus 3.1.
Upgrading Tentacles: You can upgrade to Octopus Server 3.1 without upgrading any Tentacles and get all of the new 3.1 deployment features because Calamari will continue to work on both Tentacle 3.0 and 3.1 - more information
Read the upgrade guide for more details on upgrading from your current version to Octopus 3.1.
Octopus 2.6
Highlights of 2.6
- Lifecycles to control promotion and automate deployments
- Automatic release creation from NuGet push
- Running steps in parallel
- Up to 5x faster package uploads
- Skipping offline machines
Read more about it in the blog post
Octopus 2.5
Highlights of 2.5
- Support for scheduled deployments
- Task page improvements including filtering
- Library/step template improvements including typed parameters and usage search
- Maintenance Mode
- Breaking change: All machines in a single deployment must have a unique SQUID (923)
- Breaking change: Octopus will no longer monitor its internal package folder for filesystem changes (900)
- Breaking change: When custom XML config transforms are in use,
*.Release.config
and*.#{Octopus.Environment.Name}.config
must be explicitly added to the list for the order of application to be defined (1037)
Octopus 2.4
Highlights of 2.4
- Step templates allow you to create reusable steps to share between projects
- PowerShell script modules allow you to create common PowerShell functions and use them wherever PowerShell is supported
- Active Directory groups can now be members of teams
- Integrated Windows authentication is supported
- Retention policies for the built-in NuGet repository
- Keep a limited number of backups
- Customize the way the "next release number" is generated
- Breaking change: We only call Deploy.ps1 and friends if they are at the root (details)
- Breaking change: The "Substitute variables in files" feature now runs before XML configuration transforms (details)
Octopus 2.3
Highlights of 2.3
- Prompting for variables at deployment time
- Deploy to specific machines
- Interesting mode for task output
- Audit log filtering
- Task cancellation and performance improvements
Octopus 2.2
No highlights for 2.2
Release notes
These are the features and fixes you'll get by upgrading from 2.2.1 to 3.4.10.
Changes in Octopus Server 3.4.10
- 2669 - Tenant drop down variables from projects and library variable sets now properly displays the default value if one has been set
- 2686 - When deploying using the
Deploy to all
(or theDeploy
on an individual Tenant) option from the Project Overview only include the applicable Tenant(s) - 2748 - Replacing SQL triggers with code-based triggers (to help us track future deadlock issues)
- 2760 - Fixed recursive variable definitions causing a stack overflow
- 2766 - Include variables, scoped variables and all system variable in auto-complete drop-down
- 2774 - Fixed Tentacles not correctly loading custom proxy settings
Changes in Octopus Server 3.4.9
- 2684 - Restore missing variables in binding auto-complete list
- 2749 - Apply health check cleanup per machine policy
- 2751 - Fix child actions which run on the server on behalf of a role not running for all machines
- 2757 - Fixed trigger concurrency exception when automatically deleting multiple machines
Changes in Octopus Server 3.4.8
- 2608 - Set KeepAliveInterval to 30 sec on SSH connections to keep connection to server open during long uploads.
- 2719 - Avoid reading and writing variables at the same time
- 2743 - Project Group selector on the Dashboard now sorts alphanumerically
- 2744 - Log exception stack trace when a deployment action fails
- 2745 - Populate the variables
Octopus.Action.Status.Error
andOctopus.Action.Status.ErrorDetail
when an action running in parallel fails - 2752 - Physical path of IIS Website can be set on OS with PowerShell v2
Changes in Octopus Server 3.4.7
Changes in Octopus Server 3.4.6
- 2661 - Added machine scoping to output variables that are set by a step that runs on the server on behalf of targets
- 2705 - Reduce log level of the high number of transaction message
- 2712 - Now returning the correct HTTP headers when a
401 Unauthorised
response is returned - 2717 - Channels on project overview is now sorted by default channel and then alphabetically
- 2720 - Improved error message when pushing a package to the built in repository with a non-SemVer 2.0.0 compliant version
- 2724 - Health Check Steps now require Target Roles to be specified
Changes in Octopus Server 3.4.5
- 2685 - Tenanted deployments can now progress through lifecycle phases when the minimum environment phase requirement has been satisfied
- 2692 - Removed tenant information from triggers when not applicable
- 2695 - Cascade environment deletion to tenant connections, tenant variables and triggers
- 2713 - Fixed chocolatey packages by adding checksum information to the
chocolateyInstaller.ps1
file - 2715 - Prevent the addition of project variable templates from clearing related tenant variables in some circumstances
Changes in Octopus Server 3.4.4
- 2674 - Prevent incorrect environments from displaying in trigger summary
- 2677 - Added support to set a custom deployment label for Azure cloud service steps
- 2681 - Resolved issue downloading package with SemVer 2.0 versions on Tentacle from file-system feeds
- 2687 - Fixed
FilePathTooLong
exception when extracting NuGet packages where file names contain unicode characters - 2697 - Resolved error deploying packages with SemVer 2.0 versions from remote NuGet feeds
Changes in Octopus Server 3.4.3
- 2676 - Fixed an error that prevented deploying a release when the user is part of a team with Tenant restrictions set
- 2679 -
NuGetPackageId
variable will now be correctly populated for steps after the first deployment step. - 2689 -
Octopus.Client
returnsPackageFromBuiltInFeedResource
instead ofPackageResource
for operations involving the built-in package feed - 2690 - Resolved error executing script
Script0043 - Increase Package Column Widths.sql
during 3.4 upgrade. - 2691 - Reverted changes to
Octopus.Client
that caused manual intervention steps to fail if they were awaiting approval before upgrading to3.4.2
- 2642 - Prevent automatic deployments to tenanted targets when the tenant has been disconnected from the project or environment
- 2643 - Prevent automatic deployments to tenanted or untenanted targets when a project is toggled to only tenanted or untenanted mode
- 2664 - Resolved packages with different SemVer 2.0 metadata conflicting
- 2665 - Reimplemented OctopusSuppressNestedScriptWarning variable
- 2666 - Log a friendlier message if the health status of a machine is null when running our DB migrations
- 2670 - Resolved issue downloading NuGet packages with 4-part versions from file-system feeds.
Changes in Octopus Server 3.4.1
- 2372 - Automatic Release Creation settings will no longer be hidden if they have values
- 2648 - Fixed an issue with VSTS/TFS creating releases
- 2650 - Link to deployment triggers troubleshooting documentation is now more pronounced
- 2652 - Update Step Template variables to use new generic package variable names
- 2654 - Project triggers can be accessed with
ProcessView
andProcessEdit
permissions rather thanProjectEdit
permissions - 2657 - Fixing edge case in auto-deploy regarding skipped deployment steps
- 2658 - Ensure
TenantView
permission is given to all built-in project roles - 2659 -
Tenants
andTenantTags
fields are now visible in the TeamCity plugin - 2660 - Fixed a bug which prevented editing Accounts if the multi-tenant deployments feature was not enabled
Changes in Octopus Server 3.4.0
- 1963 - You can now manage tenants and tenanted deployments with Octopus Deploy
- 2246 - Fixed issues around event table deadlocks
- 2295 - Releases by channels are now shaded appropriately by channel on the project dashboard
- 2367 - Octopus Server now requires a minimum .NET version of 4.5.1, to enable the SQL connection resiliency features in ADO.NET, Tentacles have not changed
- 2401 - Warning we will deprecate Azure Targets in 3.4
- 2419 - Octopus Server now returns
409 Conflict
instead of400 Bad Request
when pushing duplicate package to the built-in package feed - 2422 - Upgrade to WebDeploy 3.6
- 2428 - Upgrade NuGet libraries to 3.0
- 2440 - Cloud Region target type
- 2445 - You can now manage elastic and transient environments more easily with Octopus Deploy
- 2479 - Improvements around SQL query plan caching
- 2490 - Expanded proxy support to allow proxies in Tentacle communications
- 2644 - Support for SSH connection through proxies
- 2517 - Support SemVer 2.0
- 2538 - ScriptCS scripts work now on Win 2012 R2 when FIPS is enabled, ScriptCS has been updated to version 0.16.1 which works only on Mono >= 4.0
- 2549 - You can now write custom scripts using F# (
.fsx
) - 2565 - Update to Tentacle registration to account for new MachineResources changes
- 2594 - Project overview dashboard filtering, grouping and empty state improvements
- 2597 - Only download a package once on a machine when it is used multiple times
- 2602 - Remove project permission restrictions on health checks for environments
- 2609 - Updated Azure PowerShell modules to version 1.6.0
- 2613 - [DeployedBy] field on [Deployment] set to non nullable and deployment will fail if instigating user is undefined
Changes in Octopus Server 3.4.0-beta0001
- 1963 - You can now manage tenants and tenanted deployments with Octopus Deploy
- 2246 - Fixed issues around event table deadlocks
- 2422 - Upgrade to WebDeploy 3.6
- 2440 - Cloud Region target type
- 2445 - You can now manage elastic and transient environments more easily with Octopus Deploy
- 2479 - Improved around SQL query plan caching
- 2490 - Expanded proxy support to allow proxies in Tentacle communications
- 2538 - ScriptCS scripts work now on Win 2012 R2 when FIPS is enabled, ScriptCS has been updated to version 0.16.1 which works only on Mono >= 4.0
- 2565 - Update to Tentacle registration to account for new MachineResources changes
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
Changes in Octopus Server 3.3.5
Changes in Octopus Server 3.3.4
- 2278 - An additional warning will be logged if a release is not automatically created due to the package version being the greatest/maximum
- 2312 - Variables link not added to Deployment resource if variable-set is no longer available.
- 2396 - Configured scripts in package steps now support Unicode characters.
- 2399 - Importing scripts now succeeds even if the project has the same name as something else (such as lifecycle or project group)
- 2429 - Tentacle Manager now supports all TLS versions
- 2430 - Task start time displayed on hover incorrectly shows queued time rather than start time
- 2431 - The “Run on” radio button in a script template step now retains its selection after updating to a new version of the template
- 2437 - Fixed a bug that broke Project cloning in certain circumstances with an
ArgumentNullException
Changes in Octopus Server 3.3.3
- 2392 - You can now configure your Authentication Mode (Username/Password or Active Directory) when adding a node to an Octopus HA cluster using the wizard
- 2403 - You can now choose whether to use Timestamp or Checksum for WebDeploy to Azure Web App, and the default has been changed to Timestamp when creating new Azure Web App steps
- 2415 - When creating a deployment channels will now be taken into account when validating the deployment process
- 2417 - When cloning a Project the Channels will now be correctly re-mapped for Project Variables and Automatic Release Creation
- 2423 - Fixed an issue that prevented you from saving Azure Web App deployment targets with the error
'Web Space' should not be empty
- 2426 - Prevent integer-overflow error during long-running Azure Resource Group deployments.
- 2427 -
Octo.exe
Update channels information in steps that have been scoped to a channel when importing a project
Changes in Octopus Server 3.3.2
- 2391 - Add missing repositories (
Channels
,Accounts
,Retention Policies
,Defects
andServer Nodes
) toOctopusRepository
inOctopus.Client
- 2404 - Fix Javascript error preventing uploading of custom Azure Resource Manager certificates
- 2405 - Removed paging from channels so that more than 30 can be used at a time
- 2407 - Allow script steps that run on the server to be run across roles as a standalone step or as the first action in a rolling deployment
- 2410 -
Octo.exe
Import and export project channels when running the projectimport
andexport
commands - 2411 - Add
push
command toOcto.exe
and apush package
build runner to the Octopus Deploy TeamCity plugin - 2412 - When the NuGetFeed for a Package Step is set to a channel-scoped variable, it will now be resolved correctly when creating a release in those channels
- 2414 - Adds support for TLS protocols for Octo.exe to communicate with TLS-only installations of Octopus Server
Changes in Octopus Server 3.3.1
- 2376 - Fixed scenarios that were failing when the host server is required to be FIPS 140 compliant
- 2390 - On-screen help text added to Azure PowerShell step explaining Service Management cmdlets can't be used with Service Principal accounts and Resource Manager cmdlets can't be used with Management Certificate accounts
- 2395 - Immediately executing code in Script Modules now have access to Octopus Variables
- 2398 - Exporting a step template is now prevented until any changes are saved
- 2402 - Fixed an issue that was preventing Calamari from updating on multiple SSH endpoints due to a file lock
Changes in Octopus Server 3.3.0
- 641 - Email, Manual Steps and Azure Powershell steps can now be executed in a rolling step. Also added support to run a PowerShell Script on the Octopus Server.
- 2069 - Enable Azure Active Directory auth for Azure Accounts
- 2091 - Show warning if file is missing during config transformation
- 2133 - Azure Resource Group deployment step type
- 2183 - Support .zip and .tar.gz package formats
- 2189 - Script step embedded in a NuGet package
- 2304 - Support for ASP.NET Core
Changes in Octopus Server 3.3.0-beta0002
- 2345 - Corrected instructions for pushing packages via the api to the built-in repository
- 2354 - Improve the error message when using the JSON config feature and a folder is specified as the target file
- 2355 - Delete parameters that have been renamed/removed from the action properties collection
- 2356 - The selected Resource Group in the “Deploy an Azure Resource Group” step now binds correctly when editing an existing step
- 2357 - The display of long parameter names for Azure Resource Manager templates will now wrap instead of overflowing underneath the input control
- 2359 - The display of Web Apps in the select list has been updated to display the Region and Resource Group (where available)
- 2363 - The http://ASP.NET|ASP.NET Core JSON AppSettings feature is now the JSON configuration variables feature
- 2364 - JSON config feature only replaces variables it can find instead of inserting all available project variables
- 2374 - Invoke
Set-AzureRmContext
when authenticating with service-principal
Changes in Octopus Server 3.2.24
- 2231 - The Active Directory user groups cache will now be invalidated for a user when they explicitly Sign Out from the Octopus Server, forcing a foreground refresh on their next Sign In
- 2318 - Added ability to delete Octopus Server high-availability nodes via the API
- 2334 - The Octopus data importer/migrator is now more reliable when detecting duplicate historical data with key collisions
- 2362 - Updated the Octopus Server node screen to properly report task counts
- 2384 - Fixed open redirect bug in the Octopus web portal integrated authentication process
Changes in Octopus Server 3.2.23
- 2288 - Audit page date selector now displays correctly
- 2298 - Changes made to certain documents will now show correctly in the audit log
- 2324 -
.bmp
logos can now be migrated from previous versions of Octopus - 2325 - Octopus Server will now send the
X-Frame-Options: DENY
HTTP header, which can be overridden by changing thexFrameOptionAllowFrom
configuration value - 2338 - The migration process is now split into two stages, the first to import data, and the second to import task logs, making it easier to migrate very large backups from previous versions of Octopus
- 2353 - You can now provide the
--nooverwrite
parameter formigrator.exe
to skip existing documents - 2358 - Retention policy for custom versions of Calamari will no longer delete the active version
- 2360 - You can now use
octo.exe
to list and clean machines that are in a particular state in an environment which is useful for cleaning up cloud/transient/ephemeral machines that areOffline
Changes in Octopus Server 3.2.22
- 2255 - Child steps now display their status correctly when they have errors or warnings.
- 2266 - Tentacle upgrade process now displays and handles errors and warnings correctly.
- 2280 -
octo.exe
imports with validation errors now return a non-zero exit code - 2281 - Provide
--nologs
and--onlylogs
option for migrator process to seperate loading raw task logs from main server data for increased performance - 2336 - Variable expressions are now correctly persisted for sensitive fields in step templates.
Changes in Octopus Server 3.2.21
- 2279 - Package Cache Retention Policy now removes
.octosig
and.octodelta
files - 2303 - Fix bug when user provided variables that are made up of output variables are accessed in later steps.
- 2316 - Now using new
SHA2
Code Signing Certificate and signing installers/assemblies usingSHA256
algorithm. - 2319 - Removed limitations on a number of queries that would stop running when the related document count exceeded 2100 documents.
- 2327 - Only test for permission changes to environments used in an existing variable set scope when that variable set is updated.
- 2328 - Fixed an edge case where config transforms were being run twice.
Changes in Octopus Server 3.2.20
Changes in Octopus Server 3.2.19
- 2282 - Octopus Migrator now imports
Release
that were associated with deleted variable sets - 2291 - Add special variables
OctopusSkipFreeDiskSpaceCheck
andOctopusFreeDiskSpaceOverrideInMegaBytes
to allow for skipping the free disk space check and to specify a custom free space threshold. - 2293 - Correct the documentation link for channel version rule tags on the Design Rule dialog
- 2299 - Fixed issue with new Tentacle upgrade button on connectivity page
Changes in Octopus Server 3.2.17
- 2126 - Added Verbose Logging when duplicate variables exist between Step Template vars and Project/VariableSet vars.
- 2237 - Provide mechanism to lock current Tentacle version in place and dismiss upgrade reminder.
- 2243 - Add retention policy for old Calamari versions when upgrading to a new version.
- 2251 - Environment list in variable scope selection and on dashboard configuration page sorted as per environment sort order.
- 2254 - Updated
octo.exe
octopus.client library to work with the latest release - 2276 - Removed a limitation on the number of deployments that can be created/displayed for a release.
- 2277 - Increase default SQL connection timeout to mitigate transaction commit timeouts.
- 2285 - Channel variables made available to release version template
- 2286 - Removed a restriction that prevented config transform files from being applied to multiple target files (eg
transform.config => *.config
). - 2287 - Added paging to the task queue in the task summary view.
- 2289 - Removed timeout from manual intervention steps that are a part of a scheduled deployment.
Changes in Octopus Server 3.2.16
- 2030 - Keep deep link context when using integrated Windows authentication.
- 2166 - Change step rule to only check for
[]
characters if the step is new or the name has changed. - 2214 - Increased delete performance when deleting documents that may be used in variable sets or deployment processes.
- 2244 - Total deployment time in deployment with manual interventions now reflect the entire duration of the deployment instead of just for the steps that come after the manual intervention.
- 2261 - Fixed bug where un-scoped variables were being used during when action variables were being evaluated for 'committing' for use in subsequent actions.
- 2269 - Reduced the time required to render the Environments page.
- 2271 - Improved duplicate release checks when importing Octopus 2.6 backups
- 2273 - Create release page is now usable again while loading packages from the NuGet feed.
Changes in Octopus Server 3.2.15
What happened to 3.2.14? It was discovered that a Tentacle communication compatibility bug was introduced with this release that resulted in Tentacles not being able to communicate with Octopus Servers of version 3.2.13 or earlier so we decided to pull this release and go straight to 3.2.15 to avoid confusion.
- 2248 - Allow promoting a release that has been rescheduled to an earlier phase
- 2249 - Export process is now more resilient when saving files to disk.
- 2252 - Add missing calendar icon to date range picker on the Audit page
- 2263 - Fail early with a more helpful message, with a couple of solutions, if we cannot load the
WebAdministration
module inOctopus.Features.IISWebSite_BeforePostDeploy.ps1
- 2268 - Fix display issue in PS 2.0 when logging IIS bindings.
- 2272 - Resolved Tentacle communication incompatibility introduced in 3.2.14
Changes in 3.2.14
- 1977 - Updated default Tentacle connection timeouts. Handling for the scenario where all pooled connections for a Tentacle are bad.
- 2122 - Fix error message display issue when uploading a NuGet package in Firefox
- 2206 - Updating project variables while the user's environment permissions have changed forces user to reload. This blocks a bug causing variables to be removed.
- 2236 - Allow config transforms when the target file is in a relative path:
Web.Base.config => config\Web.Config
- 2247 - Link to document in audit events for lifecycles, library variable sets and step templates are now correctly created.
- 2257 - Enabled wildcard config transforms for relative paths:
transform\*.config => config\*.config
- 2258 - Changed the behaviour for config transforms when the the transform definition is a wildcard and the target file is explicit:
*.bar.config => foo.config
will apply all transforms with the suffix.bar.config
tofoo.config
. - 2267 - Resolved bug with VariableSetId columns not being long enough for migrated data.
Changes in Octopus Server 3.2.13
- 2170 - Allow updating Azure cloud service configuration values to a blank value
- 2225 - Fixed script step editor so it can insert variables again
- 2227 - Check if a swap is possible from Staging to Production before running any of package extract / upload / deploy conventions.
- 2235 - [Octo.exe] Add channel option to the deploy-release command to allow deploying the latest release in a channel
- 2238 - No channel will be assigned when migrating a release that has no project id
- 2240 - Channel rule designer only requires
ProcessView
permission
Changes in Octopus Server 3.2.12
- 2192 - Show Deploy button on project overview dashboard for environments not deployed to
- 2216 - Add individual step failure errors if multiple child steps exist within an action
- 2219 - Additional logging when assigning a web site to an application pool
- 2233 -
Octo.exe
will load additional parameters from a file when the--configFile
parameter is passed
Changes in Octopus Server 3.2.11
- 2046 - Show unsaved changes dialog if you try to move away from the editor after updating a step template
- 2071 - Allow using the Azure account name instead of account Id when binding to a variable expression.
- 2104 - Include output variables that apply to the action in the variable pop-up
- 2196 - Octopus is now FIPS compliant
- 2198 - Now supports
-name
parameter fornew_octopusartifact
on ssh targets - 2201 - EnableMSDeployAppOffline support for Azure Web Apps
- 2204 - Return 403 error message when NuGet push is missing permissions.
- 2205 - Guided failure mode now covers Package Acquisition and Retention steps in addition to your normal steps in the deployment process.
- 2215 - Members of teams restricted to specific environments can deploy to specific machines within those environments
- 2223 - All in-code references to
Cancelled
have been renamed toCanceled
to prevent tasks getting set with the wrong state. - 2224 - Tasks that are cancelled by the user don't turn into failures when child tasks throw exceptions as a result of the forced cancellation.
- 2226 - Deployments with parallel steps including one that fails and one manual intervention now execute without problems.
- 2228 - Allow non administrators to view server node list. This fixes permission error on the task page.
- 2229 - IIS app pool credentials are cleared if the selected identity is not a custom user.
- 2230 - Allow users with
ActionTemplateView
permission to view the content of step templates
Changes in Octopus Server 3.2.10
- 2008 - Server affinity is no longer required for High Availability servers behind a load balancer
- 2182 - Support logging in to multiple Octopus Server instances at the same time
- 2190 - Health check fall back for machines that have mapped NFS drives
- 2194 - Only accept HTTP verb
GET
requests to static/app
route. Other methods will return405 - Method Not Allowed
- 2197 - Fixed a
SqlConnection
leak as reported by one customer. - 2213 - Add back ability to prevent deleting packaged and custom scripts
- 2221 - IIS bindings with empty IP address field will once again bind to *
- 2222 - Fix positioning of variables pop-up so it doesn't extend outside the page width
Changes in Octopus Server 3.2.9
Changes in Octopus Server 3.2.8
- 1883 - Variable editor doesn't delete rows if the delete key is pressed while filtering.
- 2068 - Added option to test Azure account from the account edit screen
- 2172 - Pagination on project releases page works correctly when filtering by channel
- 2184 - Allow service executable arguments to contain spaces
- 2186 - Reconfigure the Octopus Server Windows Service after upgrading to ensure it is correctly configured
- 2199 - Improved readability when logging extracted Cloud Service package contents
Changes in Octopus Server 3.2.7
- 1608 - Do not show deployments that have been cancelled before they start on the dashboard
- 2007 - Allow service account selection when setting up a High Availability node
- 2087 - Fixed warning when creating database mutex table
- 2089 - Accounts page displays environments scoped to accounts
- 2162 - Eliminated performance impact of reading and writing large task log files
- 2174 - Fixed an issue with Calamari that would fail to load
System.Core
when using PowerShell 2.0 and .NET 2.0 - 2179 - Extend the
Account
andFeed
tableId
columns to allow for the fact that they are made by combining the type with theName
. - 2185 - Fixed package download permissions when package is not used in any projects
Changes in Octopus Server 3.2.6
- 1894 - Downloading packages from built-in NuGet repository only requires permissions to one project that uses the package
- 1934 - User auto complete uses
Username
orDisplayname
during search. Search now also uses Unicode character folding. - 1936 - The projects drop-down menu is now scrollable like it was in
2.x
. - 2011 - Resolved UI issue with API key being lost when clicking off the dialog
- 2168 - Now logging a warning when
OctopusPrintVariables
orOctopusPrintEvaluatedVariables
areTrue
since they should only be used when debugging problems with variables - 2178 - Resolved issue introduced in 3.2.5 with sensitive-variables resolving to incorrect values in PowerShell scripts.
Changes in Octopus Server 3.2.4
- 1425 - Interruptions no longer link to a non-existant view
- 1800 - SSH Targets now support creating artifacts on Mac OSX.
- 1891 - Include
Octopus.Release.CurrentForEnvironment
to deployment variables based on the release of the already providedOctopus.Deployment.PreviousSuccessful
- 1956 - Variable filters are now case-insensitive and look for the filter value anywhere within the column values.
- 1978 - Allow replacement of existing packages when pushing via NuGet push
- 1994 - Octopus API to retrieve deployments by release correctly supports skip
- 2018 - Tasks with error messages cause parent tasks/nodes to also be in a error state.
- 2027 - Show ReleaseDelete and ProjectDelete buttons if user has appropriate role with no project scoping.
- 2057 -
InvalidOperationException
thrown to prevent service crash if variable parsing discovers a self referencing loop . - 2072 - Re-implement ability to filter deployments by task state
- 2075 -
Assigned to:
field on theTask Summary
tab now shows the user that has been assigned to the manual intervention. - 2103 - When updating 32-bit Tentacles on 64-bit OSs it installs the 64-bit Tentacle so we update the Windows Service executable path to point the new installation location.
- 2105 - Log when variable substitution fails in custom scripts or file substitution during deployment.
- 2109 - Recording the final state of a Deployment is now more tolerant of transient faults
- 2117 - Prevent installing 32-bit Tentacle on 64-bit OS and update Windows Service executable path to prevent issues when upgrading 32-bit Tentacles on 64-bit OSs
- 2125 - Importing projects without channels into an Octopus Server that has channels will create a default channel for the imported projects
- 2140 - Warn if non-printable characters entered in variables
- 2145 - Upgrading polling Tentacles from UI no longer hangs the upgrade task.
- 2149 - Resolved issue with Azure deployments leaving extracted package in
C:\Windows\System32\config\AppData\Local\Calamari.Azure\Temp
. This was affecting 3.0 style Azure targets. - 2150 - Tentacle upgrader now looks for the Tentacle bundled package in the right directory even if a custom Calamari folder has been set.
- 2151 - Fixed a backwards-compatibility bug affecting IIS HTTPS bindings and their Certificates.
- 2152 - Resolved: SSH deploys should not block Azure deploys
- 2157 - Artifacts are correctly imported from 2.6 backups
- 2158 - The
octo.exe --channel
argument is now case-insensitive, sodefault
will matchDefault
- 2159 - Deleting a release now removes any linked variable or deployment process snapshots so long as they aren't shared by another release
- 2160 -
octo.exe
no longer fails when specifying the--channel
argument for a Channel that has any Version Rules with a blank/emptyVersion Range
. - 2161 - Changed
OctopusTools
NuGet package to be a tools-only package, movingocto.exe
into thetools
folder, which means you can also runocto.exe
from inside Visual Studio. - 2171 - Calamari now logs the
$PSVersionTable
(verbose) to help with debugging PowerShell scripts
Changes in Octopus Server 3.2.3
- 1738 - IISBindings now support IPv6 addresses
- 1882 - Prevent saving Steps with
[
or]
in the name which would otherwise cause Output Variables to stop working for that Step. - 1898 - Task type filter is not cut off by other page elements.
- 1903 - Cancelling the lifecycle-select dialog no longer persists changes.
- 2017 - Using project variables in release version template now works with automatic-release-creation.
- 2024 - Allow migrator to import step scripts where one step name may be a sub path of another
- 2025 - Support for parentheses in variable names
- 2050 - Allow exporting and importing gifs
- 2067 - Now prevents deleting an Environment that is referenced by an Account.
- 2081 - Resolved issue saving empty sensitive variables
- 2085 - Allow creating a release before creating an environment without resulting in error
- 2092 - IIS App Pool Password shown in UI if custom expression is used
- 2100 - Updated OctopusTools (
octo.exe
) so it can be added to a project using NuGet 3 - shout out to @shaynevanasperen for the contribution. - 2101 - Variable substitution breaks if target file has a variable with the character "~" on the name
- 2114 - Octopus incorrectly claims Calamari is not up to date in Tentacles
- 2120 - Corrected minor typo on lifecycle edit page.
- 2123 - Corrected self-link for events in REST API
- 2124 - Fixed an issue in Calamari that prevented using a
CustomInstallationDirectory
with$
in the path. - 2127 - Added reason why the Machine Communication Style cannot be updated after the Machine has been added.
- 2129 - Improved validation message displayed when providing an invalid Semantic Version when creating a Release.
- 2130 - Proxy configuration for Octopus Server and Tentacle now clears the username/password appropriately when selecting
Do not use a proxy
orUse the proxy server configured in Internet Explorer
. - 2132 - Task log when deploying Azure Web App lists all targets in environment
- 2136 - Show calamari version in health check
- 2141 - When deleting an Environment or Channel they will be correctly removed from the
Limited to Environments
andLimited to Channels
of relevant Steps in Deployment Processes. - 2142 - Fixed a bug that stopped the Built-In Package Feed retention policy from working correctly:
System.IndexOutOfRangeException: Release_ChannelId
- 2143 - Allowed Tentacle certificate export to file to work without an instance specified.
- 2146 - Environments in project overview are sorted consistently with the main dashboard.
- 2148 - Only invalid or missing credentials should return 401 so that a login redirect can automatically take place. Any permissions related issues should return 403.
Changes in Octopus Server 3.2.2
- 2003 - Added Support for Release Matrix Sparseboard
- 2065 - Offline Drop script fixes for PowerShell 2.0
- 2088 - Now showing a more informative message when attempting to delete a Script Module that is used by one or more Projects.
- 2134 -
Tentacle.exe register-with
handshake request no longer throws an exception if we successfully connect to Octopus - 2135 - Fix bug causing
DeployFailed.ps1
to always execute (if present) regardless of failure state - 2139 - Calamari now falls back to use
AesManaged
to decrypt sensitive variables ifAesCryptoServiceProvider
is not available from PowerShell.
Changes in Octopus Server 3.2.1
- 1529 - Variable snapshots will be used when resolving packages for an existing release
- 1952 - Calamari semaphores should now be more globally accessible by prepending the
Global\
name prefix - 1974 - Inserting a variable into script as the last action before saving will persist the changes correctly
- 2010 - Users missing MachineView permission can still deploy a release however without any specific machine related functionality.
- 2049 - Registering a polling Tentacle via Tentacle Manager will fail when it cannot reach the Octopus Server communications port
- 2059 - When performing server side retention policy, the deployment information is loaded in batches to avoid hitting
SQL Max 2100 parameters
exception. - 2070 - Importing a pfx for Azure accounts with no private key included will fail with message before persisting.
- 2080 - Bugfix for JS script error caused by race condition on deployment page
- 2095 - Dropdown controls with default values now show the default value instead of showing the control as being bound
- 2098 - Users can now Promote to Environment when their team is scoped to environments
- 2116 - Enable TLS 1.1 and 1.2 https connections from the Octopus Server.
Changes in Octopus Server 3.2.0
- 1503 - A Lifecycle can be specified when creating a project with
Octo.exe
- 1534 - Prompted variables can be specified by name or label when deploying a release using
Octo.exe
- 1613 - Fixed misleading help text in Octopus TeamCity plugin
- 1931 - Fixed error message in
Octo.exe
that referenced Project Group instead of Lifecycle - 1957 - Channels feature. 'Channels' is the name we've given to the set of features discussed in our branching RFC. See our Release 3.2 blog post for more information.
- 2034 - Lifecycles with no phase or empty phases will correctly restrict permissions for users who do not have access to environments in those lifecycles
- 2108 - Updated
Octopus.Client.nupkg
to correctly depend onNewtonsoft.Json 7.0.1
. - 2110 - Tentacle Health Checks will no longer fail on non-English Windows machines when testing for membership in the Built-in Administrators role.
- 2111 - Link to environments page in Calamari upgrade message on deployment creation page is now correct.
Changes in Octopus Server 3.1.7
- 1890 - By default bind Tentacles to both IPv6 and IPv4 address to allow communication over both protocols
- 2106 - File operation errors (such as copying files) will fail the deployment
- 2107 - Removed
useDefaultProxyCredentials
from config file which was causing Calamari to crash upon starting under mono.
Changes in Octopus Server 3.1.6
- 1626 - Display a warning when deploying a release and relevant library variables have changed
- 1660 - Allow updating outdated Calamari versions from the
Environments
page - 2000 - UI Redirects to login if any AJAX request comes back with 401
- 2023 - Tentacle automatic update now works when Tentacle is running as an Active Directory user
- 2028 - Make Octopus Server and Calamari version visible in the ServerTask logs
- 2052 -
DeployFailed.ps1
rollback convention will be run when a package fails to deploy - 2058 - Cannot find type AesCryptoServiceProvider in WindowsService_AfterPreDeploy.ps1
- 2060 - Fixed recursive variable substitution inside
#{each}
blocks. - 2090 - Added locking to prevent errors with multiple packages in offline drops
- 2097 - Now loading
AesCryptoServiceProvider
more reliably in PowerShell scripts to decrypt sensitive variables. - 2102 - Now consistently uses the system default proxy credentials for outbound HTTP requests for Octopus Server, Octopus/Tentacle Managers, and Calamari.
Changes in Octopus Server 3.1.5
- 1961 - Team can now be deleted if they once was responsible for a manual step but they are no longer responsible
- 1998 - Prevent file locking errors when unpacking Calamari while running Azure steps in parallel
- 2054 - Use local Azure profile to avoid file locking when running Azure steps in parallel
- 2063 - Wrap machine names when previewing a deployment.
- 2076 - Use a local Azure profile to prevent using a cached Azure profile that may be invalid
- 2077 - External NuGet feed name will validate the correct number of characters
- 2078 - Added variables for retrieving the time:
Octopus.Time.Hour
,Octopus.Time.Minute
,Octopus.Time.Second
- 2083 - Don't allow retention policy to remove directories of deployments if they are also used by another retained deployment.
Changes in Octopus Server 3.1.4
- 1971 - Integrated Windows (Active Directory) authentication now works if Octopus is setup in a virtual directory
- 2001 - Improved Integrated Windows (Active Directory) sign in performance while improving resilience to Active Directory server performance issues and other failures.
- 2047 - Upload full package immediately if delta compression has been disabled.
- 2055 - Deployment Steps are now correctly filtered when validating the Azure Accounts involved in deploying a Release to a particular Environment
- 2060 - Fixed recursive variable substitution inside
#{each}
blocks.
Changes in Octopus Server 3.1.3
- 2013 - Prevent multiple Octopus installations from unintentionally exceeding license limits
- 2014 - Manually entering schedule date now correctly schedules a deployment in IE11
- 2016 - When adding roles to a team the
Add
button is now shown once a role is selected. - 2019 - Deletions from octo.exe or client now audited and will be displayed in the audit trail
- 2029 - Database migrations will be applied to the correct schema
- 2031 - Don't enforce that AccountId exists on cloud service step when migrating from 2.6
- 2032 - Bring back support for config transform files in subfolders
- 2033 - Selecting script syntax now selects the syntax you chose
- 2037 - Only show machines that are part of the deployment in the package acquisition task log
- 2043 - Update syntax higlighting mode for the script editor when the user changes script syntax
Changes in Octopus Server 3.1.2
- 1582 - IIS bindings preserved (i.e. not removed and re-added) if no changes required.
- 2020 - Now prevents creating a
Machine
with noUri
via the API and prevents server from crashing on startup if there are invalidMachines
- 2021 - Allow the database upgrade script that added the
DeployedBy
column to be run multiple times as a workaround for some customers. Also increased the database operation timeout to the maximum to allow more time for these scripts to succeed. - 2022 - Fixed a typo in the Windows Service feature page
Changes in Octopus Server 3.1.1
- 2005 - Resolved issue with PowerShell 2.0 and sensitive-variables
- 2006 - Fixed issue with Azure process now allows a deployment with no machines targeted
- 2012 - Account to target Environment restrictions now correctly allow Accounts to be used in deployments to "Any Environment", specified by leaving the Account Environments setting empty
Changes in Octopus Server 3.1.0
- 1617 - Added reporting capability as per http://docs.octopusdeploy.com/display/OD/Reporting
- 1801 - Limit the number of tasks that can be run in parallel per Octopus Server node (defaults to 5)
- 1803 - Created specific Azure Step Types as per http://octopusdeploy.com/blog/azure-changes
- 1843 - Added configuration section for managing Octopus Server High Availability nodes as per http://docs.octopusdeploy.com/display/OD/High+Availability
- 1873 - Reduced the size of Calamari by splitting the Azure functionality into a separate
Calamari.Azure
package - 1884 - Tentacle Upgrades can now be performed using the UI like they were in Octopus 2
- 1902 - Octopus Server and Tentacle now support TLS 1.2 which requires .NET 4.5
- 1914 - Allow setting physical path when deploying Azure Web Apps allowing you to deploy to a subfolder of the web site.
- 1925 - Tasks can be filtered by the Octopus Server node that is assigned to the task
- 1926 - Active tasks on the Tasks page are now filtered by the task filters
- 1928 - Added a url for load balancers that will return 200 when an Octopus Server node is not in maintenance mode
- 1985 - Provide a configuration setting to allow Azure PowerShell module to be loaded from installed location, rather than the version packaged with Calamari.
Changes in Octopus Server 3.0.26
- 2565 -
Tentacle.exe register-with
copes better with machine model changes
Changes in Octopus Server 3.0.24
- 1937 - Relax license enforcement
- 1955 - Windows Service and IIS App Pool Custom Account Passwords are now treated correctly as Sensitive values by default.
- 1984 - Custom Expressions now save correctly for Windows Service and IIS App Pool Custom Account Password values.
- 1986 - Removed duplicate
-variables
argument from offline drop PowerShell script. - 1988 - The OfflineDrop
.cmd
file now executes the.ps1
file in the local folder instead of incorrectly targeting the path where the package was built.
Changes in Octopus Server 3.0.23
Changes in Octopus Server 3.0.22
- 1900 - Added the variable
Octopus.Acquire.DeltaCompressionEnabled
to toggle delta compression when sending packages
Changes in Octopus Server 3.0.21
- 1559 - Better sanitization of IIS Host Binding
- 1581 - IIS binding correctly replaces SSL certificates
- 1833 - Fixed a bug in how we decide which retention policy to apply to files on Tentacles during a deployment
- 1837 - Added a command to set file paths for NuGet repository, artifacts and task logs
- 1841 - Fix rendering issues in Edge
- 1945 - Prevent running duplicate configuration transforms due to case of transform file-name
- 1958 - Remove task queue timeout for all but scheduled tasks
- 1960 - Improved handling for missing
bin
directory issue when copying to custom installation directory.
Changes in Octopus Server 3.0.20
- 932 - Step and step template edit pages now prompt for unsaved changes
- 1619 - Step template to clean configuration transform files will now prevent null Path error if no matching files were found
- 1794 - Fix a bug where custom expressions for step template parameters didn't always show correctly
- 1871 - Special variable for the previous successful deployment ID is now available
- 1881 - Show
Ignore Offline Machines
option during deployment preview - 1897 - Added the variable
Octopus.Action.Package.IgnoreVariableReplacementErrors
to treat variable replacement errors as warnings - 1920 - Re-implement Tentacle deregister-from command.
- 1927 - Automatic retry if uploading a package fails
- 1935 - Fix an issue that prevented retention policies running for projects with thousands of releases
- 1946 - Configuration transform errors are treated as warnings when
Octopus.Action.Package.IgnoreConfigTransformationErrors
is set totrue
- 1954 - Deleted buttons that user is unable to execute are hidden by default
Changes in Octopus Server 3.0.19
- 1878 - New packages will be committed to the built-in NuGet repository at regular intervals instead of waiting until the end of re-indexing
Changes in Octopus Server 3.0.18
Changes in Octopus Server 3.0.17
- 1808 - Correctly set
Local System
as executing user of windows service to ensure it can be applied if the service was previously run under a different account - 1923 - Fix null reference in Calamari script when deploying a new service not previously deployed
- 1924 - PowerShell Script Steps are now executed with the
-NonInteractive
argument
Changes in Octopus Server 3.0.16
- 1907 - Open packages with FileShare.Read to reduce conflicts between anti-virus scanner and Tentacle
- 1916 - Allow health check to return drive information where free space < 1KB
- 1917 - Scoped
ProjectId
s onServerTask
s now remapped as part of migration - 1919 - Resolved issue deploying to Azure targets introduced in 3.0.15
Changes in Octopus Server 3.0.15
What happened to 3.0.14? Some customers experienced an issue with a SQL Database Upgrade script timing out so we decided to pull this release and go straight to 3.0.15 to avoid confusion.
- 1832 - Scheduled deployments date input updated to support popup date picker
- 1845 - Improve performance of events queries
- 1856 - Temporary certificate generated for Azure script execution is removed and not pushed up to server
- 1864 - Package feed details load independently of release details to make release page responsive sooner
- 1887 - Prevent installation of additional High Availability node if license is insufficient
- 1889 - New-OctopusArtifact now encodes the name parameter correctly
- 1892 - Change Calamari file system retry logic to a maximum time not a number of retries
- 1895 - Removed 20 minute timeout from manual tasks
- 1910 - Increased the timeout for SQL Upgrade Scripts to cater for longer running upgrades
- 1911 - Improve logging and wait for service to stop in Calamari BeforePostDeploy script
- 1913 - Bugfix for environment variable not being saved on creation of child steps
Changes in Octopus Server 3.0.13
Changes in Octopus Server 3.0.12
- 1519 - Promote buttons now hidden if the user has insufficient permissions
- 1706 - Workaround for Mono
FileNotFoundException
when callingDirectory.EnumerateFiles
with relative path - 1807 - Dashboard API only returns previous items that did not have any warnings or errors.
- 1838 - Trailing spaces on variable names removed when persisted
- 1839 - Remove missing NuGet packages from the built-in package repository on re-index
- 1852 - 'Remove additional files' (
Octopus.Action.Azure.RemoveAdditionalFiles
) and 'Preserve App_Data' (Octopus.Action.Azure.PreserveAppData
) variables for use when deploying Azure Web Apps. - 1869 - Enable IIS-style logging of HTTP requests (opt-in)
- 1870 - Older deployments will appear faded on the Project Overview page
Changes in Octopus Server 3.0.11
- 1418 - Improve helpfulness of errors when REST API client encounters a proxy server error.
- 1600 - Add a validation check on adding Environments (API) to teams to stop null values
- 1732 - Migrator: Option to limit import of historical data (releases, deployments, events, server tasks, server task logs)
- 1753 - PowerShell script steps will now respect unicode characters
- 1776 - Improved the Release version auto-increment logic
- 1817 - Filtering the deployment targets provides visual feedback for targets applicable to each step
- 1824 - Hydra now configures the Tentacle Windows Service to use the new version
- 1834 - Provide better error messages if export is partially imported.
- 1850 - Only log Error in GetMemberExternalSecurityGroupIds(String username) if it really fails
- 1851 - Prevent Octopus from crashing when marking a task as complete and the database is unavailable
- 1853 - Migrator: Export is not exporting LibraryVariableSetSnapshots
- 1854 - OctopusPhysicalFileSystem: Extra retry after deleting a file or directory
- 1855 - Migrator: Importing server tasks logs is slow
- 1858 - Migrator now supports importing deployments that originated in Octopus 1.6
- 1859 - Calamari updated to filter matching packages by version before generating hash from contents to increase performance.
- 1860 - Delete and Copy operations in Calamari will only retry failed operations instead of every operation
Changes in Octopus Server 3.0.10
- 1767 - Improved the display of long Project names that don't have spaces
- 1768 - Improved the display of long release versions on the Dashboard
- 1814 - Text Encoding of Variable Substitution files are now preserved after transformation
- 1819 - When an Octopus Server has reached its licensed number of Users the server will now prevent any new AD users from signing in explaining the reason
- 1826 - The Process Tab UI now correctly indicates Parallel and Rolling deployments
- 1828 - Long Task names no longer obscure the deployment date/time.
- 1829 - History in Task Summary page now shows 3.0 Tasks, not just 2.6 Tasks.
- 1831 - Tentacle setup - Text updated to indicate "add deployment target" instead of legacy "add machine"
- 1836 - Octopus Server will no longer consider 3.1 the maximum available update
Changes in Octopus Server 3.0.9
- 1665 - Log file names no longer clash with new installs of Octopus Server
- 1747 - Migrator from 2.6->3.0 now imports project logos
- 1813 - Corrupted log lines no longer cause the Migrator to stall
- 1821 - Block deployment permissions scoped to a project now work correctly
- 1823 - Import process will now merge VariableSets
Changes in Octopus Server 3.0.8
- 1774 - Proxy configuration is not used by Calamari
- 1775 - Hand icon appears when hovering over Task Summary
- 1783 - Fixed an exception when trying to set a variable to a date
- 1793 - Provide more informative exception when uploaded Azure Management cert is password protected
- 1797 - Show correct Azure web app & service icons when target is disabled
- 1802 - Enable Azure steps to run in parallel on Octopus
- 1810 - Spinner on NuGet Package Search dialog is misaligned
- 1811 - Properly align blocking tasks on Task Progress screen
- 1818 - SSH and Offline Drop Location passwords could be overwritten when not specified
Changes in Octopus Server 3.0.7
- 1790 - Updated the TeamCity plugin to support
--deploymenttimeout
parameter for Octo.exe - 1799 - Automatic release creation will now continue enumerating projects instead of breaking on the first failure
- 1786 - Cloud Service Deployment Target dropdown values now load and bind correctly
- 1789 - Correct license message will be displayed when Octopus Server can be updated
- 1739 - ActivityLog files are now deleted when deleting documents that have Activity Logs, like ServerTasks
- 1782 - Deployments no longer fail if a manual step happens after package acquisition
- 1791 - Added a warning to the Azure target pages about the changes we are planning for 3.1
- 1780 - Enabled DtdProcessing on XML reader to fix DTD security exception due to default value change in .Net 4.0
- 1806 - Better error reporting for Migration
- 1758 - Fixed a NullReferenceException in
TaskLogFileWriter
that occurred during the Import process - 1779 - Now migrating SMTP Settings from 2.6 to 3.0
- 1781 - Now imports deprecated FTP and Azure steps but prevents subsequent deployment
- 1764 - Package retention policies for the Built-in NuGet feed will now be respected properly
- 1772 - Re-enabled pagination for library packages and feeds
- 1785 - Now supports Windows Services with apostrophe/single-quote in the name
- 1788 - Step Template drop down now correctly highlights the selected option in edit mode
- 1750 - Sensitive values are now masked consistently across all types of logs
- 1796 - Azure SubscriptionId is now validated before allowing you to save
- 1787 - Arguments for sc.exe are now quoted and escaped more consistently when configuring Windows Services
Changes in Octopus Server 3.0.6
- 1509 - Now prevents you from adding ActiveDirectory groups to the "Everyone" team
- 1718 - The Plugins Module has been revived
- 1770 - Cascading deletes now work as expected (for example, deleting users now also deletes them from teams)
- 1777 - Health check now uses Environment property rather than WMI to get machine host name
- 1778 - License is now migrated from 2.6 to 3.0
- 1771 - Octopus Server will no longer crash when checking for cancelled tasks if the database becomes unavailable
- 1769 - Hydra now uses the latest Octopus Installers which ensure Tentacles are reconfigured after update
Changes in Octopus Server 3.0.5
- 1756 - Active Directory authentication now works even if the User does not provide a UPN
- 1724 - Removed some inaccurate API hyperlinks that are no longer relevant
- 1755 - Calamari no longer picks the wrong files when running Octodiff which would cause Octodiff to fail
- 1742 - The Dashboard now updates correctly in more circumstances
- 1740 - The Dashboard now updates correctly when deployments finish
- 1652 - The login form now prevents multiple submissions which would have prevented new Active Directory users from signing in
- 1762 - Extraneous artifacts in backup file no longer crash the data migrator
- 1763 - Fixed several issues with the IIS Bindings UI
- 1701 - Deployments with Manual steps and Retention Policies no longer experience a NullReferenceException
- 1736 - Reverted step parallelism to 2.x behaviour which can be overridden by
OctopusBypassDeploymentMutex
- 1710 - Single quote in environment name no longer breaks pre/post deploy Powershell scripts
- 1759 - More descriptive exceptions are now thrown for missing files and directories during data import
- 1751 - Removed misleading validation on Description fields that have no maximum length constraints
- 1745 - Upload the full package if delta patch fails instead of failing the deployment
- 1725 - Project variables with whitespace in the name will now work
Changes in Octopus Server 3.0.4
- 1609 - The SMTP Client is now disposed correctly
- 1743 - Deleting an Octopus Server instance no longer requires the SQL Database to exist
- 1717 - No longer downloading packages for skipped steps
- 1451 - Clarified Authentication Mode in the IIS Web Site deployment feature
- 1735 - Offline deployments no longer fail when running steps in parallel
- 1690 - Improved timeliness of getting logs from Calamari
- 1731 - Improved logging of unhandled exceptions in Calamari
- 1745 - When Octodiff.exe apply-delta throws an exception the full package is now uploaded as a fall back
Changes in Octopus Server 3.0.3
Changes in Octopus Server 3.0.2
- 1723 - Addressed some UI and behavioural bugs on the Step Templates pages
- 1721 - Fix for z-index for variables pop-up window for bindings
- 1722 - Increase timeout for database creation during install
- 1727 - Fix in Tentacle MSI to correct for Service path on previously upgraded Tentacles
- 1728 - Script console fullscreen now more robust
Changes in Octopus Server 3.0.1
- 1532 -
--deploymenttimeout
used in octo.exe and TeamCity plugin now counts hours too - 1526 - Changes to cookie behaviour for reasons (see issue for full explanation of result)
- 1400 - Logging added of how many files were copied to Custom Install Directory
- 1555 - Semicolon added as email separator in email steps
- 911 - Artifacts are now collected when a Tentacle job fails
- 1193 - Variable filtering now works in the UI
- 1177 - Added
Octopus.Web.BaseUrl
a default web base URL variable for Octopus - 1496 - Added
Octopus.Release.PreviousForEnvironment.Id
and `Octopus.Release.PreviousForEnvironment.Number' - 1533 - Fixed Https bindings when not on the default port
- 1225 - Added correctly spelled variable
IgnoreConfigTranformationErrors
- 1170 - Octopus.Tentacle.CurrentDeployment.TargetedRoles now always available
- 1419 - Provide an option for
any
machine variables (see issue for use and syntax) - 1531 - Removed script console timeout
- 1398 - We now send less log messages when processing XML transforms
- 1238 - Additional logging added for additional transforms if not found
- 820 - Environment variables now updated before invoking scripts
- 1522 - Download icon now links to the correct package in the library
Changes in Octopus Server 3.0.0
- 1532 -
--deploymenttimeout
used in octo.exe and TeamCity plugin now counts hours too - 1526 - Changes to cookie behaviour for reasons (see issue for full explanation of result)
- 1400 - Logging added of how many files were copied to Custom Install Directory
- 1555 - Semicolon added as email separator in email steps
- 911 - Artifacts are now collected when a Tentacle job fails
- 1193 - Variable filtering now works in the UI
- 1177 - Added
Octopus.Web.BaseUrl
a default web base URL variable for Octopus - 1496 - Added
Octopus.Release.PreviousForEnvironment.Id
and `Octopus.Release.PreviousForEnvironment.Number' - 1533 - Fixed Https bindings when not on the default port
- 1225 - Added correctly spelled variable
IgnoreConfigTranformationErrors
- 1170 - Octopus.Tentacle.CurrentDeployment.TargetedRoles now always available
- 1419 - Provide an option for
any
machine variables (see issue for use and syntax) - 1531 - Removed script console timeout
- 1398 - We now send less log messages when processing XML transforms
- 1238 - Additional logging added for additional transforms if not found
- 820 - Environment variables now updated before invoking scripts
- 1522 - Download icon now links to the correct package in the library
Changes in Octopus Server 2.6.5
- 1515 - Added extra logging around Automatic Release Creation
- 1514 - Automatic Release now fixed if automatically generated release number was already used
- 1565 - Fix memory leak with ActorStateFile last snapshot on Tentacle
- 1512 - Automatic Release creation uses pre-release tag but only for nominated package
Changes in Octopus Server 2.6.4
- 1456 - 2.6 Lifecycle retention policies displaying messages incorrectly
- 1507 - Allow variables to be updated even if the deployment process has changed
- 1477 - Automatic release creation now works for first release
- 1510 - Fixed bug in IIS script for non-SNI bindings
- 1411 - Corrected issue where polling Tentacles couldn't be correctly re-configured as Listening Tentacles
- 1481 - Environment history added to releases to show release history for users with view permissions
- 1482 - Correct help text added SMTP Port field
- 1485 - Defect permissions corrected to allow for users to block or unblock releases
- 1479 - Steps now populate isSkipped when determined to be skipped during deployment (such as incorrect environment)
Changes in Octopus Server 2.6.3
Changes in Octopus Server 2.6.2
- 1406 - Run steps in parallel, now more robust when steps are skipped or reordered
- 1475 - Automatic retries around streaming uploads
- 1421 - Octo.exe Import/export now with Lifecycles!
- 1390 - Octo.exe deploy-release updated help reference to "--version=latest" usage.
- 1202 - Variable editable when variable scoped over multiple environments with combination view/edit permissions
Changes in Octopus Server 2.6.1
- 1450 - Fixed issue causing deployments to stall mid-deployment (fingers crossed)
- 1442 - 2.6 health check task should not timeout prematurely
- 1433 - Library -> Packages page now available for non-administrators
- 1428 - Service paths quoted when deploying a service
- 1430 - Fixed an issue causing diagnostics page not to show
Changes in Octopus Server 2.6.0
- 1392 - Project dashboard reverted - slow loading cannot be fixed until 3.0
- 1402 - Fixed HTTP bindings displaying SNI as "Undefined"
- 1391 - Hide promote button when user doesn't have permission on next environment in lifecycle
- 1387 - Pagination in Internal repository fixed when many versions
- 1379 - Fixed issue with role case-sensitivity - causing variable scope issues
- 1384 - Fixed typo in new sc.exe config causing error
Changes in Octopus Server 2.5.13
- 1488 - Fixed a Tentacle issue that caused deployments to hang
Changes in Octopus Server 2.5.12
- 1268 - Fixed internal repository cleanup errors (again)
- 1245 - Project settings screen - Release versioning setting didn't appear to be saving
- 876 - SSL Binding Stability - Specify certificate store name when binding
- 1187 - As above
- 1242 - Renamed IIS Binding from "Add" to "Save"
- 1267 - Red Gate Database Deployment Powershell 2 support
Changes in Octopus Server 2.5.11
- 1237 - Fixed "Run Condition: Failure" to show its correct value in the UI
- 1228 - Added Octopus.Machine.Hostname variable
- 1023 - Deployment log will no longer show warnings for tentacles not included in project
- 1192 - Octo.exe import fixed when the Environment already exists
- 1140 - Ability to specify an Active Directory container
- 1120 - Service dependency removed when not found in existing service dependencies list
- 1189 - Pre-deploy step template step defined variables now expanding properly
- 1227 - edtFTPnet/PRO upgraded to 8.6.1
- 1067 - Fixed display issue with browser resizing hiding navigation
Changes in Octopus Server 2.5.10
Changes in Octopus Server 2.5.9
- 1101 - API for creating teams now properly validates data
- 1146 - Ability to delete Team permission roles
- 1108 - Added a link to the Octopus Repository to allow package download
- 1155 - Added a minimum length to masked tokens
- 1142 - Allow exporting of all step template types
- 1209 - Allow task page view for "taskview" and "taskviewlog" permissions
- 1107 - Can now deploy to environment if UNUSED machine is on wrong tentacle version
- 1121 - Deploy time for schedule deployments matches created time not deploy time
- 1211 - Ensure XML config transform exceptions can be ignored
- 1055 - Large machine roles on Environment page now do not overlap
- 1110 - Extended maintenance mode to include all admin abilities
- 1143 - Handle stale dashboards more gracefully
- 1119 - Output for logging is now buffered to help with large deployments
- 1115 - Fixed incorrect docs in help for octo.exe releaseversion
- 1122 - Fixed Windows 7 x64, PowerShell.exe running as 32-bit
- 1137 - Projects page now has correct pagination
- 1018 - Release Version setting now applied for cloned projects from original project
- 1074 - Setting GuidedFailure option to False ignored when Environment has it set to True
- 1176 - Show 'all' variables that are un-scoped when filtered
- 1103 - Able to delete team (Manual Intervention Related)
- 1109 - Updated "File System - Clean Directory" Step template to work in PS2.0
- 1082 - Update audit log for releases to include version # and application/project name
- 1124 - Script Console now has targets when run as "all environments all roles"
- 1221 - Increased timeout limitation for the Octopus Server communication from Tentacles from 30s to 1h
- 1112 - We now trim Tentacle and Octopus thumbprints of whitespace
Changes in Octopus Server 2.5.8
- 1139 - Fixed issue with import failing due to empty task log
- 1171 - Fixed error causing problems connecting new Tentacles in some environments
- 1159 - Provided a fallback for storing user accounts where no explicit UPN is provided
- 1147 - Show who approved a deployment in the log
- 1161 - Fixed issue with UTF-8 encoding declaration on responses breaking gzip compression
- 1160 - Fixed error whereby large dashboards would show an error
Changes in Octopus Server 2.5.7
- 1113 - Ability to bypass deployment lock on a single Tentacle using a setting
- 1129 - Bug fix for Basic and Windows authentication settings in IIS not being respected
- 1106 - Display deployment time tool tips on the Projects page
- 947 - Fixed special global variable editor permissions allowing viewing of other non-global variables under certain situations
- 1083 - Fixed error "The receiver is offline or experiencing high load and cannot accept the message"
- 1080 - Release notes now allow for markdown > blockquote
- 1134 - "Previously installed package cannot be found" now info from warning
- 1132 - Fixed issue with projects settings initially assuming unsaved changes
- 1105 - Release number de-duplication is fixed for importing
- 1104 - Added unique constraint when importing Retention Policies
- 1078 - Retention policies now run after last package step
- 876 - Avoid SSL certificate binding failure when some certificates without cert store names are present
Changes in Octopus Server 2.5.6
Changes in Octopus Server 2.5.5
Changes in Octopus Server 2.5.4
- 1041 - We now show previous deployments on the dashboard/task list
- 1061 - Variable substitutions can now use filters like ToLower and HtmlEscape
- 1005 - Fixed a race condition that prevented using output variables from child steps
- 1076 - Fixed a bug which caused packages to be deleted from the built-in repository prematurely
- 1070 - Improved help text for custom installation directory
- 1066 - When an error is encountered when communicating with a Tentacle, try again sooner
Changes in Octopus Server 2.5.3
- 1054 - Colons now allowed in variable names when substituted in files or emails
- 1037 - Apply user-specified config transforms in order, even when they overlap with the default
- 1052 - Checks for empty/whitespace encoding names when substituting in files
- 1053 - Release number auto-increment doesn't break on numeric file hashes
- 1028 - Incorrect IIS configuration for virtual and custom directory error with guided messages
- 1039 - Added deletion support to the API for deployments
- 1007 - You can now use Pack with Octo.exe
- 959 - Outcome of steps now provided as a variable (or two)
- 1043 - Install location output variable retrieved even when skipping an installed package to allow for child steps to work
- 1056 - Corrected documentation wording in Octo.exe regarding Environments
- 991 - Warning message for machine target roles now less misleading
- 1035 - Team member count now includes AD groups
- 1038 - Fixed issue with Web portal URL redirection when Octopus is running under a virtual directory
Changes in Octopus Server 2.5.2
- 979 - UI to "Trace permissions" for users added
- 1033 - Date variables excluded from the binding helper
- 240 - Maintenance mode
- 1034 - Style change to distinguish between releases on the project overview page
- 1031 - Fix bug in Windows Service deployment feature (from version 2.5.1)
- 1019 - legacy importer names duplicates in correct SemVers
- 1036 - Scheduled deployments via Octo.exe
- 816 - Show more NuGet package versions
Changes in Octopus Server 2.5.1
- 949 - Windows Service has 'unchanged' start mode and will not try to start up a disabled service
- 292 - Finer control over config transforms
- 929 - Server/Tentacle.exe version included when logging exceptions
- 1022 - Fixed Firefox bug when creating a release with a specific version package number
- 994 - Fixed behavior with mixed case variables
- 724 - You can now clone projects without having to be an administrator (requires Project Initiator or Project Contributor)
- 730 - Paginator now collapses when there are lots and lots and lots of pages
- 854 - No longer overwriting AD usernames when manually creating users
- 479 - Only fatal errors now sent to event log, and activity level events no longer recorded twice
- 1017 - Dashboard now does a hard refresh every 5 hours
- 930 - You can now not deploy to tentacles who's version does not match the Octopus Server
- 951 - AD distribution lists now not shown when searching for AD groups
- 898 - Script variables excluded from OctopusPrintVariables
- 962 - Fixed issue with Failure Guidance Text Box Losing Focus
- 972 - Fixed issue with reorder steps interface re-sizing
- 900 - NuGet Package repository no longer watched due to locking issues, see breaking change
- 970 - Linked .app config packages now correctly package with OctoPack
- 1008 - Octo.exe now has option to show the progress of a deployment
- 1004 - Inital foreground SQUID check now done on separate actor
- 841 - Retention policies '# of releases to keep' are now per-environment
- 581 - Manual Intervention Note now visible in the History log for a release
- 919 - More human-friendly ID's for feeds - now use name in the slug
- 965 - Nuget.exe push now shows errors! such as bad API Key
- 995 - Manual steps now included in Skip All
- 946 - OctoPack - Release notes file can be passed twice
- 945 - OctoPack - option to suppress Octo001 warning
- 1010 - OctoPack now doesn't include duplicate files
- 683 - Option to now not delete .ps1 files post deployment
- 916 - Organised the binding helper suggestions
- 923 - Deployments are prevented if duplicate machines are found
- 1021 - Change logo page now works
- 734 - Prompted variable support in Octo.exe
- 826 - Prompted variables cannot also be scoped to roles
- 787 - Removed the "sensitive variable in Azure config" warning
- 915 - Provided links to all deployment processes that use a given step template
- 843 - Tasks page now organised and filterable!
- 987 - Run retention policies after the last package step instead of as last task in a deployment
- 870 - SSL certificate thumbprint can now be bound
- 252 - Scheduled Deployments
- 835 - Setting for Package Cache retention time now supported
- 894 - Support YYYY, MM, DD variables in version templates
- 532 - Tag process steps by environment
- 999 - Users with TaskView permissions now see high level task progress
- 921 - Fixed bug with transferring a zero-byte file causing artifact collection to hang
- 743 - Disabled concurrent server GC to prevent intermittent access violation crash
- 933 - Typed parameters & custom field types for step templates
- 865 - Use relative (or protocol-independent) URL when redirecting to /app
- 958 - Use specific version reference for Json.NET
- 926 - ### Now supported in variable replacement in custom config files
- 977 - Polling machines now show its IP address
Changes in Octopus Server 2.4.10
Changes in Octopus Server 2.4.9
- 1003 - Add a warning that Deploy.ps1 files in subdirectories won't be run anymore
- 1014 - Ensure all files are included in backups
- 1015 - Incorrect handling of some locales results in bad date/time formatting, breaking retention policies
- 1012 - Projects cannot have the same version numbers with Octo.exe
- 1008 - Show progress of deployment in Octo.exe
Changes in Octopus Server 2.4.8
- 983 - Changes to how file transfers work, their chunk size and error handling to allow for low bandwidth tentacle connections
- 974 - Errors now shown when importing invalid JSON step templates
- 967 - Make it clear that API-only users need to be assigned to teams
- 1001 - MaxParallelism now supported at the root Aquire stage for packages
- 860 - Only 'Fatal' messages are now be logged to the event viewer all others stored in log files
- 976 - Project Overview - You can now view the next page! And the one after that! And so on.
- 920 - Errors now shown when pushing packages to the built in repository if a bad API key is given
- 963 - Windows 2003 installations no longer try to install firewall exceptions
- 982 - SQUID is now restored when a backup is restored
- 993 - Temp files now cleaned up when pushing NuGet packages to the built in repository
- 840 - Now correctly failing on a Tentacle install if the service could not be started
- 996 - Windows Service custom user account password is now stopped from being displayed in configuration output
- 864 - Upload progress bars jittery behavior has been fixed
Changes in Octopus Server 2.4.7
- 831 - Allow Tentacles to be upgraded by environment
- 954 - Concurrency tag should default to task name
- 910 - Presence of BOM not detected/preserved by file substitutions
- 963 - Remove the "Add Windows Firewall exception" checkbox on Windows 2003
- 955 - Show all machines on environments page, grouped by status
- 973 - Step templates that have been used in a release cannot be deleted
- 971 - Use DataDumper for backup/restore
Changes in Octopus Server 2.4.5
Changes in Octopus Server 2.4.4
Changes in Octopus Server 2.4.2
- 878 - Import/export of step templates
- 881 - Include script module link overlaps steps
- 882 - Need good defaults when selecting versioning strategy
- 858 - Packages are not overwritten when already present in the built-in feed
- 862 - Tentacle should not extract packages to the same path twice
- 899 - Variable re-evaluation discards Tentacle-set variables
- 893 - Variable set content type is not set after upgrade
Changes in Octopus Server 2.4.1
- 853 - Add a deregistration command to complement register-with
- 494 - Add ability to create custom user roles
- 571 - Allow deployment scripts (PostDeploy.ps1 etc) to be shared
- 606 - Allow for API-key only users
- 817 - Allow steps to be shared between projects
- 293 - Allow us to move the TEMP folder
- 11 - Associate Active Directory (AD) groups with Octopus Teams
- 751 - Automatic retry when there are IIS configuration problems
- 811 - Automatically replace invalid step name chars during migration
- 687 - Better handling for processes that produce thousands of lines of log output
- 807 - Bring back integrated windows authentication
- 660 - Browser auto-fill on password box does not set password on model
- 666 - Can't push to the built-in feed with NuGet 1.8
- 825 - Captive threads are always logged as being cancelled
- 844 - Checkbox to add Firewall exception during Tentacle setup
- 791 - Dashboard has lost its empty "tutorial" message
- 757 - Detailed Server Logs - no date information
- 645 - Difficult to correctly launch Tentacle Manager on Server Core
- 785 - Disabled machines continue to fail with health checks.
- 879 - Document why (All) scoped variables can't be viewed/edited by default, and how to override
- 692 - Don't cap the number of package versions returned to the package selection dialog
- 749 - Don't download NuGet packages that are skipped
- 677 - Double scrollbar on variables page causes save button to move off screen
- 810 - During package deployment the activity log entry is shown as Success prematurely
- 748 - Ensure PowerShell output is correctly encoded
- 353 - Ensure new-certificate can work without a profile, or document how to load profiles
- 836 - Exclude duplicate release versions when migrating from 1.6
- 842 - Filter audit events by environment
- 619 - Increase discovery process timeout so that Tentacle configuration is more robust to broken CRL checks
- 852 - Increase the deployment process timeout
- 789 - Interruption 'log' link disrupted by 'Interesting' view setting
- 782 - Issue upgrading Tentacle.
- 851 - Keep a limited number of backup files
- 728 - Library variable sets cannot use prompted variables
- 295 - Links to tools and Tentacle downloads from within Octopus
- 848 - Log an error when the downloaded package version number doesn't match the version actually requested
- 505 - Long month names cause misalignment of deployment matrix cells
- 735 - Make Azure management certificate instructions more prominent
- 824 - Make IIS PowerShell run on Windows Server 2008 SP1
- 830 - Make NonInteractive optional
- 608 - Make configuration tab visible to anyone with the right permissions
- 770 - Make it possible to edit un-scoped variables
- 765 - Make license error suggestions
- 580 - Manual Intervention Note is ignored when aborting
- 873 - Manual step instructions are not rendered as markdown
- 681 - Manual steps with explicit approvers, and other specially designated steps, should not be skippable
- 759 - Nicer display for release snapshot variables
- 515 - Octo.exe continues using the 1.6 strategy of the highest package version number
- 736 - Octo.exe delete releases pagination bug
- 867 - OctoPack should check files exist
- 814 - Only 15 lines of PowerShell showing in full screen
- 875 - Only execute the PowerShell scripts at the package root
- 839 - Override how stderr is treated
- 758 - Permissions for package pushing
- 815 - Provide variables relating to the previous version
- 661 - Resolving a domain account called "Administrator" still fails during setup
- 803 - Restore 'Apply retention policy' button back
- 636 - Retention policies for built-in NuGet repository
- 866 - Retention policies should be managed per action, not per step
- 769 - Script console shouldn't prompt for unsaved changes when nothing changed
- 874 - Search for scripts in staging directory, not current directory
- 793 - Semantic version masks 1.2.i etc. use culture-sensitive formatting
- 688 - SkipIfAlreadyInstalled skips package which failed to install
- 819 - Substitute in files should respect original encoding
- 827 - Substitutions in files should be performed before XML config transforms
- 514 - Support selectable strategy for "next release number" generation
- 783 - Switch to package-based versioning on upgrade if a project has package steps
- 773 - Symbolic links are being wiped out with their contents
- 812 - Task log refresh gets very slow when large packages are transferred
- 689 - Tentacle Deletes Packages In Use
- 862 - Tentacle should not extract packages to the same path twice
- 780 - UNC path as application directory and Web Site
- 684 - Unique RavenDB and polling listen ports for multiple instances
- 739 - Use variables from one step in subsequent steps
- 755 - Validate master key when restoring backups
- 448 - Variable evaluation performed before Set-OctopusVariable is considered
- 760 - Variable for default Tentacle application root
- 764 - Variable to indicate whether current deployment is failing
- 828 - Variables for the currently targeted role
- 680 - View 'History' issue at 'Task summary'
- 818 - View/delete packages from the built-in package repository
- 729 - When last step is skipped, root activity isn't marked completed
- 601 - Windows Service feature and Custom Install Location feature interaction
Changes in Octopus Server 2.3.6
- 850 - Releases for the same project with duplicate versions can be imported
Changes in Octopus Server 2.3.4
Changes in Octopus Server 2.3.3
Changes in Octopus Server 2.3.2
Changes in Octopus Server 2.3.1
- 349 - Active process management
- 699 - Apply retention policies does not finish
- 642 - Better expand/collapse behavior for Task Output, and "Interesting" mode
- 714 - Check for more duplicate issues during import from 1.6
- 686 - Clean actors when repairing DB
- 551 - Concurrent package downloads compete for file access in the package cache
- 671 - Custom expression on NuGet Package ID field in process step doesn't get replaced when creating a release
- 529 - Custom fields for NuGet feeds does not let me enter a variable
- 717 - Ensure that environments that the user can't see aren't removed from the environment list when editing steps
- 713 - Ensure we don't run custom scripts when the feature is disabled
- 673 - Fail running tasks when restoring backups
- 701 - Filter audit events
- 563 - Generic template-based file transformation
- 710 - Improve performance of task output and dashboard rendering
- 695 - Keep focus on manual comments field when refreshing deployment
- 640 - Keep horizontal scroll position on dashboard
- 639 - Large package uploads degrade over time
- 698 - Migrate OctopusWebSiteName
- 716 - Only allow editing variable sets/deployment processes if editing the latest version
- 573 - Project Viewers cannot submit manual steps even in an appropriate team
- 674 - Promote To and Try Again should remember previous skipped steps
- 227 - Prompted variables
- 715 - Redirect after login
- 721 - Select specific machines to deploy to
- 685 - Select/deselect all link on skip steps for deployments
- 694 - Standardise how collections of paths are represented in variables
- 589 - Support IIS 8/8.5 Performance Enhancements
- 474 - Support large numbers of projects in the drop-down project list
- 712 - TeamCity create/deploy release runner does not fail if deployment fails
- 720 - When tasks are queued, show a list of tasks they are queued behind Please read this guide when upgrading from Octopus 2.0.
Changes in Octopus Server 2.2.1
Highlights of 2.2
- Ad-hoc PowerShell console
Define Deploy.ps1 scripts in Octopus
Changes from 2.1.3 to 2.2.1
675 - Full screen editor for PowerShell scripts
- 672 - Deploy.ps1 scripts can be defined in Octopus rather than embedded in packages
- 670 - Email step CC binding bug fix
- 668 - Various license encoding issues
- 652 - Fix excessive web UI HTTP traffic when browsing
- 646 - IIS bindings support duplicate copies of a certificate in the store
- 627 - Library variable set scoping/resolving improvements
- 605 - FTPS timeout tweaks
- 601 - Windows Services and custom installation directory work together
- 598 - Releases for the same project can be created simultaneously
- 542 - Process step renaming issue fixed
- 540 - Project overview and release details page now auto-refresh
- 539 - Large NuGet package sizes are shown correctly
- 535 - IIS convention now allows HTTP/HTTPS bindings to be bound
- 465 - Reorder environments always updates dashboard
- 176 - Show master key improvements for remote desktop users