What's new in Octopus Deploy 2024.2.6366
Apr 29, 2024
- Small UI improvement to Server-Side Apply config options
- Fixed issue where file paths field would not be shown in Deploy Kubernetes YAML step properly when sourcing from a Git repository
- Fix an unexpected error that occurs on the triggers page if a branch has been deleted
New in Octopus Deploy 2024.2.6041 (Apr 24, 2024)
- Octopus no longer supports custom authentication extensions. Read the blog for more details: https://octopus.com/blog/deprecating-authentication-extensions
New in Octopus Deploy 2024.2.5350 (Apr 19, 2024)
- Audit events are no longer added for the Deployment and Runbook history table
- Fixed sorting order of Steps in the Deployment Step scope dropdown of the variable editor
- Fixed an issue where the browser's back button would need to be clicked twice to go back to the previous page after clicking into a project
- Allow users to choose to automatically transition a ServiceNow Change Request to either Review or Closed after a successful deployment
- Fixed an issue where splitting insights report by project group would result in an error
- Normalised User and converted document persistence from JSON to relational model
- Reduce load on database during health status checks and analytics collection
- Fixed issue with old expired trial license being blocked by tenant limits
New in Octopus Deploy 2024.2.4636 (Apr 12, 2024)
- Remove call to API endpoint that requires ConfigureServer permission on the Create Deployment page
- Add space switcher tool-tip to reveal truncated name
- Allow creating an emergency CR in ServiceNow when deploying a release of a project to an environment that both are change controlled
- Fixed an issue where reordering list items in some situations would be duplicated and potentially crashing the ui
- Log ClientDenied messages at Debug level
New in Octopus Deploy 2024.2.2914 (Mar 21, 2024)
- Overhauled Step Selection screen to reduce confusion and make it easier for K8s users to choose the appropriate step
- Converted ScopedUserRole document persistence from JSON store to relational model
- Fix pull request URLs for GitLab repositories in a subgroup
- Calamari distribution no longer differentiates between Calamari.exe and Calamari.Cloud.exe
- Converted UserSession document persistence from JSON store to relational model
New in Octopus Deploy 2024.2.2075 (Mar 18, 2024)
- Add/edit source code in Terraform steps has a small textarea
New in Octopus Deploy 2024.2.1902 (Mar 13, 2024)
- Disabled /reporting/deployments-counted-by-week API endpoint
- Fix Excel prompting for user credentials when updating our Excel reporting template to use your own Octopus instance
- Fixed an issue where file access to the same git resource in parallel would cause a deployment failure
New in Octopus Deploy 2024.2.1511 (Mar 11, 2024)
- Disabled project level /git/branches API endpoint
- Disabled Project level /runbooks/all API endpoint
- Fixed an issue where clicking on a worker machine that requires a tentacle upgrade will navigate to the wrong page and display a not found error
New in Octopus Deploy 2024.2.534 (Feb 28, 2024)
- Display 'Missing resource' text instead of permission error for project variables
- Always keep "edit" button visible in Tenant Variables page
- Show Octopus version for nodes listed on node page
New in Octopus Deploy 2024.1.10284-hotfix.10558 (Feb 12, 2024)
- Resolved an issue where deployment target health checks would not correctly use specified action containers
- Fixes memory leak in WebAuthCache that could lead to OutOfMemoryExceptions in certain circumstances
- On the Project Tenant Variable page, added missing value warnings to project template tab and sidebar. Also added missing warning callout
- Allow configuring what elliptic curve to use when generating a self signed certificate
- Fixes a bug in which not all task logs would be returned when the same Server task was run both before and after the multi node task logs feature is enabled, for example as part of an auto deployment
- Variables scoped to a process are now considered when configuring a rolling deployments window size
- Add tenant tag filter to the Tenant Variables page
- Improved the memory usage when querying large Helm repositories
New in Octopus Deploy 2024.1.9900 (Feb 7, 2024)
- The debounce time on package name inputs is too short
- Introduce new Octopus.Project.Git.BasePath system variable
- Fixed an issue where file access to the same git resource in parallel would cause a deployment failure
- Fixed strike-through text on excluded targets in deployment creation
- Fixed an issue where the edit release overflow menu item would not redirect to the edit release page
- A new "Featured" category has been added to the step selection screen, promoting a few "Recommended" steps
- Add environment filter to Tenant Variables
- Fix error running lost-master-key command with Tenant Variables and Library Variable Sets
- Display installed community steps will now be visible in both the Library Step Templates and their original categories
- Fixed an issue where the runbook retry button redirecting to the run now page instead of the retry runbook run page
- Updated the label on the support menu item in the user menu dropdown to be "Octopus support" rather than "Your organization's internal support" when a custom support URL isn't configured
- Fix links to deployment process step sometimes failing to navigate to the correct step
- Users can now opt-in to a new project tenant variables experience from the project templates or common templates pages
- Updated Octopus Server's builtin username/password and API key storage parameters to align with industry best-practices
- Fixed issue with custom k8s resources from previous deployments not being deleted
- Fixed a routing issue with Runbook Tasks not being able to redirect to their task details screen
- Fixed a regression where a power user weren't able to change other user's passwords via the UI
- Improved detection of Network Errors when communicating with Tentacles, allowing Octopus Server to re-attempt communication
- Removes Polling Response Timeout in favour of depending on ordinary communication timeouts. Doing so allows for large packages to be sent between Octopus Server and Tentacle
- Fixed a bug where task running and waiting counts wouldn't load if filters were applied
- Fixed an issue where SupplementalGroups and RunAsUserId were not populated in the Edit Yaml section for the "Deploy a Kubernetes container" step
- Fixed a bug where "Google cloud account" couldn't be selected when creating or editing template variables
- Make it clear that the Kubernetes target Namespace property is optional
- Record events related to editing Event Retention configuration as correct the user
- Fixes a bug in which Octopus may not have waited long enough for scripts run on tentacle to be cleaned up, resulting in a misleading message that the cleanup failed when it may succeed. https://github.com/OctopusDeploy/OctopusTentacle/issues/770
- Fix re-running step templates not using settings from the previous run
New in Octopus Deploy 2023.4.7608 (Oct 31, 2023)
- Fix missing gap between buttons when editing a lifecycle
- Improve transaction names in diagnostic reports
- Fix scheduled release creation with package versioning strategy
- Added validation for the auth session timeout to prevent setting it to a value s too short
New in Octopus Deploy 2023.4.5452 (Oct 13, 2023)
- Fix "Cannot create GitProjectReference for non-Git project" for some releases
- Fix janky UI when machine summary contains long name and many target roles
- Fix runbook cloning UI where not all runbooks are available to select
- Add icon selector to tenant logo editor
- 'Calc' variable substitution allows variable names to be enclosed in { } to overcome parsing issues
- Fixed an issue where Insights reports were not showing new deployments
- Don't run package acquisition step for targets that are unavailable and project allows skipping those targets
- Fixed Code Editor losing language selection when toggling full screen mode in the variable editor
- Fix project reference error when editing config-as-code releases
- Improved performance on Process Edit page for projects with large number of connected Library Variable Sets
New in Octopus Deploy 2023.4.3586 (Sep 25, 2023)
- Remodel ServerTask to avoid concurrency contention when deploying multiple deploy a release steps in parallel
- All Variables page hangs and errors in Spaces with lots of projects, Tenants and Tenant Variables
- Correctly handle variable set ids in master key rotation
New in Octopus Deploy 2023.4.3511 (Sep 22, 2023)
- - Added a Load More button and load all link into the Release page progression section to allow viewing of more deployments for a release
- Updated API documentation for the /api/tenantvariables/all endpoint to clarify behaviour
- Fixed a bug where some error messages weren't shown on the Projects, Tenants, Insights Reports, and main Dashboard pages
- Clears Tentacle cache directory upon Octopus server start
- The user account menu now shows the user's display name in the menu and on hover
- Fix an issue where the release details page displayed an error for releases in a Version-controlled project that were created before the VCS conversion
New in Octopus Deploy 2023.4.939 (Sep 4, 2023)
- Improve performance of various API endpoints when querying large sets of data
New in Octopus Deploy 2023.3.11507 (Aug 22, 2023)
- Fixed an issue with Execution Timeouts where warning logs would trigger after task completion
- Adding the ability to source YAML from a Git Repository for the Kubernetes Raw YAML Step
- For better discoverability, we have changed the order of steps, so new steps are displayed first
- Improved Release page load and responsiveness when viewing a release with thousands of deployments
- Improve performance of the Deployment Template endpoint for large scale tenanted scenarios
- Fix redeploy tenanted release issue where the option to skip tenants where release is current for a tenant isn't available after explicitly selecting tenants
- Deprecation warnings added to health checks & tasks on Windows 2003 Targets & Workers
- Fix tentacle version checking when installed version is higher than the server comes with
New in Octopus Deploy 2023.3.8714 (Aug 2, 2023)
- 8244 - Allow multiple tenants to be connected to a project in the same request
- 8247 - Removing a step package used in channel rule now requires removing the channel rule itself
- 8254 - Fix expand icon buttons not aligned in the Environment page
- 8243 - Added Tenants section to all projects which displays all tenants connected to the project and allows connecting tenants from the project side
- 8253 - Fix project logo background not circular in dark theme
New in Octopus Deploy 2023.3.7514 (Jul 17, 2023)
- Support null values in variables
- Octopus Server on Linux will no longer attempt to run HTTP.sys in extensions
- Name search for Deployment Targets is now case insensitive
New in Octopus Deploy 2023.3.6938 (Jul 13, 2023)
- Fix tooltip positions incorrect in Safari
- Log .NET Framework during windows healthcheck
- Fixed error when exporting a project if the project has more than 2100 releases
- Improved performance of deployment preview
New in Octopus Deploy 2023.3.6319-hotfix.6572 (Jul 10, 2023)
- Fix library variable set usage
- Fixed issue with Kubernetes Object Status tab not displaying status of objects in Kubernetes that were being updated from child steps
New in Octopus Deploy 2023.3.6026 (Jul 10, 2023)
- Changes in Octopus 2023.3.6026:
- 8236 - Fixed the bug where customers are not able to turn KOS off when using multi glob pattern
- 8238 - Fix error when migrating inputs for package step
- 8190 - Updated Autofac dependency from v4.9.4 to v6.4.0
- 8234 - Fixed some incorrect layouts in removeable list items
- 8235 - Moved user session and git repository cache invalidation to SQL database
New in Octopus Deploy 2023.3.4541 (Jun 26, 2023)
- Fix possible null reference exception when cancelling interrupted server tasks
- Run package acquisition steps if later steps with a run condition of Variable / Always run / Failure in the process require packages, even if previous steps in the deployment process have failed. Packages for variable steps will always be acquired - the variable condition will not be checked for package acquisition
- Reduced the key size of IX_MessageBusCursor_ConsumerGroupId and UQ_MessageBusCursor_ConsumerGroupIdUnique
- "Deploy Kubernetes config map resource" step no longer resets namespace when edited via yaml source
New in Octopus Deploy 2023.3.4135 (Jun 20, 2023)
- 8193 - Initial support for OCI registries
- 8204 - Fix unclickable details button when hovering over action template cards
- 8205 - Prevent portal on instances with DNS prefix starting with "api" from failing to resolve API URIs
- 8203 - Use a background task to bulk update step template usages
- 8201 - NULL value for Project Description may cause an error when attempting to search Projects
- 8202 - Words in the project dashboard will no longer be broken up
- 8198 - Fixes CryptographicExceptions thrown due to dotnet runtime updates https://support.microsoft.com/en-us/topic/kb5025823-change-in-how-net-applications-import-x-509-certificates-bf81c936-af2b-446e-9f7a-016f4713b46b
- 8200 - Fixed a regression that prevented some projects from loading
- 8182 - Tenants filters have been updated to dynamically expand as new filters are added. Negation filters have been added. The multi-select picker for tags has been updated to allow multiple selections without closing the picker
- 8196 - Updated styling of visual feedback for checkboxes
- 7954 - Virtual Directory - Initial redirect from / to /app
- 8197 - Changed clock icon colour for scheduled runbook triggers
- 8191 - Fixed focus rings being clipped incorrectly in the new navigation bar
- 7998 - Added support for kubelogin to AKS authentication. When authenticating to an AKS cluster with kubelogin in the execution environment, the kubeconfig will now be updated by calling kubelogin convert-kubeconfig -l azurecli
- 8192 - The /reporting/deployments-counted-by-week API endpoint is being removed in future versions. Further details of this deprecation can be found in the deprecations documentation
- 8199 - The GET api/projects/{projectId}/runbooks/all API endpoint is being removed in future versions. Further details of this deprecation can be found in the
- 8037 - Added support for cancellations in our full-table cache (made async)
- 8189 - Rename of Kubernetes output variables to prevent clashing with customer variables
- 8120 - Display Kubernetes Objects Status During Deployment
- 8171 - Calling the tasks/{id}/details REST endpoint will now return all valid log entries before invalid JSON is detected in a log file.
New in Octopus Deploy 2023.3.2586 (Jun 13, 2023)
- Fix incorrect icon color in the quick commit button
- Upgrade a Helm Chart step - Helm feeds require a trailing slash in the URL if helm repo's index.yaml uses relative URLs
- Deployment retention no longer cleans up packages - that is all handled by package retention
- Python script output is buffered which causes logging issues
- Fixed cloning project issue caused by permission scoping
- Users with the required permissions to clone a project scoped to a specific project group receive a permission warning when cloning a project
- Reduce irrelevant build information on deployments
- Tag set filters on the Tenants overview page now show up dynamically as new filters are added
- Connectivity checks running indefinitely blocking execution on a deployment target
- Fixed package acquisition with multiple workers and multiple package references when lease cap is enabled
New in Octopus Deploy 2023.3.1708 (Jun 7, 2023)
- Introduced audit log retention feature. See here for more details
- Calling the tasks/{id}/details REST endpoint will now return all valid log entries before invalid JSON is detected in a log file.
- This fix also ensures Task Log Aggregation does not aggregate task log files that contain invalid JSON entries, and leaves related task logs in their original unaggregated form - 8177 - Fixed a regression that prevented AWS credentials from being used during step execution - 8025 - Python script output is buffered which causes logging issues - 7184 - NuGet packages with build metadata in the version will now use the package cache to speed up transfers - 8169 - Improved the speed of built-in package reindexing when there are many packages with the same package id - 8165 - Name search for Deployment Targets is now case insensitive - 8178 - Tasks that rely on mono will start logging warning messages - 8163 - Guest users can now access Version Controlled projects and several other pages that previously returned an error - 8166 - Updated styling of visual feedback for most buttons across the portal - 8129 - Fixing UserId filtering for audit logs
New in Octopus Deploy 2023.3.829 (May 29, 2023)
- Moved the filters on the Tenants overview page into the toolbar at the top of the page
- Fixed an issue where the top navigation bar crashes the UI when a user has no permissions
New in Octopus Deploy 2023.2.10947 (May 17, 2023)
- Unique name constraint error when cloning a project
- Steps can be configured to automatically retry when they fail
New in Octopus Deploy 2023.2.10545 (May 14, 2023)
- Fix tenant variable removal when removing environments from projection connection
- Resolving Manual Interventions and Guided Failure as well as viewing blocking deployments is now much faster when there are a large number of interventions or guided failures
- Overhauled the Tenants overview page to improve the visibility of all available Tenants and their respective tags and project/environment connections
New in Octopus Deploy 2023.2.10265 (May 10, 2023)
- Improved aesthetics and visual hierarchy for the top navigation bar
- Only display build information linked to the package that is being viewed
- Connectivity checks running indefinitely blocking execution on a deployment target
- Retention policies are no longer run simultaneously to reduce contention on the database
New in Octopus Deploy 2023.2.9849 (May 8, 2023)
- Fix release notes overflow on Task Summary page
- Fixing UserId filtering for audit logs - https://github.com/OctopusDeploy/OctopusDeploy/pull/17836
- Fixed a permission scoping issue affecting docker container registries, causing image search and tag search to fail impacting release creation
- Fixed error if TrustedProxies contains invalid values
- Fixes an issue with upstream DockerHub auth where tokens requested with "registry:catalog:" no longer grant access. Updated to use "registry:"
New in Octopus Deploy 2023.2.9088-hotfix.9778 (May 4, 2023)
- Fixed a permission scoping issue affecting docker container registries, causing image search and tag search to fail impacting release creation
New in Octopus Deploy 2023.2.8159 (Apr 27, 2023)
- Updated warning on failed Always Run steps to suggest retrying where safe to do so
- Configure audit stream button now shows up correctly
New in Octopus Deploy 2023.2.5309 (Apr 13, 2023)
- Fixed an issue where a long-running database transaction would grow the transaction log unreasonably large during a long deployment
- Fix for tenants endpoint missing Page.Next hypermedia link when more than one page of results
New in Octopus Deploy 2023.2.4819-hotfix.4932 (Apr 4, 2023)
- Fixed an issue where Bash scripts can reveal secret values
New in Octopus Deploy 2023.2.4336 (Mar 30, 2023)
- 8103 - Fix blob error during master key rotation
- 8099 - Fixed an issue where GET /workers did not respect filtering by worker pool IDs
- 8100 - Improve performance and prevent lock-ups of Octopus Server Portal on pages that display variables when there are thousands to display (eg Release page)
- 8095 - Improved performance and prevent browser from locking up on the Release page, when the release contains thousands of variables
- 8091 - Fix modify project endpoint not picking up project id properly
- 8087 - Reduce unnecessary server requests when viewing environments and deployment targets
New in Octopus Deploy 2023.2.3263 (Mar 20, 2023)
- 8084 - Fixed an issue when saving web portal configuration using OctopusClient which caused authentication configuration to be overridden
- 7433 - Fixed daylight saving causing triggers to fire repeatedly
- 8079 - Improved the performance of the list deployments API when there is large build information
New in Octopus Deploy 2023.2.2718 (Mar 13, 2023)
- 8077 - Fixed a persistence issue on ForcePackageDownload option for Runbooks
- 8071 - API key generation can be restricted to allow only Service Accounts
- 8070 - Fixed a problem where "missing variables" indicators on the Tenants page take an extremely long time to load when there are thousands of tenants that have missing variables
New in Octopus Deploy 2023.2.2394 (Mar 13, 2023)
- 8063 - Decreased the number of queries to the project and lifecycle tables during retention
New in Octopus Deploy 2023.2.2394 (Mar 8, 2023)
- Decreased the number of queries to the project and lifecycle tables during retention
New in Octopus Deploy 2023.1.9672 (Mar 3, 2023)
- Breaking Changes:
- Update action templates logo endpoint to return not found response when the logo is not found
- Other Changes:
- EnvironmentIds, TenantIds and TenantTags are no longer required when modifying a certificate
- SSH home paths are unique per SSH target or worker rather than per HA node
- Terminate child processes on Linux targets and Workers when a server task is cancelled
- Added deployment duration chart to the Insights feature
- Fixed Insights Report creation validation error TenantMode is required
- Task incorrectly reporting earlier versions of package on tentacle
- Fixed a recent regression in the time taken for policies to be loaded during release retention
- Improved the log output of the retention task
- Fixed an issue with Azure Service Fabric AAD referencing the ADAL .dll library instead of MSAL
- Addressed an issue where some resources could be viewed when the user does not have access to the space
- Make environment summary search on partial name case-insensitive again
- Minor UI - Deploy CloudFormation Step Template - Configuring S3 Source Gives "Template Source Not Specified"
- AWS S3 Bucket Feed doesn't show in feed selection dropdown in Deploy a Package steps
- /nuget/packages endpoint no longer handles trailing slashes after query parameters
- Improve performance for Git projects connected to repositories with a large number of branches and tags
- Fix step template updating on Git projects when there are pending Git migrations
- fixes issue where project triggers would run immediately after modification
- Index rebuilding is no longer happening during an upgrade
- Fixed an issue loading Runbooks whose names contained certain characters
- Tentacle upgrades are performed on more machines at once, reducing the overall time it takes to upgrade many Tentacles
- Fixed an issue where running the Deploy an Azure Web App (Web Deploy) step would fail when running in the Worker Tools
- Prevent tag deletions if they are used in runbook processes
- Show a warning that scoped variables will be deleted when deleting channels and deployment targets
- When importing projects that have a library variable set attached you might get a duplicate entry for some variables
- Fix channel create and edit page on Git projects when the current branch has an invalid deployment process
- Fix loading variable-bound packages when creating releases in Git projects
- Fix modifying project group name/description
- ECS Step Template - Unable to specify FirelensConfiguration in Container Definition
- Fixed autocomplete popup not showing in the fullscreen code editor
- Fixes issue where updating to a new major version of a step would result in unexpected null values in step inputs
- Resolved Temp/NugetTemp cache folder retaining packages after tentacle package acquisition
- Adding handling for invalid certificate exceptions and will continue to process other certificate expiries
- Fix duplicate slug error when cloning steps in the process editor
- Fix issue when converting a project to Git using an existing Octopus configuration folder
- Fixed workerpools endpoint in /api doc
- Fixed an issue where you could clone a runbook with an empty name
- Fix event type when machine is deleted by machine policy
- Certificate metadata corrected to allow expiry and warnings to be properly raised
- Search no longer throws an exception when default space is enabled
- The Deployment History section will now be refreshed when the variables are updated for a Release
- Fixed task log delays for logs from a long-running process
- Improve Tentacle free disk space checks to take into account mount points
- Fixed an issue where telemetry would fail to send when hosting server in a virtual directory
- Releases created on version controlled projects before conversion will fallback to using the deployment settings from the default branch on the preview screen
- Fixed and issue where certain packages in the built in package repository could not be viewed
- Fixed empty audit messages being generated for workers when doing health checks
- Fix issue preventing certificate tenant mode from being updated
- Fix an issue where the deployments page did not show an error message in some circumstances when the deployment has been deleted
- Provide a clearer error message when trying to save a tenant tag set without a name
- Fixed the issue that variables selection button retains focus after a variable is selected
- Usage not displayed for Accounts set to a variable in a variable set that is part of a release which blocks Account deletion
- Added support to define Host Aliases in the Deploy Kubernetes Containers step
- Fixed the Swagger UI to work when Octopus is configured to use a virtual directory
- Fixed runbook run list display so that it is consistent between pages
- ServerTaskStartedDomainEvent not published for deployment tasks.
- Swagger UI missing the body for POST'ing to the /users/ endpoints.
- Failed automatic deployments from lifecycle promotion will no longer create empty server tasks
- Steps with a Variable Run Condition evaluating as "false" presents a Status.Code of "Succeeded" instead of "Skipped"
- Fixed an issue where validation during running a runbook could incorrectly think there were duplicate runbook names
- Reduce the number of API calls made when rendering lifecycle previews
- Allow release versions up to 349 characters
- Fixed a potential issue when fetching git documents
- To enable customers running Octopus behind a proxy to send logs to Seq we now send default proxy credentials as part of the HTTP request to Seq
- Fixed incorrect Json serialization casing in the execution API responses
- Build VCS details exposed to release notes via Octopus.Release.Builds variable
- Fixed a conflict issue when concurrently updating multiple channels
- Added a warning during deployment for GKE customers if their deployment requires the gke-gcloud-auth-plugin to be available
- Cancelled Tasks (e.g. a deployment) completes but the Task is never marked as completed and stays in the cancelling state with SQL Error 1222.
- Cancelling now works in HA setups
- Stopped a canceling server task from being deleted until it has finished canceling
- Make default API key expiry 6 months instead of never
- Target discovery and AWS steps can now inherit web identities such as those associated with service accounts in EKS pods
- Fix package details error when id contains metadata
- Fixes the display type of space search results to not be an internal type
- Fix error when reading from Git projects with a trailing slash on the base path
- Return a more helpful error message when failing to download packages from a file system NuGet feed
- Runbook publish status not reflected immediately after publish
- Improved log message when failing to pump from the message bus
- Improved internal caching, resulting in health checks over thousands of machines running closer to how long they used to
- Fixed a bug where clicking on a scheduled trigger hyperlink on the audit page would cause a React error
- Indicate when subsequent child steps are skipped
New in Octopus Deploy 2023.1.8263-hotfix.8481 (Feb 9, 2023)
- Fixes issue where project triggers would run immediately after modification
- Security fixes
- Index rebuilding is no longer happening during an upgrade
- Fixed an issue with the content security policy blocking custom step templates and various other things
- Fixed an issue loading Runbooks whose names contained certain characters
- Swagger UI now loads correctly
- Fixed an issue where running the Deploy an Azure Web App (Web Deploy) step would fail when running in the Worker Tools
- Fixed an issue where the Community Template Sync task could fail if an installed Template's underlying data needed updating to be in-sync with the published version
- Prevent tag deletions if they are used in runbook processes
- Show a warning that scoped variables will be deleted when deleting channels and deployment targets
- Removed a restriction that prevented deployments to older versions of Tentacle
New in Octopus Deploy 2023.1.6715 (Jan 19, 2023)
- Update action templates logo endpoint to return not found response when the logo is not found
New in Octopus Deploy 2022.4.6133 Hotfix 6926 (Nov 2, 2022)
- 7870 - Support master key rotation
- 7857 - Disable new Tentacle upgrade flow
- 7838 - Improved the load time of the Create Deployment screen
- 7855 - Removed redundant second health check when a new worker is created
- 7848 - Fixed an issue where a transient database connection issue could persist even after the transient issue has gone
- 7853 - Octopus just keeps getting better and better!
- 7812 - The Lead Time now shows the values on the days in the lead up to the deployment not just on the day it occured
- 7744 - Stale package locks are now appropriately released
- 7604 - In addition to SemVer, package retention now also supports other version formats
- 7830 - Fixed an issue where project settings for git projects could not be modified when no OCL existed on the default branch
- 7826 - Improved the performance of the project summaries API endpoint
New in Octopus Deploy 2022.4.5100 (Oct 24, 2022)
- 7830 - Fixed an issue where project settings for git projects could not be modified when no OCL existed on the default branch
- 7826 - Improved the performance of the project summaries API endpoint
New in Octopus Deploy 2022.4.4600 (Oct 13, 2022)
- 7833 - Make PUT /dashboardconfiguration restore default settings when called with no request payload instead of returning a "No request body" error message
- 7827 - Fixed a problem where steps that use an Execution Container hosted on a private registry may fail if they come after a Manual Intervention step
- 7818 - Support newer timezones, e.g. Europe/Kyiv
- 7817 - Fixed an issue in the Process Editor where pressing enter while the Variable Picker is open unexpectedly triggers the Save or Commit action on the step
- 7777 - Scheduled triggers save correctly again
- 7769 - Fix error running Runbooks in projects with prompted library variables
New in Octopus Deploy 2022.4.2898 Hotfix 3486 (Sep 30, 2022)
- 7759 - OpenID Connect authentication providers can only be uninstalled by setting their environment variables
- 7748 - LDAP authentication provider can only be uninstalled by setting an environment variable
- 7757 - Directory services authentication provider can only be uninstalled by setting an environment variable
New in Octopus Deploy 2022.4.1372 Hotfix 1838 (Sep 16, 2022)
- 7765 - Start Date now shows correctly again on the Project Trigger overview and when editing
New in Octopus Deploy 2022.4.1372 (Sep 12, 2022)
- 7769 - Fix error running Runbooks in projects with prompted library variables
New in Octopus Deploy 2022.4.1371 (Sep 9, 2022)
- Breaking Changes:
- Username Password authentication provider can only be uninstalled by setting an environment variable
- Updated ServiceNow approval caching. This results in existing Change-controlled deployments being unable to exit "Queued" state; these will need to be canceled and restarted
- Fixes an issue with the "Create Release" page for projects that rely on an image from a DockerHub (<https://index.docker.io>) feed
- Other Changes:
- Fixed an issue whereby deployments which reference Jira Work Item(s) (using the Jira Integration) and contain a Manual Intervention step would fail, reporting an AutoFac circular dependency
- Fixed an issue where git migrations may incorrectly get skipped
- Out of date Tentacle and Calamari warnings are no longer useful
- Fixed an issue where duplicate slugs were allowed in deployment and runbook processes
- Fixed an issue where tenant certificates were not being exported
- Project triggers no longer generate modified audit events without user input
New in Octopus Deploy 2022.4.791 (Sep 7, 2022)
- Breaking Changes:
- Guest authentication provider can only be uninstalled by setting an environment variable
- Other Changes:
- Attempting to save a Form without a selected Account fails validation but the Combo Box does not show as red
- API deployments/create/untenanted/v1 fails to deploy release in a version controlled project
- Adding a deployment target will once again ensure that linked environments, machine policies, and tenants exist in the system when using the API
- Ensure rolling deployments happen in correct order based on targets
- Fix an issue where branches created via the branch selector would end up prefixed with refs/heads/
- Fix styling around the load all button
- Fix deployment creation page using incorrect git ref for deployment settings
- Fix clickable area in user identity search list
- Allow delete dialogs to be submitted using the enter key
- Fix navigation bar overflow menu not appearing on smaller screen widths
- Added "machine task processing limit" to the Upgrades settings to allow processing more machines in upgrade and health check tasks at any given time
- Fixed upgrade error when there is a release with a large number in the version
- Fixed deserialization of dates
- Fix Entity Not Found error on Project pages for Projects with unicode character names
- Fixed issue with Unicode in project names
- Connections to machines without a proxy are closed when the machine is deleted
- Make automatic release creation more performant for instances with a large number of projects
- Private spaces are decommissioned and will no longer be available. Existing private spaces will be deleted in the background over time
- The message bus QueryNotificationObserver will backoff when the SQL Server is not reachable
- Fixed unexpected duplicated action template when importing projects
- Improved performance of viewing variable sets
- Reduced number of ids per request when retrieving resources via /all?ids
- Added a retry policy with exponential delay when fetching the message bus sequence number to avoid logging too many messages
- Added page size control to releases page
New in Octopus Deploy 2022.3.5512 (Jul 26, 2022)
- Breaking Changes:
- 7673 - Reduced number of requests made to external feeds when creating and viewing releases. SelectedPackagePublished in deploymentprocesses/{id}/template has been moved to Published in packages/notes
- Other Changes:
- 7672 - Fixed an issue where the releases/create/v1 endpoint would fail to create releases for version controlled projects with package references
- 7675 - Fix error viewing a release when a lifecycle phase has trailing whitespace
- 7551 - Tenant Tags correctly filter deployment targets on Infrastructure screen (regression)
- 7670 - Fixed warning message: Resolving ... from this named scope OctopusTaskScope is not permitted
- 7666 - Improved performance of retrieving and deleting artifacts
- 7658 - Added a retry policy with exponential delay when fetching the message bus sequence number to avoid logging too many messages
- 7661 - Fixes an issue where Octopus Cloud and Octopus Server on Linux could not talk to NuGet feeds hosted behind NTLM auth (including self-hosted TFS package feeds)
New in Octopus Deploy 2022.3.5455 (Jul 21, 2022)
- 7672 - Fixed an issue where the releases/create/v1 endpoint would fail to create releases for version controlled projects with package references
New in Octopus Deploy 2022.3.4953 (Jul 18, 2022)
- Fix triggers not processing when a space's task queue is stopped
- Fixed an issue where step templates with broken references could prevent deployment processed from being read from OCL
- Improved performance of viewing variable sets
- Updated Create Release/Execution commands JSON payload definitions to match its associated class properties
- Address a performance issue when using step templates in a version controlled deployment process
- Fixed an issue where step packages stored in OCL were incorrectly deserialised
- Added the ability to specify a docker network name in the docker create a network step
- Improve performance of deploymentprocesses/template
- Scheduled trigger times are correctly shown and new triggers execute as expected
- Fix slow memory leak in Octopus Server
- Runbook multi-tenancy and deployment target status resets to default when cloning a project with runbooks
- Fixed the Build Information event categories on audit events
- Fixed an issue where Run a Kubernetes Script step would fail if the cluster was not available
- Fix issue where not found error was returned when creating releases for Git projects with deploy release actions
- Creating a release in the UI is blocked if using a Docker feed that fails to search (eg. GitHub Container Registry)
- Scheduled Tasks Logs are intermittently missing from the UI but appear in the shared .TaskLogs folder
- Change how we scan for task logs so we don't enumerate the whole task logs folder which caused performance issues for instances with a large amount of task logs
- Fixed issue with Unicode in project names
- Fix external feed lookup error when using a step template that uses an external feed many times in Git deployment process
- Fix issue where Git projects with step templates are permanently broken after changes are made to referenced data
- Performance telemetry is now logged at a verbose level when send telemetry server task runs
- Fixed an issue where Octopus Server would not start when the license is expired
- Fixed an issue where the configured Web Request Proxy was not respected in Health Checks for Azure App Service deployment targets
- SSH workers will no longer deadlock on parent/child deployments
New in Octopus Deploy 2022.2.7244 (Jul 12, 2022)
- Improved performance of viewing variable sets
New in Octopus Deploy 2022.3.2616 (Jun 23, 2022)
- Fixed an issue where deployments made via automatic lifecycle promotions would fail and remain persisted in a bad state
- Fix issue of YAML editor in Kubernetes step stripping characters from variable whose name contains colons
New in Octopus Deploy 2022.3.2387 (Jun 20, 2022)
- Workers now perform retention on their package cache
- Improve performance of git migration script
New in Octopus Deploy 2022.3.1591 (Jun 14, 2022)
- Improved the handling of missing steps when using the channel version rule designer
New in Octopus Deploy 2022.1.2744 (Jun 2, 2022)
- Config as Code API URLs renamed:
- We have made minor changes to some Config as Code API URLs and keys in the related links collection. These changes only impact version-controlled projects and should only cause issues if you're using any URLs directly.
New in Octopus Deploy 2022.1.2735 (Jun 1, 2022)
- Highlights:
- Configuration as Code (Config as Code) for deployments is now available! This means you can see your deployment process in your Git repo next to your application code and evolve them together. When Config as Code is enabled for a project, you can continue to use the Octopus UI as you always have, or you can edit the text files in your favorite editor. Work wherever you're the most productive.
- This release also includes other noteworthy updates:
- Visual Studio Code extension with Octopus Configuration Language (OCL) syntax highlighting, code snippets, and navigation tree
- Updated Terraform Provider with support for version-controlled projects
- New integrations:
- Buildkite plugins (early access) allow your build agents to create and deploy releases, push build information, and run runbooks as part of a pipeline
- Opsera integration lets you connect Octopus to other DevOps tools with no-code automation
- Octopus now supports connecting to multiple Azure DevOps organizations
- Updated TeamCity plugin with the latest Log4j security patches
- Automated step updates and discovery for steps built using our next-generation step package framework
- Octopus Deploy acquired the Dist technology
- Breaking changes:
- Config as Code API URLs renamed:
- We have made minor changes to some Config as Code API URLs and keys in the related links collection. These changes only impact version-controlled projects and should only cause issues if you're using any URLs directly.
New in Octopus Deploy 2022.1.2342 (Apr 12, 2022)
- Highlights:
- Configuration as Code (Config as Code) for deployments is now available! This means you can see your deployment process in your Git repo next to your application code and evolve them together. When Config as Code is enabled for a project, you can continue to use the Octopus UI as you always have, or you can edit the text files in your favorite editor. Work wherever you're the most productive.
- This release also includes other noteworthy updates:
- Visual Studio Code extension with Octopus Configuration Language (OCL) syntax highlighting, code snippets, and navigation tree
- Updated Terraform Provider with support for version-controlled projects
- New integrations:
- Buildkite plugins (early access) allow your build agents to create and deploy releases, push build information, and run runbooks as part of a pipeline
- Opsera integration lets you connect Octopus to other DevOps tools with no-code automation
- Octopus now supports connecting to multiple Azure DevOps organizations
- Updated TeamCity plugin with the latest Log4j security patches
- Automated step updates and discovery for steps built using our next-generation step package framework
- Octopus Deploy acquired the Dist technology
- Breaking changes:
- Config as Code API URLs renamed
- We have made minor changes to some Config as Code API URLs and keys in the related links collection. These changes only impact version-controlled projects and should only cause issues if you're using any URLs directly.
New in Octopus Deploy 2022.1.2300 (Apr 7, 2022)
- This release also includes other noteworthy updates:
- Visual Studio Code extension with Octopus Configuration Language (OCL) syntax highlighting, code snippets, and navigation tree
- Updated Terraform Provider with support for version-controlled projects
- New integrations:
- Buildkite plugins (early access) allow your build agents to create and deploy releases, push build information, and run runbooks as part of a pipeline
- Opsera integration lets you connect Octopus to other DevOps tools with no-code automation
- Octopus now supports connecting to multiple Azure DevOps organizations
- Updated TeamCity plugin with the latest Log4j security patches
- Automated step updates and discovery for steps built using our next-generation step package framework
- Octopus Deploy acquired the Dist technology
- Breaking changes:
- This release contains one breaking change.
- Config as Code API URLs renamed:
- We have made minor changes to some Config as Code API URLs and keys in the related links collection. These changes only impact version-controlled projects and should only cause issues if you're using any URLs directly.
New in Octopus Deploy 2022.1.2264 (Apr 4, 2022)
- Config as Code API URLs renamed:
- We have made minor changes to some Config as Code API URLs and keys in the related links collection. These changes only impact version-controlled projects and should only cause issues if you're using any URLs directly.
New in Octopus Deploy 2022.1.2232 (Mar 31, 2022)
- This release also includes other noteworthy updates:
- Visual Studio Code extension with Octopus Configuration Language (OCL) syntax highlighting, code snippets, and navigation tree
- Updated Terraform Provider with support for version-controlled projects
- New integrations:
- Buildkite plugins (early access) allow your build agents to create and deploy releases, push build information, and run runbooks as part of a pipeline
- Opsera integration lets you connect Octopus to other DevOps tools with no-code automation
- Octopus now supports connecting to multiple Azure DevOps organizations
- Updated TeamCity plugin with the latest Log4j security patches
- Automated step updates and discovery for steps built using our next-generation step package framework
- Octopus Deploy acquired the Dist technology
- Breaking changes:
- This release contains one breaking change.
- Config as Code API URLs renamed:
- We have made minor changes to some Config as Code API URLs and keys in the related links collection. These changes only impact version-controlled projects and should only cause issues if you're using any URLs directly.
New in Octopus Deploy 2021.2.8139 (Mar 10, 2022)
- Highlights:
- Built-in support for Google Cloud makes it easier to manage deployments and runbook automation on Google infrastructure — including containerized applications with Kubernetes.
- Other features allow you to:
- Integrate Octopus Deploy with business workflows using our no-code Workato connector
- Authenticate to Active Directory via LDAP when you're self-hosting Octopus on Linux
- Create more dynamic run conditions with new variable substitution (Octostache) filters
- Breaking changes:
- This release includes one breaking change.
- Steps that use bundled tools require the OctopusUseBundledTooling property:
- The new upgrade script sets the OctopusUseBundledTooling property to False for steps that use an execution container. Otherwise, the script sets the property to True or respects the legacy variables. This change only impacts users with custom Windows execution containers who rely on Octopus to inject the Azure or AWS tooling. Read about the workaround for that use case in the GitHub issue.
New in Octopus Deploy 2021.3.12372 (Mar 2, 2022)
- New default behavior for GET machines/{id}/tasks:
- We added runbook run activity to the deployment target screen. In support of this change, GET machines/{id}/tasks now returns both deployments and runbook runs. You can specify a type parameter to filter the results: Deployment or RunbookRun.
- Recommended version of Mono to run Calamari:
- Calamari can execute on the Mono framework. We recommend 5.14.0 as the minimum version of Mono for running Calamari.
- Recommended version of the Octopus .NET API client:
- We recommend 11.3.3453 as the minimum version of the Octopus .NET API client for interacting with Octopus Server 2021.3.
- Customers who use the Octopus .NET API client to work with teams, roles, and permissions must use version 11.3.3453 of the client (or newer) to ensure compatibility with Octopus Server 2021.3.7491 and newer.
New in Octopus Deploy 2021.3.12313 (Feb 24, 2022)
- New default behavior for GET machines/{id}/tasks:
- We added runbook run activity to the deployment target screen. In support of this change, GET machines/{id}/tasks now returns both deployments and runbook runs. You can specify a type parameter to filter the results: Deployment or RunbookRun.
- Recommended version of Mono to run Calamari:
- Calamari can execute on the Mono framework. We recommend 5.14.0 as the minimum version of Mono for running Calamari.
- Recommended version of the Octopus .NET API client:
- We recommend 11.3.3453 as the minimum version of the Octopus .NET API client for interacting with Octopus Server 2021.3.
- Customers who use the Octopus .NET API client to work with teams, roles, and permissions must use version 11.3.3453 of the client (or newer) to ensure compatibility with Octopus Server 2021.3.7491 and newer.
New in Octopus Deploy 2021.3.12205 (Feb 10, 2022)
- Updating a Certificate from Tenanted to Untenanted deployment mode without removing associated tenants doesn't save2021.3.12206
New in Octopus Deploy 2021.3.12196 (Feb 9, 2022)
- Add an associated space label for the Space Managers on Test Permissions Page
- Include Tenant name in Jira Environment DisplayName
- Fixed SQL timeout on the api/events endpoint
- Fixed an issue where Structured Configuration Variables were failing to correctly process XML files without the *.xml file extension (eg *.config)
- Fixed an issue where Structured Configuration Variables were failing to correctly process .properties files, and instead treating them as .yaml files
New in Octopus Deploy 2021.3.12132 (Feb 3, 2022)
- Fixed an issue where large amounts of Build Information data could cause high CPU and network load
New in Octopus Deploy 2021.3.8275 (Nov 24, 2021)
- Changes in Octopus 2021.3.8275:
- 7109 - Fixed JSON serialisation issues in OCL when enabling Config as Code
- 7152 - Can't add/edit Azure account variables
- 7153 - Repackaged node-bootstrapper tool manually to work properly with our .tgz archiving pipeline
- 7140 - Fixes a issue in which the Task History was not updated because QueueTime was set to the minimum value
- 2998 - Improved the performance of the release page when the project has a large number of package steps
- 7191 - Could not view old releases
- 7139 - Fixed a performance issue where querying a large number of ServerTasks was taking a long time
- 7190 - Octopus Client not working with Server
- 7137 - Migrating api/smtpconfiguration from Nancy to MVC
- 7131 - Migrating api/accounts from Nancy to MVC
- 7132 - Database collations errors now indicate what failed the collation test
- 7186 - Modify VCS space used logic to account for file being removed while its getting calculated
- 7126 - Long package names are now correctly handled by build information
- 6580 - Version correctly recorded for Linux targets during health check
- 7117 - On Windows, Tentacle.exe no longer requires admin rights for most CLI commands
- 6965 - Improved detection of a NuGet V3 feed and handling of NuGet V3 feeds that don't fully implement the NuGet V3 specification
- 7052 - Resolve an issue where there could be deadlocks and duplicate events when adding or deleting machines
- 7116 - Removed log noise from logging some expected exceptions as errors
- 7105 - Fixing an issue where viewing a release referencing packages created in other releases shows errors while loading release notes
- 7108 - Fix SQL Server error The server failed to resume the transaction
- 7096 - Migrating api/machineroles/all from Nancy to MVC
- 36 - JIRA Integration Octopus URL Virtual Directory Binding
- 35 - Jira integration authentication TEST button returns a 404 through reverse proxy.
- 7097 - Migrating api/machineroles/all from Nancy to MVC
- 7098 - Fix for server tasks being created with QueueTime of DateTimeOffset.MinValue
- 7099 - Reduce blob column sizes and make index unique
- 7103 - Add simple performance test for creating releases and deployments, logged to TeamCity build statistics
- 7079 - Migrated unknown variable types to a known type
- 7080 - Removed a visible semicolon when adding a deployment target
- 7101 - DynamicExtensionsScripts Configuration was changed
- 7045 - Fixed an issue where portal would use incorrect styles immediately after upgrading
- 7102 - Add stop-loss convention test for MVC controller parameters
- 7070 - Octopus Server running on linux can now connect to named SQL Server instances
- 7068 - Reduced the size of the docker image by restructuring the docker container layers
- 7100 - Revert "Tune GC settings to be more friendly to shared hosting" for performance
- 7104 - Cherry-pick performance changes to entity tracker
- 7024 - Fixed an issue where the process editor loses all state when resizing the browser window
- 6904 - You can now push Build Information to Maven packages with : in their name
- 7057 - Fixed Permissions Check to allow Audit Events to be written down during background tasks
- 7063 - Improved performance of auto-deploy logs
- 6987 - Enable anonymous bind support in LDAP authentication provider
- 7059 - Kubernetes Job resources do not include images
- 7008 - Add Google Cloud support to New-OctopusKubernetesTarget cmdlet
- 7015 - Fixed a permissions issue when attempting to delete deployment targets
- 7073 - Reversal of behavioral change introduced in 2021.2.5105 - Lifecycles on Releases are now sourced from the Channel again
- 6806 - Removing check for Azure Service Management API usage as it is no longer needed and displays an incorrect warning when Legacy Mode is enabled for Azure Web App deployment
- 7027 - Project trigger validation message is cryptic
- 7037 - Space deletions task no longer fails
- 7029 - Improve error message resulting from attempting to register an Account without setting resource permissions
- 56 - Fixed issue retrieving Jira issues that have comments
- 6903 - New installs of Octopus will now include FeedView and ActionTemplateView for Project Viewers, and ActionTemplateView and VariableView on Runbook Consumers to allow these roles to view action template steps. An error will be displayed instead of an infinite loading bar on viewing an action template step without enough permissions
- 7019 - Download custom version menu item should go to the Tentacle download page
- 7033 - Kubernetes YAML view does not remove unrecognised elements when saving and opening again
- 7007 - Fix Swagger documentation for DELETE apikeys
- 7023 - Kubernetes deployments on a Linux worker always wait for the deployment
- 7000 - Validate the JSON entered into the Azure Web Service step
- 6997 - Add support for structured variable replacements in S3 uploads
- 6993 - Allow CloudFormation templates to be deployed via S3
- 6998 - Export Terraform plan output in JSON
- 6938 - Existing certificates which point to a non-existent replacement certificate will no longer have an invalid reference. References to replacement certificates will be cleaned if the replacement certificate is deleted
- 6984 - Fixed issue where enabling legacy mode in Azure steps disabled role selection
- 6923 - AWS steps now support IMDSv2
- 6982 - Breaking change Added runbook run activity to the deployment target screen. GET machines/{id}/tasks now returns both deployments and runbook runs, and can be filtered by specifying a type parameter
- 6978 - Deploy Kubernetes Containers step custom resource with Windows line endings fails to deploy
- 6945 - Fetch Lifecycle usage data when accessing page directly
- 6975 - Fixes ordering of Kubernetes environment variables to allow substitution of Downstream APIs
- 6944 - Remove role input from variable preview, instead retrieve role scope based on the deployment target selected
- 6973 - Helm, Terraform, ARM Template, and CloudFormation steps referencing Docker images
- 6960 - Release retention now keeps the appropriate dashboard items in discrete channel mode
- 6970 - Validate variable types and correctly deserialize types to allow case-insensitive input
- 6966 - Terraform step will not parse template with "{{
- 6950 - Dashboard once again displays most recent releases per environment when there are multiple channels
- 6486 - Ensure correct status is shown on Deploy Child Project steps with manual intervention
New in Octopus Deploy 2021.2.7713 (Oct 22, 2021)
- Highlights:
- Built-in support for Google Cloud makes it easier to manage deployments and runbook automation on Google infrastructure — including containerized applications with Kubernetes.
- Other features allow you to:
- Integrate Octopus Deploy with business workflows using our no-code Workato connector
- Create more dynamic run conditions with new variable substitution (Octostache) filters
New in Octopus Deploy 2021.2.7706 (Oct 21, 2021)
- Steps that use bundled tools require the OctopusUseBundledTooling property:
- The new upgrade script sets the OctopusUseBundledTooling property to False for steps that use an execution container. Otherwise, the script sets the property to True or respects the legacy variables. This change only impacts users with custom Windows execution containers who rely on Octopus to inject the Azure or AWS tooling. Read about the workaround for that use case in the GitHub issue.
New in Octopus Deploy 2021.2.7697 (Oct 19, 2021)
- This release includes one breaking change:
- Steps that use bundled tools require the OctopusUseBundledTooling property:
- The new upgrade script sets the OctopusUseBundledTooling property to False for steps that use an execution container. Otherwise, the script sets the property to True or respects the legacy variables. This change only impacts users with custom Windows execution containers who rely on Octopus to inject the Azure or AWS tooling. Read about the workaround for that use case in the GitHub issue.
New in Octopus Deploy 2021.2.7693 (Oct 19, 2021)
- Highlights:
- Built-in support for Google Cloud makes it easier to manage deployments and runbook automation on Google infrastructure — including containerized applications with Kubernetes.
- Other features allow you to:
- Integrate Octopus Deploy with business workflows using our no-code Workato connector
- Authenticate to Active Directory via LDAP when you're self-hosting Octopus on Linux
- Create more dynamic run conditions with new variable substitution (Octostache) filters
New in Octopus Deploy 2021.2.7650 (Oct 5, 2021)
- Fixed auditing diffs for document modified entries
- Fixed Permissions Check to allow Audit Events to be written down during background tasks
New in Octopus Deploy 2021.2.7529 (Sep 21, 2021)
- Highlights:
- Built-in support for Google Cloud makes it easier to manage deployments and runbook automation on Google infrastructure — including containerized applications with Kubernetes.
- Other features allow you to:
- Integrate Octopus Deploy with business workflows using our no-code Workato connector
- Authenticate to Active Directory via LDAP when you're self-hosting Octopus on Linux
- Create more dynamic run conditions with new variable substitution (Octostache) filters
New in Octopus Deploy 2021.2.7462 (Sep 14, 2021)
- Highlights:
- Built-in support for Google Cloud makes it easier to manage deployments and runbook automation on Google infrastructure — including containerized applications with Kubernetes.
- Other features allow you to:
- Integrate Octopus Deploy with business workflows using our no-code Workato connector
- Authenticate to Active Directory via LDAP when you're self-hosting Octopus on Linux
- Create more dynamic run conditions with new variable substitution (Octostache) filters
- Breaking changes:
- This release includes one breaking change.
- Steps that use bundled tools require the OctopusUseBundledTooling property
- The new upgrade script sets the OctopusUseBundledTooling property to False for steps that use an execution container. Otherwise, the script sets the property to True or respects the legacy variables. This change only impacts users with custom Windows execution containers who rely on Octopus to inject the Azure or AWS tooling. Read about the workaround for that use case in the GitHub issue.
New in Octopus Deploy 2021.1.7738 (Sep 2, 2021)
- Highlights:
- Octopus 2021.1 is part of the Octopus 2021 Q2 release and delivers a better cloud experience. With this release, you can:
- Migrate Octopus projects to Octopus Cloud with self-service export/import.
- Integrate Octopus more easily with GitHub Actions and HashiCorp's Terraform.
- Deploy your Azure web apps with our improved Azure App Service step.
- Scale Octopus Cloud as your needs grow:
- Run more concurrent automation tasks.
- Persist more build and automation artifacts with best-in-class storage.
- Configure the Tentacle agent without root or admin permissions.
- Breaking changes:
- This release includes one breaking change.
- Change to support for Windows Docker images
- We have deprecated Windows Docker images for Octopus Server and Octopus CLI as customer uptake was low and Microsoft no longer supports the OS versions we were publishing (Windows 1809, 1903, and 1909).
- Customers are encouraged to use the Linux Docker image instead. Existing Windows images for Octopus Server and Octopus CLI will remain available from our Docker Hub repository, but those tagged as latest will no longer work on Windows.
- Octopus CLI is available as an exe, a .NET Core global tool, or via chocolatey. Please refer to our downloads page.
- We will continue to publish Windows Docker images for Tentacle. Once we've updated the images for Tentacle to Windows 2019 and Windows 20H2, we will deprecate the existing Windows 1809/1903/1909 containers.
New in Octopus Deploy 2021.1.7665 (Aug 13, 2021)
- This release includes one breaking change:
- Change to support for Windows Docker images:
- We have deprecated Windows Docker images for Octopus Server and Octopus CLI as customer uptake was low and Microsoft no longer supports the OS versions we were publishing (Windows 1809, 1903, and 1909).
- Customers are encouraged to use the Linux Docker image instead. Existing Windows images for Octopus Server and Octopus CLI will remain available from our Docker Hub repository, but those tagged as latest will no longer work on Windows.
- Octopus CLI is available as an exe, a .NET Core global tool, or via chocolatey. Please refer to our downloads page.
- We will continue to publish Windows Docker images for Tentacle. Once we've updated the images for Tentacle to Windows 2019 and Windows 20H2, we will deprecate the existing Windows 1809/1903/1909 containers.
New in Octopus Deploy 2021.1.7638 (Aug 11, 2021)
- Change to support for Windows Docker images:
- We have deprecated Windows Docker images for Octopus Server and Octopus CLI as customer uptake was low and Microsoft no longer supports the OS versions we were publishing (Windows 1809, 1903, and 1909).
- Customers are encouraged to use the Linux Docker image instead. Existing Windows images for Octopus Server and Octopus CLI will remain available from our Docker Hub repository, but those tagged as latest will no longer work on Windows.
- Octopus CLI is available as an exe, a .NET Core global tool, or via chocolatey. Please refer to our downloads page.
- We will continue to publish Windows Docker images for Tentacle. Once we've updated the images for Tentacle to Windows 2019 and Windows 20H2, we will deprecate the existing Windows 1809/1903/1909 containers.
New in Octopus Deploy 2021.1.7622 (Aug 3, 2021)
- Highlights:
- Octopus 2021.1 is part of the Octopus 2021 Q2 release and delivers a better cloud experience. With this release, you can:
- Migrate Octopus projects to Octopus Cloud with self-service export/import.
- Integrate Octopus more easily with GitHub Actions and HashiCorp's Terraform.
- Deploy your Azure web apps with our improved Azure App Service step.
- Scale Octopus Cloud as your needs grow:
- Run more concurrent automation tasks.
- Persist more build and automation artifacts with best-in-class storage.
- Configure the Tentacle agent without root or admin permissions.
- Breaking changes:
- This release includes one breaking change:
- Change to support for Windows Docker images:
- We have deprecated Windows Docker images for Octopus Server and Octopus CLI as customer uptake was low and Microsoft no longer supports the OS versions we were publishing (Windows 1809, 1903, and 1909).
- Customers are encouraged to use the Linux Docker image instead. Existing Windows images for Octopus Server and Octopus CLI will remain available from our Docker Hub repository, but those tagged as latest will no longer work on Windows.
- Octopus CLI is available as an exe, a .NET Core global tool, or via chocolatey. Please refer to our downloads page.
- We will continue to publish Windows Docker images for Tentacle. Once we've updated the images for Tentacle to Windows 2019 and Windows 20H2, we will deprecate the existing Windows 1809/1903/1909 containers.
New in Octopus Deploy 2021.1.7608 (Jul 30, 2021)
- Highlights:
- Octopus 2021.1 is part of the Octopus 2021 Q2 release and delivers a better cloud experience. With this release, you can:
- Migrate Octopus projects to Octopus Cloud with self-service export/import.
- Integrate Octopus more easily with GitHub Actions and HashiCorp's Terraform.
- Deploy your Azure web apps with our improved Azure App Service step.
- Configure the Tentacle agent without root or admin permissions.
- Scale Octopus Cloud as your needs grow:
- Run more concurrent automation tasks.
- Persist more build and automation artifacts with best-in-class storage.
- Breaking changes:
- This release includes one breaking change.
- Change to support for Windows Docker images
- We have deprecated Windows Docker images for Octopus Server and Octopus CLI as customer uptake was low and Microsoft no longer supports the OS versions we were publishing (Windows 1809, 1903, and 1909).
- Customers are encouraged to use the Linux Docker image instead. Existing Windows images for Octopus Server and Octopus CLI will remain available from our Docker Hub repository, but those tagged as latest will no longer work on Windows.
- Octopus CLI is available as an exe, a .NET Core global tool, or via chocolatey. Please refer to our downloads page.
- We will continue to publish Windows Docker images for Tentacle. Once we've updated the images for Tentacle to Windows 2019 and Windows 20H2, we will deprecate the existing Windows 1809/1903/1909 containers.
New in Octopus Deploy 2021.1.7595 (Jul 23, 2021)
- Change to support for Windows Docker images:
- We have deprecated Windows Docker images for Octopus Server and Octopus CLI as customer uptake was low and Microsoft no longer supports the OS versions we were publishing (Windows 1809, 1903, and 1909).
- Customers are encouraged to use the Linux Docker image instead. Existing Windows images for Octopus Server and Octopus CLI will remain available from our Docker Hub repository, but those tagged as latest will no longer work on Windows.
New in Octopus Deploy 2021.1.7469 (Jul 5, 2021)
- Migrate Octopus projects to Octopus Cloud with self-service export/import.
- Integrate Octopus more easily with GitHub Actions and HashiCorp's Terraform.
- Deploy your Azure web apps with our improved Azure App Service step.
- Configure the Tentacle agent without root or admin permissions.
- Scale Octopus Cloud as your needs grow:
- Run more concurrent automation tasks.
- Persist more build and automation artifacts with best-in-class storage.
New in Octopus Deploy 2021.1.7316 (Jun 10, 2021)
- Change to support for Windows Docker images:
- We have deprecated Windows Docker images for Octopus Server and Octopus CLI as customer uptake was low and Microsoft no longer supports the OS versions we were publishing (Windows 1809, 1903, and 1909).
- Customers are encouraged to use the Linux Docker image instead. Existing Windows images for Octopus Server and Octopus CLI will remain available from our Docker Hub repository, but those tagged as latest will no longer work on Windows.
- Octopus CLI is available as an exe, a .NET Core global tool, or via chocolatey. Please refer to our downloads page.
- We will continue to publish Windows Docker images for Tentacle. Once we've updated the images for Tentacle to Windows 2019 and Windows 20H2, we will deprecate the existing Windows 1809/1903/1909 containers.
New in Octopus Deploy 2020.6.5030 (May 18, 2021)
- Channels now require the ProjectView permission. Performing operations on Channels requires the ProjectView permission in addition to the existing permissions.
- Change to support for Windows Server 2008. Microsoft no longer supports Windows 2008. For this reason Octopus does not actively test against Windows 2008, and certain operating system specific issues may not be fixed.
- Removal of Package Redeployment option from the Project Settings UI - Packages are by default redeployed to machines even if the same version exists. To change this behaviour, a System Variable Octopus.Action.Package.SkipIfAlreadyInstalled can be added to the Project Variables with the value as True.
New in Octopus Deploy 2020.6.4923 (May 6, 2021)
- Added support for Terraform CLI v0.15.0
New in Octopus Deploy 2020.6.4915 (Apr 29, 2021)
- Worker pool results in the global search now open to the right place
- Ensured all enum parsing was case in-sensitive so that case differences in API calls or DB values don't cause a problem
- Version parsing tolerates version strings with spaces
New in Octopus Deploy 2020.6.4855 (Apr 13, 2021)
- Changes:
- Package upload no longer fails if there are more than 2100 projects with ARC enabled
- Import and Export commands in the migrator fail to mask the password
New in Octopus Deploy 2020.6.4809 (Apr 12, 2021)
- Allow Project cloning when user has ProjectGroup scoping on ProjectCreate permission
- Cleaning the package cache will no longer block other scheduled maintenance jobs from executing
- Reduced the performance impact of loading a release with many associated Library Variable Sets
New in Octopus Deploy 2020.6.4788 (Apr 1, 2021)
- The latest docker tag should not be sorted as the latest version.
- Custom script steps do not evaluate release notes or build information when using dynamic packages
- Project API calls are case insensitive matching the project slug
- Fixes an issue where commits were omitted from the release screen when the VCS type is unknown
- The Octopus Server version number is now displayed as major.minor (Build buildcounter)
New in Octopus Deploy 2020.6.4722 (Mar 23, 2021)
- Notes are now snapshotted with the deployment process
- Local privilege escalation in Octopus Server (CVE-2021-26556)
- Backport Fix - The WebUI HTTP listener now retries if there is a network error that causes it to terminate
- Fixed an error calling octo create-release when package version supplied for a deploy a release step does not exist
- Pen Test Report: Insecure Cookie (2019.6 LTS)
- Updating no-javascript link to https
- Improve Performance of Dashboard by indexing temp table
- Fixed single quotes arguments passed to Terraform
- Improved the speed of the automatic release creation after a package upload
- Fixed an issue where an excessive amount of requests were being made for tenant tag sets when on the deployment target settings page
- Improved the performance the Projects API when many projects use features that are based on step names
- Save terraform sensitive values as Octopus sensitive values
- Prevented infinite polling loop when navigation happens while request is in flight
- Prevented infinite polling loop when navigation happens while request is in flight
- New-OctopusAzureWebAppTarget command slot name parameter is now honoured
- UI fix for variable editor popover menus being visually cut off
- Fragmented database indexes are automatically rebuilt or reorganized after other upgrade script have run
- Improved the performance of the permission loading that occurs after a Team, User or Role is changed
New in Octopus Deploy 2020.6.4701 (Mar 16, 2021)
- Library Variables Usage can time out
- Script Module Usage is slow
New in Octopus Deploy 2020.5.8 (Feb 17, 2021)
- Fixed parsing of service messages if they were split across multiple lines on SSH targets
New in Octopus Deploy 2020.5.7 (Feb 15, 2021)
- Highlights:
- Octopus 2020.5 includes a collection of improvements to support self-signed certificates, Terraform updates, Kubernetes updates, automation step notes, and a ton of behind-the-scenes changes to support our upcoming Config as Code feature:
- Create self-signed certificates in the certificate library
- GitHub container registry support
- Terraform update - Inline scripts now support HCL2 and Terraform 0.12+
- Add markdown notes to automation steps
- Behind-the-scenes changes to support our upcoming Config as Code feature.
- Kubernetes updates:
- Expose envFrom fields in Deploy Kubernetes containers step
- Allow DaemonSets and StatefulSets to be created and deployed
- Breaking changes:
- This release includes two breaking changes:
- Importing an Action Template with a package reference will now validate the Feed Id. This change means that Feed View permission is required to import an Action Template with a package reference.
- Octopus Cloud added the ability to record some metrics so we could do performance tuning. This functionality is no longer used, and we have removed this support. We have updated Octopus DSC to deprecate the LogTaskMetrics and LogRequestMetrics properties to reflect this.
New in Octopus Deploy 2020.5.6 (Jan 28, 2021)
- Fixes issue where step template settings were not applied
- Possible fix to tasks hanging due to deadlock when accessing the log file
New in Octopus Deploy 2020.5.5 (Jan 6, 2021)
- Breaking changes:
- This release includes two breaking changes:
- Importing an Action Template with a package reference will now validate the Feed Id. This change means that Feed View permission is required to import an Action Template with a package reference.
- Octopus Cloud added the ability to record some metrics so we could do performance tuning. This functionality is no longer used, and we have removed this support. We have updated Octopus DSC to deprecate the LogTaskMetrics and LogRequestMetrics properties to reflect this.
New in Octopus Deploy 2020.5.4 (Jan 4, 2021)
- Highlights:
- Octopus 2020.5 includes a collection of improvements to support self-signed certificates, Terraform updates, Kubernetes updates, automation step notes, and a ton of behind-the-scenes changes to support our upcoming Config as Code feature.
- Create self-signed certificates in the certificate library
- GitHub container registry support
- Kubernetes updates
- Expose envFrom fields in Deploy Kubernetes containers step
- Allow DaemonSets and StatefulSets to be created and deployed
- Terraform update - Inline scripts now support HCL2 and Terraform 0.12+
- Add markdown notes to automation steps
- Behind-the-scenes changes to support our upcoming Config as Code feature.
- Breaking changes:
- This release includes two breaking changes.
- Importing an Action Template with a package reference will now validate the Feed Id. This change means that Feed View permission is required to import an Action Template with a package reference.
- Octopus Cloud added the ability to record some metrics so we could do performance tuning. This functionality is no longer used, and we have removed this support. We have updated Octopus DSC to deprecate the LogTaskMetrics and LogRequestMetrics properties to reflect this.
New in Octopus Deploy 2020.5.3 (Dec 21, 2020)
- Fixed an issue where upgrading from an older version of Octopus Server resulted in corrupt FeedId values stored in the database
- Fixed an issue where bash script output would not stream back to Octopus Server in real time
- Re-introduces support for api-key query string parameter
- Fixed issue with virtual directories returning 404 if accessed with no trailing slash
- Structured Configuration variables now tries all parsers for files that don't match well-known file extensions
- Fixed bug with Check Upgrade task timing out on Octopus Cloud instances
- Allow nuget v3 package download timeout to be overridden via the special variable OctopusNugetHttpTimeout
New in Octopus Deploy 2020.5.2 (Dec 15, 2020)
- Create self-signed certificates in the certificate library
- GitHub container registry support
- Kubernetes updates
- Expose envFrom fields in Deploy Kubernetes containers step
- Allow DaemonSets and StatefulSets to be created and deployed
- Terraform update - Inline scripts now support HCL2 and Terraform 0.12+
- Add markdown notes to automation steps
- Behind-the-scenes changes to support our upcoming Config as Code feature.
New in Octopus Deploy 2020.5.0 (Nov 24, 2020)
- 6382 - All the Deploy Kubernetes containers step to define deferred packages in temples
- 6472 - Calamari tar extraction now uses UTF8
- 6476 - Variable replacement is now run against yalues.yaml on helm charts
- 6482 - Fix issue where a large number of polling Tentacles can significantly slow down Octopus Server
- 6497 - Fixes issue with migrator failing to export when related machines exist in deployments
- 6504 - Fix issue where parent step run conditions would override a child's
- 6522 - Reduced the chance of log contention when scheduled jobs are run on different nodes
- 6527 - Helm upgrade step now works when package ID doesn't match the archive subdirectory
- 6532 - Child step based on custom template can't be updated if it has a variable run condition
- 6533 - Updating library step template in process requires browser refresh to show changes
- 6535 - "Force Version Selection" override for package selection was not being displayed in certain circumstances
- 6536 - Fix potentially invalid event diffs
- 6540 - Add support for readiness gates in the Deploy Kubernetes containers step
- 6541 - Fix server task log files being left open
- 6546 - Fix NGINX Web Server feature potentially naming configuration files incorrectly
- 6547 - Fix Legacy IIS feature potentially targeting the incorrect web site/virtual directory
- 6548 - Fix deployments sometimes incorrectly not being skipping when SkipIfAlreadyInstalled variable is set
- 6549 - fixes bug in which cloning a step into another project would fail
- 6551 - Allow Daemonsets and Statefulsets to be created and deployed
- 6553 - Fixes error displayed when deleting machine policies
- 6558 - Fix crash in lost-master-key command
- 6561 - Allow Java archives to not compress their contents
- 6562 - Inline Terraform scripts now support HCL2 and Terraform 0.12+
- 6567 - GitHub Container Registry now supported more gracefully
- 6571 - Fixed error on Account Usages when referenced via a Runbook run
- 6574 - fixes issue where tentacle and space names would be truncated when running configure-tentacle.sh
- 6578 - Fix URL encoding bug with checking for upgrades job
- 6582 - Importing an Action Template with a package reference will validate the Feed Id. Breaking change: Feed View permission required to import an Action Template with a Package Reference
- 6583 - Create self signed certificates in the certificate library
- 6585 - Linux Docker image can now be run as the user octopus
- 6587 - Expose envFrom fields in Deploy Kubernetes containers step
- 6588 - Improve audit screen query performance
- 6593 - Version component extraction as filter
- 6604 - Fix bug where bash script can reveal sensitive variable values (CVE-2020-25825)
- 6608 - Deployment steps can now have notes
- 6609 - Fixed summary when variable bindings are used in Deployment Condition field
- 6612 - Always include the build information from the current release when deploying, even if it's not the latest version
- 6637 - Fix bug where bash script can reveal sensitive variable values - CVE: CVE-2020-25825
- 6642 - fixes issue where Set-StrictMode in dynamic infrastructure scripts would cause an error during execution
- 6650 - Improved text for Tentacle upgrade policy options
- 6672 - Fixed an issue with timeouts for Maven artifact downloads
New in Octopus Deploy 2020.4.10 (Oct 29, 2020)
- Highlights:
- Better configuration file support for YAML, JSON, XML, and Java properties files, and built-in Worker Pools on Octopus Cloud for both Windows and Linux.
- Better configuration file updates for Java, NodeJS, Ruby and more: is an update to our JSON configuration variable replacement support to make it even more useful. It now supports JSON, YAML, XML, and Java Properties files.
- Octopus Cloud: Built-in Windows and Linux Worker Pools, and simpler dependency management. Octopus Cloud provides dynamic workers to execute scripts against your services and infrastructure. This update adds better cross-platform support with images for modern Windows and Linux operating systems. All Worker images support execution containers, which let you execute deployment work in isolation without the need to manage dependencies and containers.
New in Octopus Deploy 2020.4.9 (Oct 26, 2020)
- Better configuration file support for YAML, JSON, XML, and Java properties files, and built-in Worker Pools on Octopus Cloud for both Windows and Linux.
- Better configuration file updates for Java, NodeJS, Ruby and more: is an update to our JSON configuration variable replacement support to make it even more useful. It now supports JSON, YAML, XML, and Java Properties files.
- Octopus Cloud: Built-in Windows and Linux Worker Pools, and simpler dependency management. Octopus Cloud provides dynamic workers to execute scripts against your services and infrastructure. This update adds better cross-platform support with images for modern Windows and Linux operating systems. All Worker images support execution containers, which let you execute deployment work in isolation without the need to manage dependencies and containers.
New in Octopus Deploy 2020.4.6 (Oct 15, 2020)
- Highlights:
- Better configuration file support for YAML, JSON, XML, and Java properties files, and built-in Worker Pools on Octopus Cloud for both Windows and Linux.
- Better configuration file updates for Java, NodeJS, Ruby and more: is an update to our JSON configuration variable replacement support to make it even more useful. It now supports JSON, YAML, XML, and Java Properties files.
- Octopus Cloud: Built-in Windows and Linux Worker Pools, and simpler dependency management. Octopus Cloud provides dynamic workers to execute scripts against your services and infrastructure. This update adds better cross-platform support with images for modern Windows and Linux operating systems. All Worker images support execution containers, which let you execute deployment work in isolation without the need to manage dependencies and containers.
New in Octopus Deploy 2020.4.5 (Oct 13, 2020)
- Highlights:
- Better configuration file updates for Java, NodeJS, Ruby and more: is an update to our JSON configuration variable replacement support to make it even more useful. It now supports JSON, YAML, XML, and Java Properties files.
- Octopus Cloud: Built-in Windows and Linux Worker Pools, and simpler dependency management. Octopus Cloud provides dynamic workers to execute scripts against your services and infrastructure. This update adds better cross-platform support with images for modern Windows and Linux operating systems. All Worker images support execution containers, which let you execute deployment work in isolation without the need to manage dependencies and containers.
New in Octopus Deploy 2020.4.4 (Oct 12, 2020)
- df command in healthchecks can hang on CentOS
New in Octopus Deploy 2020.3.4 (Aug 31, 2020)
- Highlights:
- Runbooks improvements: This release includes a batch of customer-driven improvements, including runbook-only projects, Octopus CLI support, environment scoping, guided failure mode per runbook, and the addition of runbook retention policies.
- Jenkins Pipelines support enables you to integrate with Octopus from your Jenkinsfile.
- Streamlined process editor allows you to edit multiple steps at once and save your changes with a single update.
- Octopus Linux Docker image (Early access) is now available, making it possible to run Octopus in a Linux Docker container.
- Breaking changes:
- Deprecated our Azure VM extensions - We recommend using PowerShell DSC as a replacement. Our documentation covers this decision and links to further articles on how to achieve this with PowerShell DSC. See this article for instructions to accomplish this with Amazon Web Services as well.
- Updated Deploy to IIS step - We have updated this step to remove support to deploy to Azure App Services. We recommend using our Azure support instead.
New in Octopus Deploy 2020.2.11 (Jun 4, 2020)
- Execution containers for workers let you execute deployment work in isolation without the need to manage dependencies and containers.
- Integrated change management with Jira Service lets teams create change requests during their deployment automatically.
- Better run conditions adds deployment process improvements, including rolling deployment and machine level variable conditions.
- Fast variable lookups with our improved code unlocks the ability to quickly add Octopus variables into your custom scripts without touching the mouse
New in Octopus Deploy 2020.2.8 (May 25, 2020)
- Highlights:
- Execution containers for workers (EAP), Jira Service Desk change requests, better run conditions and fast variable lookups with our improved code editor.
- Execution containers for workers let you execute deployment work in isolation without the need to manage dependencies and containers.
- Integrated change management with Jira Service lets teams create change requests during their deployment automatically.
- Better run conditions adds deployment process improvements, including rolling deployment and machine level variable conditions.
- Fast variable lookups with our improved code unlocks the ability to quickly add Octopus variables into your custom scripts without touching the mouse.
- Breaking changes:
- Octopus 2020.1 introduced updated minimum requirements for running Octopus Server to Windows Server 2012 R2 and SQL Server 2017. This release is now enforcing the SQL Server minimum requirements.
New in Octopus Deploy 2020.1.18 (May 21, 2020)
- Fixed cloned tenants not being editable if the tenant they were cloned from got deleted
- Fixed Package Feed variable not found Error in the UI
New in Octopus Deploy 2020.1.17 (May 12, 2020)
- Highlights:
- DarkMode, Improved Octopus CLI support on macOS and Linux, and environment specific Worker Pools.
- Dark Mode is cool and it's easier on your eyes.
- Octopus and Octopus CLI are more at home on Linux and macOS: AWS and Azure built-in steps are cross-platform, and you can now install and use the Octopus CLI via Homebrew, Yum, and APT.
- Environment and tenant specific worker pools: New worker pool variables unlock the ability to have dedicated worker pools for different environments or tenant tags.
- Breaking changes:
- This release includes the following breaking changes.
- Octopus Server minimum requirements - Octopus 2020.1 raises the minimum requirements for running Octopus Server to Windows Server 2012 R2 and SQL Server 2017.
- Library variable set permission changes - You can now scope variables stored inside library variable sets to environments and tenants, giving you fine-grain permissions and more consistent access control.
New in Octopus Deploy 2020.1.16 (May 7, 2020)
- Highlights:
- DarkMode, Improved Octopus CLI support on macOS and Linux, and environment specific Worker Pools.
- Dark Mode 😎 is cool and it's easier on your eyes.
- Octopus and Octopus CLI are more at home on Linux and macOS: AWS and Azure built-in steps are cross-platform, and you can now install and use the Octopus CLI via Homebrew, Yum, and APT.
- Environment and tenant specific worker pools: New worker pool variables unlock the ability to have dedicated worker pools for different environments or tenant tags.
- Breaking changes:
- This release includes the following breaking changes.
- Octopus Server minimum requirements - Octopus 2020.1 raises the minimum requirements for running Octopus Server to Windows Server 2012 R2 and SQL Server 2017.
- Library variable set permission changes - You can now scope variables stored inside library variable sets to environments and tenants, giving you fine-grain permissions and more consistent access control.
New in Octopus Deploy 2020.1.15 (Apr 28, 2020)
- Fixes an issue where deploying a package to an Azure Cloud Service target would result in an infinite loop during deployment
- Added "Audit Trail" option to overflow menu for spaces
New in Octopus Deploy 2020.1.13 (Apr 22, 2020)
- Removed Release Lane and Long-Term Support concepts from Octopus Server - every release from 2020.1 comes with 6 months support
- Fixes a UI error when creating a scheduled trigger
- Fixes an issue where a run condition based on a variable expression doesn't work when the variable is scoped to a process
- SynchronizeExternalSecurityGroupsForUsers task is not executed when AD integration is not present
New in Octopus Deploy 2020.1.12 (Apr 16, 2020)
New in Octopus Deploy 2020.1.11 (Apr 15, 2020)
- Dark Mode is cool and it's easier on your eyes
- Octopus and Octopus CLI are more at home on Linux and macOS: AWS and Azure built-in steps are cross-platform, and you can now install and use the Octopus CLI via Homebrew, Yum, and APT
- Environment and tenant specific worker pools: New worker pool variables unlock the ability to have dedicated worker pools for different environments or tenant tags
New in Octopus Deploy 2020.1.10 (Apr 8, 2020)
- Fix bug where the Tenant Common Variable Tab is missing when LibraryVariableSetView permissions are scoped to a Tenant or Environment
- Fixed error with upgrading from 2018 versions to 2020.1
- Maven artifacts are properly selected when creating a release with channel rules
New in Octopus Deploy 2020.1.8 (Mar 31, 2020)
- Fix bug where Java-based deployments failed on non-Windows targets
- Fix bug where you can't download plain text artifacts greater than 4KB in size
New in Octopus Deploy 2020.1.5 (Mar 19, 2020)
- On premise Active Directory privilege escalation bug fixed
- Tentacle upgrade button is displayed again
- Using a Deploy Package step works again when targeting one of the deprecated Azure Web App targets
New in Octopus Deploy 2019.13.7 (Feb 20, 2020)
- Changes in Octopus 2019.13.7:
- 6143 - Fix to the variables/all endpoint when runbooks are in use
- 6152 - Fix DateTime overflow and year skip in db upgrade schedule conversion
- 6164 - Fixed up the messages printed in the summary section of health checks
- 6186 - UI will now default to the last accessed space when no explicit space is provided
New in Octopus Deploy 2019.13.6 (Feb 19, 2020)
- Fixing import migrations for multiple project triggers and runbooks
- Fixed issue preventing Azure DevOps Issue Tracker to be enabled on Octopus Cloud
- Fix icon alignment for copy API key button
- Fix a race condition on the runbook run page which was causing previews to get out of sync
- Fixed bug where package extraction is failing on OSX and BSD targets
New in Octopus Deploy 2019.13.3 (Feb 2, 2020)
- 6140 - Fix for a blocking TypeScript error occurring in IE11
New in Octopus Deploy 2019.13.2 (Jan 31, 2020)
- Changed Releases screen so it doesn't go boom if your instance/space doesn't have any environments
- Reduce likelihood of dashboard queries timing out
- Fix for user lockout when exceeding limit of wrong password attempts
- Package IDs with slashes break the NGINX step by placing conf files in a subdirectory
New in Octopus Deploy 2019.13.1 (Jan 29, 2020)
- Fix for dialog issue in Firefox/Edge with the Kubernetes step template
- Resolved issue preventing k8s raw yaml volume from being saved if it contained a variable expression
- Fix to consider both release and runbook snapshots before deleting the shared variable set snapshot
- Fixing runbook run and snapshot variable links to match the UI redirection logic
- Scheduled triggers for Operations Runbooks that have prompted variables no longer throw a NullReferenceException
- Scheduled deployments and runbook runs will now use default prompted variable values
- Stop icons shrinking in Team lists when the name/description is long
- "An item with the same key has already been added" error with the NGINX step and multiple regex based locations
- Drop experimental header check on project/summaries to avoid issues with proxies
New in Octopus Deploy 2019.11.3 (Jan 8, 2020)
- Disable adding a new project in the UI when there are no Project Groups or Lifecycles
- The target limit specified in the license is enforced now
- Fix React Error in container within Kubernetes step
- External groups are now indicated on users' teams lists
- Fixed layout issue on the User Role tab on the Team Edit page
New in Octopus Deploy 2019.11.2 (Jan 7, 2020)
- 4440 - Include experimental support for linux-arm SSH targets
- 5687 - Newline characters in variables are persisted after editing
- 5822 - Cancelling a health check for an offline Tentacle now cancels much quicker, and no longer waits the full connect timeout
- 5840 - Fixed a bug where deleting a parent step might delete the wrong step
- 6060 - Update UI to Show Spaces dropdown when permitted to add spaces or has access to multiple spaces
- 6066 - Improved performance for many places using projects, including the projects page and the tasks page
- 6081 - Handled trailing semicolons in the address field of the send email step
- 6085 - Fixed issue where sometimes server tasks are not processed until restart
New in Octopus Deploy 2019.11.1 (Dec 17, 2019)
- Highlights:
- Official Jenkins Plugin and Operations Runbooks:
- Official Octopus Deploy Jenkins plugin enables teams to integrate their Jenkins builds with Octopus deployments.
- Operations Runbook platform for automating routine maintenance and emergency operations tasks. Runbook examples include infrastructure provisioning, database management, and website failover and restoration.
- Familiar configuration process for anyone who has configured a deployment processes.
- Execute Runbooks directly against infrastructure on-demand or on a schedule (nightly, weekdays, once a month etc.) as per your teams needs.
- Built for teams:
- Runbooks can be parameterized with prompted variables.
- Make changes with confidence, publishing only once they have been safely tested.
- Updated our suite of Octopus build server plugins to rename our Push Package Metadata step to Push Build Information.
- Breaking changes:
- Scheduled Triggers The API for scheduled triggers has changed in this release. In an effort to make trigger behaviour more predictable the trigger filter for daily and days per week has changed. See this issue for further details.
New in Octopus Deploy 2019.11.0 (Dec 12, 2019)
- Highlights:
- Official Jenkins Plugin and Operations Runbooks
- Official Octopus Deploy Jenkins plugin enables teams to integrate their Jenkins builds with Octopus deployments.
- Operations Runbook platform for automating routine maintenance and emergency operations tasks. Runbook examples include infrastructure provisioning, database management, and website failover and restoration.
- Familiar configuration process for anyone who has configured a deployment processes.
- Execute Runbooks directly against infrastructure on-demand or on a schedule (nightly, weekdays, once a month etc.) as per your teams needs.
- Built for teams:
- Runbooks can be parameterized with prompted variables.
- Make changes with confidence, publishing only once they have been safely tested.
- Updated our suite of Octopus build server plugins to rename our Push Package Metadata step to Push Build Information.
- Breaking changes:
- Scheduled Triggers The API for scheduled triggers has changed in this release. In an effort to make trigger behaviour more predictable the trigger filter for daily and days per week has changed. See this issue for further details.
New in Octopus Deploy 2019.10.12 (Dec 5, 2019)
- Resolved an issue that prevented deployments to Cloud Regions
New in Octopus Deploy 2019.10.11 (Dec 4, 2019)
- 3765 - The start time for targets in rolling deployments is now shown correctly in the log headers
- 6035 - Reduce network IO usage in Windows listening tentacles
- 6037 - Fixed db query to improve speed of task event query
New in Octopus Deploy 2019.10.10 (Nov 28, 2019)
- Option to not re-deploy release for scheduled trigger with "deploy latest release" action
- Fix on screen error for channel creation
New in Octopus Deploy 2019.10.9 (Nov 25, 2019)
- 4559 - Fixed bug causing new targets to not be included in deployments when targets are re-included by the same health check
- 5945 - Update the Jira Issue Tracker test button to do a more thorough check of the user's permissions and ability to read work items
- 6010 - Fixed race condition when selecting tenants or tags when creating a release possibly causing the wrong deployment to be shown
- 6015 - Added a UriPart function to Octostache
- 6023 - Fixed issue in health checks where machines were not correctly re-included into the deployment
- 6024 - The Deployments and Operations menus within a project now always remain open
- 6025 - Fixed bug that was excluding targets from deployments if they were "healthy with warnings"
- 6026 - Fixed dropdown "select as you type" functionality
- 6027 - Fixed a bug where connections may have been opened unnecessarily when querying the /api/projects/all endpoint
- 6031 - Fixed a regression with force package deployment that was introduced in 2019.10
New in Octopus Deploy 2019.10.8 (Nov 20, 2019)
- 5173 - Included Azure CLI tools when deploying to Kubernetes with Azure credentials
- 5989 - Allow configuring pod service account in deploy k8s containers step
- 5994 - Improved tenanted deployment preview screen to batch API calls which improves performance
- 6011 - Deferred deployments are now taken into account on the project and main dashboards
- 6012 - Allow variables to be set for tentacle health checks
- 6013 - Show a preview of the release notes on the deployment page with a button to show more
- 6014 - Aligned the retention of non-deployment and non-health check tasks to be the last 20 and the last 30 days
- 6017 - Fixed a bug with GitHub feed tags not getting more than the first 100 tags
- 6019 - Fixed issue where the Azure PowerShell modules weren't configured correctly when deploying a helm chart to Azure AKS
New in Octopus Deploy 2019.10.4 (Nov 4, 2019)
- Synchronization external security groups task hangs
- Fixed an error calling octo create-release when package version supplied for a deploy a release step does not exist
- Changed machine license check to sql column for better performance
- Added log warning in Calamari when it detects Management Certificates in use on an Azure Web App step
- Improved Let's Encrypt problem explanations with details of the remote status
- Details coming soon
- Details coming soon
New in Octopus Deploy 2019.10.2 (Oct 31, 2019)
- 5802 - Enforce version checks for Octopus.Migrator
- 5923 - OpenID Connect authentication provider packaging updated
- 5924 - Fix for StackOverflowException causing Octopus Server to crash
- 5927 - Fix for recursive variable loop when there isn't one
- 5931 - Fix task screen crashing when viewings tasks unrelated to deployments and runbooks
- 5933 - UI option to load a sample process for new projects
- 5935 - "Missing Resource" chip no longer displaying on Machine Clean Up Events page
- 5936 - Lowered the severity of some messages logged by Halibut when client connections timeout
- 5937 - Fixed tenant scoping issue with the DeploymentView permission, which would prevent all deployments from appearing on the dashboard
- 5939 - Fixed bad data for release versions in package metadata
- 5940 - Prevent modification of some of the user roles for Octopus Administrators and Octopus Managers
New in Octopus Deploy 2019.10.1 (Oct 21, 2019)
- Fix for duplicate key exception when cleaning up build information/package metadata
- UI performance boost for Octopus instances with lots of projects doing lots of deployments
- On the project process view, the step list overlaps if the step name has long words
- Fix issue where project switcher would open a new tab when clicking away
- Fixed issue with Build Information upgrade script that would block if it couldn't find expected old indexes
- UI rendering performance improvements to the projects list screen for customers operating at scale
- Fix for handling of deployment processes where a null package collection may result in a Value cannot be null error during deployment
- Fix an issue where adding a project group would result in an empty page being shown
New in Octopus Deploy 2019.10.0 (Oct 15, 2019)
- Fix for error saying unable to delete a step template that's in use
New in Octopus Deploy 2019.9.0 (Oct 10, 2019)
- This release bundles the following command line tools and frameworks:
- AWS CLI - 1.16.178
- AWS PowerShell Cmdlets - 3.3.390
- Azure CLI - 2.0.50
- Azure Powershell Cmdlets - 6.13.1
- Terraform CLI - 0.11.8
- Terraform AWS provider - 1.39.0
- Terraform Azure provider - 0.1.1
- Erraform AzureRM provider - 1.17.0
New in Octopus Deploy 2019.8.4 (Sep 12, 2019)
- Fixed issue where step delete silently fails when step is used in the versioning strategy
- Fixed replace option for Upload Package dialog and client backwards compatibility
- Fixed issue with tenant variable editing, which occurred if a team the user was in had a role scoped to an environment
- Fixed Octopus ID authentication provider's default configuration to stop warnings appearing in the server logs unnecessarily
- Fix for NullReferenceException in CheckForOctopusUpgrade reported in server dignostic errors
New in Octopus Deploy 2019.8.3 / 5.0.4 Tentacle (Sep 9, 2019)
- Improved startup performance when many files exist in the Octopus Server directory
- Empty annotation, label, secret and configmap values are now passed through to K8S
- Includes bundled Tentacle 5.0.4 which includes the new Linux Tentacle
New in Octopus Deploy 2019.8.2 (Sep 5, 2019)
- 5647 - Package acquisition now runs after manual intervention for steps with additional packages
- 5803 - Automatic redirect to secure WebUI binding now works for localhost binding
- 5820 - Fix misaligned deployment process chips
- 5825 - Certificates without a private key can now be installed into another user's key store on windows
- 5826 - Fixed the User edit page so the Reset Password button is only enabled based on the same permissions checks logic the API is using
- 5830 - Updated bundle Tentacle to 5.0.3 to fix crash when launching Tentacle Manager
- 5834 - Includes bundled Tentacle 5.0.3 with fix for memory leak with Listening Tentacles
New in Octopus Deploy 2019.8.1 (Aug 29, 2019)
- Highlights:
- 2019.8 includes:
- Improved deployment process editor: Quickly jump between steps when editing the deployment process
- Cloning Tenants
- More health check scheduling options: Health checks can be configured to run on a cron expression, or to never run
- Allow overriding namespace in Kubernetes steps
- New Variable Filter expressions: Trim, Substring, Truncate, UriEscape, UriDataEscape
- Copy and paste to add certificates: Certificates can now be pasted as text directly into the portal
- This release bundles the following command line tools and frameworks:
- AWS CLI - 1.16.178
- AWS PowerShell Cmdlets - 3.3.522
- AWS Azure CLI - 2.0.50
- AWS Powershell Cmdlets - 6.13.1
- Terraform CLI - 0.11.13
- Terraform AWS provider - 2.8.0
- Terraform Azure provider - 0.1.1
- Terraform AzureRM provider - 1.27.1
New in Octopus Deploy 2019.8.0 (Aug 29, 2019)
- Improved deployment process editor: Quickly jump between steps when editing the deployment process
- Cloning Tenants
- More health check scheduling options: Health checks can be configured to run on a cron expression, or to never run
- Allow overriding namespace in Kubernetes steps
- New Variable Filter expressions: Trim, Substring, Truncate, UriEscape, UriDataEscape
- Copy and paste to add certificates: Certificates can now be pasted as text directly into the portal
- Tools
- This release bundles the following command line tools and frameworks:
- AWS CLI - 1.16.178
- AWS PowerShell Cmdlets - 3.3.522
- AWS Azure CLI - 2.0.50
- AWS Powershell Cmdlets - 6.13.1
- Terraform CLI - 0.11.13
- Terraform AWS provider - 2.8.0
- Terraform Azure provider - 0.1.1
- Terraform AzureRM provider - 1.27.1
New in Octopus Deploy 2019.7.10 (Aug 16, 2019)
- Highlights:
- Octopus 2019.7 is a significant release even though it doesn't include any user-facing features. It includes technical changes to retarget Octopus Deploy to .NET Framework 4.7.2 and .NET Core 2.2 so Octopus can run natively on Linux and in Linux containers. This change is initially for Octopus Cloud and it will be extended to Octopus self-hosted in the future.
- Watch our blog for some great technical blog posts on what this involved and our lessons learned.
- Breaking changes:
- Most customers can upgrade directly to Octopus Server 2019.7, except those hosting Octopus Server on Windows Server 2008 SP2. This blog post has more details about who will be affected, and what you can do to upgrade.
- Don't worry, the Octopus Server installer will prevent you from accidentally upgrading if your host operating system will not be supported.
- Tools
- This release bundles the following command line tools and frameworks:
- AWS CLI - 1.16.178
- AWS PowerShell Cmdlets - 3.3.522
- AWS Azure CLI - 2.0.50
- AWS Powershell Cmdlets - 6.13.1
- Terraform CLI - 0.11.13
- Terraform AWS provider - 2.8.0
- Terraform Azure provider - 0.1.1
- Terraform AzureRM provider - 1.27.1
New in Octopus Deploy 2019.7.9 (Aug 15, 2019)
- 5772 - Metadata button only expands/collapses its own section
- 5773 - Expose Docker Image labels as Project Variables
- 5774 - Adds additional validation to the deployment process API to guard against PackageReference.Properties from accepting null values
- 5777 - Fixed a memory leak with listening Tentacles
- 5779 - Creating a space no longer requires AdministerSystem. SpaceCreate should be sufficient
New in Octopus Deploy 2019.7.8 (Aug 13, 2019)
- 5722 - Fix for slow performing release and deployment queries
- 5762 - Added more information about target's status in the deployment preview screen
- 5763 - Fixed issue where Tentacle Upgrades fail on servers that do not have .Net Framework 4.7.2
- 5766 - Reduce the set of users editable with the UserEdit permission, such that this responsibility can be delegated to less privileged users
- 5767 - Prevents multiple spaces being flagged as the default space via the API
- 5768 - fix search boxes on Safari
New in Octopus Deploy 2019.7.7 (Aug 7, 2019)
- 4513 - Fixed exception when setting up a scheduled trigger for a specific day of the month
- 4714 - Reduced the CPU usage when deploying to many machine in parallel within the same deployment
- 4733 - Fixed preservation of JAR manifest info during deployment
- 4748 - Reduced the amount of data that is retrieved from the database throughout the application
- 4749 - UI adding an overflow menu option from various documents to the auditing screen
- 4752 - Fixed Azure Web App deployment failure when no Resource Group is provided
- 4753 - Run package scripts during Azure Resource Group deployment
- 4754 - Fixed a bug which limited trial licenses to a single worker and worker pool, when trials are meant to get unlimited workers and worker pools
- 4755 - Target retention during deployment no longer retrieves all the machines multiple times
- 4757 - Send additional licensing and usage details back to octopus.com in addition to existing telemetry
- 4758 - The proxy selection is no longer cleared when expanding the proxy section on the Tentacle details page
New in Octopus Deploy 2019.7.6 (Aug 5, 2019)
- 4513 - Fixed exception when setting up a scheduled trigger for a specific day of the month
- 4714 - Reduced the CPU usage when deploying to many machine in parallel within the same deployment
- 4733 - Fixed preservation of JAR manifest info during deployment
- 4748 - Reduced the amount of data that is retrieved from the database throughout the application
- 4749 - UI adding an overflow menu option from various documents to the auditing screen
- 4752 - Fixed Azure Web App deployment failure when no Resource Group is provided
- 4753 - Run package scripts during Azure Resource Group deployment
- 4754 - Fixed a bug which limited trial licenses to a single worker and worker pool, when trials are meant to get unlimited workers and worker pools
- 4755 - Target retention during deployment no longer retrieves all the machines multiple times
- 4757 - Send additional licensing and usage details back to octopus.com in addition to existing telemetry
- 4758 - The proxy selection is no longer cleared when expanding the proxy section on the Tentacle details page
New in Octopus Deploy 2019.7.5 (Jul 31, 2019)
- 4513 - Fixed exception when setting up a scheduled trigger for a specific day of the month
- 4714 - Reduced the CPU usage when deploying to many machine in parallel within the same deployment
- 4733 - Fixed preservation of JAR manifest info during deployment
- 4748 - Reduced the amount of data that is retrieved from the database throughout the application
- 4749 - UI adding an overflow menu option from various documents to the auditing screen
- 4752 - Fixed Azure Web App deployment failure when no Resource Group is provided
- 4753 - Run package scripts during Azure Resource Group deployment
- 4754 - Fixed a bug which limited trial licenses to a single worker and worker pool, when trials are meant to get unlimited workers and worker pools
- 4755 - Target retention during deployment no longer retrieves all the machines multiple times
- 4757 - Send additional licensing and usage details back to octopus.com in addition to existing telemetry
- 4758 - The proxy selection is no longer cleared when expanding the proxy section on the Tentacle details page
New in Octopus Deploy 2019.7.4 (Jul 26, 2019)
- Breaking changes:
- Most customers can upgrade directly to Octopus Server 2019.7, except those hosting Octopus Server on Windows Server 2008 SP2. This blog post has more details about who will be affected, and what you can do to upgrade.
- Don't worry, the Octopus Server installer will prevent you from accidentally upgrading if your host operating system will not be supported.
- Tools
- This release bundles the following command line tools and frameworks:
- AWS CLI - 1.16.178
- AWS PowerShell Cmdlets - 3.3.522
- AWS Azure CLI - 2.0.50
- AWS Powershell Cmdlets - 6.13.1
- Terraform CLI - 0.11.13
- Terraform AWS provider - 2.8.0
- Terraform Azure provider - 0.1.1
- Terraform AzureRM provider - 1.27.1
New in Octopus Deploy 2019.7.3 (Jul 24, 2019)
- Improved the variable preview screen to make it clearer how it works and ensured all variable types were displayed correctly
- Fixed disposing of leases for external workers with packages
- Added default roles for build servers
- Fixed license check code to deduplicate tentacles and ssh endpoints
- Create correct commit links in Octopus when using git@: URLs in the VCS root in package metadata
- Fix for project and project-group scoped permission UI issues
- Fix for DeploymentQueued event not being created with ARC
- Fix for Project Deploy Release page appears to hang with a large number of tenants
New in Octopus Deploy 2019.7.2 (Jul 18, 2019)
- Highlights:
- Octopus 2019.7 is a significant release even though it doesn't include any user-facing features. It includes technical changes to retarget Octopus Deploy to .NET Framework 4.7.2 and .NET Core 2.2 so Octopus can run natively on Linux and in Linux containers. This change is initially for Octopus Cloud and it will be extended to Octopus self-hosted in the future.
- Watch our blog for some great technical blog posts on what this involved and our lessons learned.
- Breaking changes:
- Most customers can upgrade directly to Octopus Server 2019.7, except those hosting Octopus Server on Windows Server 2008 SP2. This blog post has more details about who will be affected, and what you can do to upgrade.
- Don't worry, the Octopus Server installer will prevent you from accidentally upgrading if your host operating system will not be supported.
- Tools
- This release bundles the following command line tools and frameworks:
- AWS CLI - 1.16.178
- AWS PowerShell Cmdlets - 3.3.522
- AWS Azure CLI - 2.0.50
- AWS Powershell Cmdlets - 6.13.1
- Terraform CLI - 0.11.13
- Terraform AWS provider - 2.8.0
- Terraform Azure provider - 0.1.1
- Terraform AzureRM provider - 1.27.1
New in Octopus Deploy 2019.7.1 (Jul 11, 2019)
- Highlights:
- Octopus 2019.7 is a significant release even though it doesn't include any user-facing features. It includes technical changes to retarget Octopus Deploy to .NET Framework 4.7.2 and .NET Core 2.2 so Octopus can run natively on Linux and in Linux containers. This change is initially for Octopus Cloud and it will be extended to Octopus self-hosted in the future.
- Watch our blog for some great technical blog posts on what this involved and our lessons learned.
- Breaking changes:
- Most customers can upgrade directly to Octopus Server 2019.7, except those hosting Octopus Server on Windows Server 2008 SP2. This blog post has more details about who will be affected, and what you can do to upgrade.
- Don't worry, the Octopus Server installer will prevent you from accidentally upgrading if your host operating system will not be supported.
- Tools
- This release bundles the following command line tools and frameworks:
- AWS CLI - 1.16.178
- AWS PowerShell Cmdlets - 3.3.522
- AWS Azure CLI - 2.0.50
- AWS Powershell Cmdlets - 6.13.1
- Terraform CLI - 0.11.13
- Terraform AWS provider - 2.8.0
- Terraform Azure provider - 0.1.1
- Terraform AzureRM provider - 1.27.1
New in Octopus Deploy 2019.7.0 (Jul 8, 2019)
- 4802 - Added validation to the IIS configuration to ensure a hostname is entered when SNI is enabled
- 5503 - Show error message when kubectl returns error message
- 5504 - Fixed issue where historical feed data in database caused primary key violation when creating a new space
- 5602 - Fixed paging on the user activity feed
- 5642 - Clarified error message shown when a recursive variable definition is detected
- 5645 - Fix for team deletion issue with email steps
- 5646 - Removed ProjectGroupId from Deployment as this was not being kept in sync during Project moves (to other project groups), and causing octo.exe to fail to import
- 5653 - Accounts referenced by targets used in a deployment manifest are now shown in account usage
- 5654 - Made displaying usage more consistent and performant
- 5656 - Fixed dirty state checking on Deploy an ARM Template step
- 5657 - Fixed the logic in Azure Service Fabric deployments to determine if upgrades are available
- 5658 - Account usage for Token, Username/Password and SSH Key Pair account types now show all available usage types, not just usage in targets
- 5659 - Consolidated release usages and release snapshot usages for account types for clarity
- 5660 - Added the ability to delete a specific deployment
- 5664 - Fix an issue where it was not possible to select a certificate or account when using tenant variables
- 5666 - Deployments awaiting manual intervention will no longer block other deployments to the environment by default. This behavior can now be controlled by a switch on the manual intervention step
- 5669 - Fixed an issue where the UI would prevent you from selecting an environment to deploy to if your DeploymentCreate permissions were scoped to tenants
New in Octopus Deploy 2019.6.2 (Jul 4, 2019)
- Fix an issue where it was not possible to select a certificate or account when using tenant variables
New in Octopus Deploy 2019.6.1 (Jul 3, 2019)
- Fixed the logic in Azure Service Fabric deployments to determine if upgrades are available
New in Octopus Deploy 2019.5.12 (Jun 27, 2019)
- Breaking Changes:
- In order to support some customers who have Active Directory configurations where users share email addresses, we have had to remove the uniqueness restriction on user email.
- Health check properties of machine policies have changed to accommodate Linux Tentacle. TentacleEndpointHealthCheckPolicy has been renamed to PowerShellHealthCheckPolicy and SshEndpointHealthCheckPolicy has been renamed to BashHealthCheckPolicy. Any custom tools that create machine policies should use the new property names.
- The OnlyConnectivity option that was configured on SSH health check policies is now a policy-wide setting. This setting is commonly used for raw scripting on SSH targets. If you are using this setting a new machine policy will be created during the Octopus Server upgrade. Please refer to this GitHub issue for details, you may need to take action.
New in Octopus Deploy 2019.5.10 (Jun 13, 2019)
- Highlights:
- Script Module support for C# (and F# and Bash and Python)
- As quite a few people have requested, we've extended support for Script Modules to all supported languages. Now you can centrally manage common Bash, C#, F# and Python script functions, and even see where the Script Modules are being used.
- Breaking Changes:
- In order to support some customers who have Active Directory configurations where users share email addresses, we have had to remove the uniqueness restriction on user email.
- Health check properties of machine policies have changed to accommodate Linux Tentacle. TentacleEndpointHealthCheckPolicy has been renamed to PowerShellHealthCheckPolicy and SshEndpointHealthCheckPolicy has been renamed to BashHealthCheckPolicy. Any custom tools that create machine policies should use the new property names.
- The OnlyConnectivity option that was configured on SSH health check policies is now a policy-wide setting. This setting is commonly used for raw scripting on SSH targets. If you are using this setting a new machine policy will be created during the Octopus Server upgrade. Please refer to this GitHub issue for details, you may need to take action.
New in Octopus Deploy 2019.5.8 (Jun 10, 2019)
- Breaking Changes:
- In order to support some customers who have Active Directory configurations where users share email addresses, we have had to remove the uniqueness restriction on user email.
- Health check properties of machine policies have changed to accommodate Linux Tentacle. TentacleEndpointHealthCheckPolicy has been renamed to PowerShellHealthCheckPolicy and SshEndpointHealthCheckPolicy has been renamed to BashHealthCheckPolicy. Any custom tools that create machine policies should use the new property names.
- The OnlyConnectivity option that was configured on SSH health check policies is now a policy-wide setting. This setting is commonly used for raw scripting on SSH targets. If you are using this setting a new machine policy will be created during the Octopus Server upgrade. Please refer to this GitHub issue for details, you may need to take action.
New in Octopus Deploy 2019.5.7 (Jun 3, 2019)
- Breaking Changes:
- In order to support some customers who have Active Directory configurations where users share email addresses, we have had to remove the uniqueness restriction on user email.
- Health check properties of machine policies have changed to accommodate Linux Tentacle. TentacleEndpointHealthCheckPolicy has been renamed to PowerShellHealthCheckPolicy and SshEndpointHealthCheckPolicy has been renamed to BashHealthCheckPolicy. Any custom tools that create machine policies should use the new property names.
- The OnlyConnectivity option that was configured on SSH health check policies is now a policy-wide setting. This setting is commonly used for raw scripting on SSH targets. If you are using this setting a new machine policy will be created during the Octopus Server upgrade. Please refer to this GitHub issue for details, you may need to take action.
New in Octopus Deploy 2019.5.6 (May 28, 2019)
- In order to support some customers who have Active Directory configurations where users share email addresses, we have had to remove the uniqueness restriction on user email.
- Health check properties of machine policies have changed to accommodate Linux Tentacle. TentacleEndpointHealthCheckPolicy has been renamed to PowerShellHealthCheckPolicy and SshEndpointHealthCheckPolicy has been renamed to BashHealthCheckPolicy. Any custom tools that create machine policies should use the new property names.
- The OnlyConnectivity option that was configured on SSH health check policies is now a policy-wide setting. This setting is commonly used for raw scripting on SSH targets. If you are using this setting a new machine policy will be created during the Octopus Server upgrade. Please refer to this GitHub issue for details, you may need to take action.
New in Octopus Deploy 2019.5.5 (May 27, 2019)
- IIS bindings with upper case protocols are now show correctly in the IIS Manager
- The IIS binding list on the step edit now shows the value of the enabled flag
- Provide warning if email body fails to evaluate variables
- API keys are now immediately removed from the server cache when a user is disabled or deleted
- Offline drops now escape Windows and Linux special characters on all platforms
- UI fix for dialog overflow and scrolling issues
- Support escaped quotes in octostache variable filter parameters
- Now when a Tentacle is deleted from Octopus all connections to that machine will be closed
- Fix for the migration API pushing packages to a destination server
- Fixed bug that caused automatic release creation failures to return 400 and 500 on package push
- Fix for API key not being copied to the clipboard in the generate new API key dialog
- Fix an issue where autocomplete popover does not close after selecting an item
- Fix an issue where autocomplete and multi selects would not select an item when pressing enter after focusing an item in the list
- Fixed bug where emails fail due to certificate error when SSL/TLS is disabled in SMTP configuration
- Guest authentication provider now supports automatic logins
- Allow all feed types to select non acquisition option during script steps
New in Octopus Deploy 2019.5.4 (May 20, 2019)
- Highlights:
- Script Module support for C# (and F# and Bash and Python)
- As quite a few people have requested, we've extended support for Script Modules to all supported languages. Now you can centrally manage common Bash, C#, F# and Python script functions, and even see where the Script Modules are being used.
- Breaking Changes
- In order to support some customers who have Active Directory configurations where users share email addresses, we have had to remove the uniqueness restriction on user email.
- Health check properties of machine policies have changed to accommodate Linux Tentacle. TentacleEndpointHealthCheckPolicy has been renamed to PowerShellHealthCheckPolicy and SshEndpointHealthCheckPolicy has been renamed to BashHealthCheckPolicy. Any custom tools that create machine policies should use the new property names.
- The OnlyConnectivity option that was configured on SSH health check policies is now a policy-wide setting. This setting is commonly used for raw scripting on SSH targets. If you are using this setting a new machine policy will be created during the Octopus Server upgrade. Please refer to this GitHub issue for details, you may need to take action.
New in Octopus Deploy 2019.5.2 (May 15, 2019)
- Fixed missing navigation menus when creating a new Deployment Target or Worker
- Rolled back the logging changes in 2019.4.3 that are likely causing deployments, tasks and server shutdown to hang
New in Octopus Deploy 2019.5.1 (May 14, 2019)
- Fixed an issue where multi-select and auto completion fields would render popovers partially offscreen when close to the edge
- Deployment retention no longer requires exclusive access to the tentacle (this bug was introduced in 2019.4.5)
- Fixed "Sequence contains no elements" error when viewing releases that don't match the current project release versioning settings
- Fix terraform steps unable to asume AWS service roles
- Only load script module usage on demand
- Include monthly active user count in usage statistics
New in Octopus Deploy 2019.5.0 (May 9, 2019)
- Halved the performance impact of the project dashboard for instances with many deployments
New in Octopus Deploy 2019.4.7 (May 2, 2019)
- 5482 - Fixed a bug preventing deployment target triggers from working when any project has more than one deployment target trigger defined
- 5511 - Releases and deployments now have access to a distinct list of work items, as well as the original hierarchical data structures
- 5515 - Fix up some UserRoles that were not set up correctly in 2019.1 and could not be saved
- 5518 - Added support for Azure accounts in Terraform steps
- 5521 - Work items with an alphanumeric project identifier in issue ID can now be parsed
- 5528 - Fixed an access control bug where project scoping was not being applied for VariableViewUnscoped and VariableEditUnscoped permissions (CVE-2019-11632)
- 5532 - Fixed single quotes arguments passed to Terraform
New in Octopus Deploy 2019.4.6 (May 1, 2019)
- 5511 - Releases and deployments now have access to a distinct list of work items, as well as the original hierarchical data structures
- 5515 - Fix up some UserRoles that were not set up correctly in 2019.1 and could not be saved
- 5518 - Added support for Azure accounts in Terraform steps
- 5521 - Work items with an alphanumeric project identifier in issue ID can now be parsed
- 5528 - Fixed an access control bug where project scoping was not being applied for VariableViewUnscoped and VariableEditUnscoped permissions
New in Octopus Deploy 2019.4.5 (Apr 30, 2019)
- 4567 - Automatic Release Creation now creates releases after a step rename
- 5394 - K8S deploy step supports external secrets to be used for ingress TLS
- 5458 - Improved the speed of the automatic release creation after a package upload
- 5488 - Release note accumulation honors the Discrete Channel release setting on the project
- 5494 - Raw commit details as an Octopus variable for release notes
- 5495 - Work item release notes from GitHub / Jira
- 5498 - Improved error message when attempting to acquire helm charts but helm is missing
- 5501 - Fixed an issue preventing the cloning of a step into the current project
- 5506 - Fixed issue with creating releases when multiple packages exist on the versioning step
New in Octopus Deploy 2019.4.4 (Apr 18, 2019)
- 5483 - Changed all popover components to use the new MUI component which is reported to fix the positioning delay
- 5487 - Return a more helpful error message on the release page if a package / version combination cannot be found in the built-in repository
- 5490 - Make package published date format in UI consistent and include tooltip with timezone info
- 5491 - Fixed exception on Project settings page if auto release creation is enabled and a package step is configured to use a versioning template instead of package step
- 5493 - BugFix: DockerHub feeds fail to authenticate during acquisition
New in Octopus Deploy 2019.4.3 (Apr 17, 2019)
- Fixed an issue where redeploying a SF application of the same app/type/version would fail regardless of override behavior
- UI adding categories to make step template selection more intuitive
- Related to 5468, Azure Resource Group template parser updated to handle non-string types
- Added warning when user is creating/editing an Email Step or a Subscription and SMTP hasn't been configured yet
- Prevented disabled steps from being used for release versioning and automatic release creation
- Updated health check messages to better reflect plural and singular
- Octopus Server can no longer be started against a database with a newer schema
- Azure Resource Group step fixed to handle the templates correctly when bool and integer types are used
- Corrected read-only summary label for container volume mount in k8s deploy containers step
- Ensure only distinct package versions are included when running package metadata retention
- Button styling has been updated to improve accessibility
- Resolved spurious validation failure related to secret volume on deploy k8s containers step
- Add certificate variable validation for HTTPS binding on the Deploy to IIS step
- Bug: Unable to pull docker image on some ssh targets
- Kubernetes step resource validation is over-eager and not allowing variables
New in Octopus Deploy 2019.2.8 (Apr 1, 2019)
- Fix for editing a release with a package that doesn't match channel rules
- Octopus Cloud Octopus Manager team doesn't have permissions to export users permission structure
- Fix for broken Project settings page if project was cloned from another project that's not available due to permission/deletion/migration
- Made the getting started guidance available to hosted customers and space managers
- Adding null checking around database upgrade script
- Docker acquisition script moved from Server to Calamari
New in Octopus Deploy 2019.2.7 (Mar 28, 2019)
- Added validation to ensure machine policy timeouts
- Added ability to supply additional arguments in Upgrade Helm Chart step
- ags entered but not added are now auto-added when saving a tenant tag set
- Added the ability to filter by project and environment on the tenants overview
- Removed unnecessary Tenant Preview buton on Tenant Overview page
- Fix issue where side bar navigation was missing on the Create Subscription page
- Improved the processing speed of the auto-deploy triggers background process
New in Octopus Deploy 2019.2.6 (Mar 21, 2019)
- Fixed crash on node --drain command
- Fixed issue with subscription webhooks using wrong http header type
- Fixed startup issue for a subset of customers by a data consistency script in 2019.2.5
New in Octopus Deploy 2019.2.5 (Mar 20, 2019)
- Fixed issue where expired cron expressions for scheduled deployments were throwing exceptions
- Renamed 'Run a Helm Update' step to 'Upgrade Helm Chart'
- Fixed issue where worker health checks run for deployment targets instead
- Cleaned up callouts in Space Edit screen to improve UX
- Fixes scoping for projects when a different project group is scoped on the user role
- Environment section text only shows up if there are environments created on that Octopus instance
- Fixes project scoping for user roles when scoped to the projects' group
- Fixes dashboard bug when accessing projects in a group the user doesn't have access to
- Added target name to Calamari/Tentacle upgrade task name
- Fix for permission errors when trying to view another users permissions if you do not have access in another space
- Improved cross document links for ScopedUserRoles to Teams and UserRoles in Audit
New in Octopus Deploy 2019.2.4 (Mar 18, 2019)
- Fixed an issue where guided failure does not fail a deployment on the first attempt
- Re-wording message that shows up when a task is suspended because the space queue was stopped
- Added client side input validation for retry attempts in external feeds
- Filter in Teams page should only render after all teams have loaded
- UsernamePassword authentication now accepts email address
- Fixed feed refresh button crashes in several built-in steps
- Sorted the output of show-configuration and the root api responder to make it easier to find things
- fixes an exception during some upgrades due to incorrect assumptions in the UserRole data model
- Migrator.exe no longer fails when importing snapshot VariableSet referencing deleted certificate
- Migrator now remaps deployment action worker pool ID when importing
New in Octopus Deploy 2019.2.3 (Mar 13, 2019)
- Highlights:
- This fast lane release is our second minor release after the 2018.10 LTS release with long term support. If you're not sure what this means to you, please read the announcement to help decide which lane works best for you.
- User Invitations into Space Teams:
- We have added the ability to invite new users into Teams that are owned by Spaces. Previously, new Users could only be invited into System-level Teams, but now Spaces and Space Managers can be self sufficient by inviting new Users without needing to ask a more privileged user to first invite the user into a System team.
- Improved Date Display:
- We've done some renovations around how we handle and display dates. Now, we display dates in your local timezone where possible, and if that isn't possible, we include the timezone, so it's much easier to tell when something happened if you're in a distributed team or in a different timezone to your Octopus Server. Unfortunately, this has meant we've had to make some breaking changes, but we believe the impact will be low.
- Breaking Changes:
- The LastSeen property on octopusservernodes/ping now returns an ISO8601 date instead of a formatted string
- The human-readable Completed date on a Task is now formatted with a timezone
- The human-readable Published date on a Package is now formatted with a timezone
- The Rank, LastSeen and IsOffline properties have been removed from the /api/OctopusServerNodes/{id} endpoint, and are now available from a new endpoint /api/OctopusServerNodes/summary
- The EffectiveExpiryDate on the /api/licenses/licenses-current-status endpoint is now formatted with a Date (yyyy-MM-dd) rather than DateTimeOffset data type.
- The third party libraries we use to read certificates have been upgraded to newer versions which include tighter certificate verification. This may reject incorrectly formatted certificates.
- Changes:
- 4243 - Cloning a project now copies all project settings correctly
- 4349 - Reduce confusion around the select and deselect options for steps excluded from a deployment
- 4685 - Fixed issue where the "new server version" notification was not appearing
- 5322 - Fixed issue where Check Tentacle Health summary was not showing details when all targets ended up as HasWarnings or Unhealthy
- 5357 - Modified the tooltip text for Space and System team chips to make it easier to understand
- 5363 - Re-indexing the in-built package repository can now run on any node in a multi-node cluster
- 5364 - Fixed an issue where users without TeamView could not view the configuration for a Space
- 5366 - Allow deployment of raw YAML to K8S Cluster
- 5367 - Corrected an issue where the certificate archive would show incorrect results when loading the second and subsequent pages
- 5368 - Updated the Space Switcher to highlight the active Space
- 5369 - Added a link to the Space Switcher to allow easy space creation
- 5371 - Fixed a bug where you could not fetch artifacts for releases with a large number of deployments
- 5374 - Fixed an issue where the AWS Account variable selector wasn't being displayed
- 5377 - Allow collapsing environment variables for project variable templates when browsing project variables on a tenant
- 5378 - Task Queue startup code handles now exceptions correctly
New in Octopus Deploy 2019.2.1 (Mar 1, 2019)
- Add validation for drop down options for variable templates of type "select"
- 5303 - 2100 SQL parameter limit hit when updating usages of step templates fixed
- 5325 - Fixed the api/reporting/deployments/xml endpoint, a bug introduced in 2019.1.0
- 5338 - Corrupt builtinrepositoryconfigurations-single configuration json column fixed
- 5343 - Delete project error message does now display the teams blocking the deletion
- 5346 - Automatic lifecycle promotion after automatic release creation works regardless of the permissions of the user that pushed the package, fixing an issue introduced in 2019.1.0
- 5349 - Expose ephemeral storage requests and limits in K8S
- 5351 - Using Tentacle Manager to configure a polling Tentacle does not authenticate with username/password has been fixed
- 5352 - Fixed an issue where nodes with very long names would show StringTooLongException warnings in the log and were unable to elect a Leader node
- 5354 - Improve user experience adding a worker when at license limit
New in Octopus Deploy 2019.2.0 (Feb 28, 2019)
- Fix for scheduled triggers editing UI now using the previously selected non-default channel to show correct environment options
- Fix for missing optional LifeCycle phases in new release triggers
- Improved error messages on when supplying space names to commands and user lacks permission
- EffectiveExpiryDate value returned in Licence api should return just date and not datetimeoffset
- Script Console will load now Azure dependecies when used to run a script on an Azure target
- Database upgrade script failed with a InvalidOperationException
- Upgrade Bouncy Castle certificate library to latest version with up-to-date validation logic
- Allow file substitution wanrnings to be supressed in Terraform deployment
- Breaking Change Split the OctopusServerNodes table, and moved heartbeat/cluster information to a new endpoint
New in Octopus Deploy 2019.1.11 (Feb 26, 2019)
- Issues and Bugfixes:
- Breaking change Increased the speed of artifact retrieval and cascade deletion when there are many artifacts
- Added Tentacle support for spaces. Breaking change Deregister commands no longer remove trust for the server
- Tentacle Manager no longer overwrites Tentacle instances with the same name.
- Tentacle Manager now properly handles selecting and creating of Roles that include spaces
New in Octopus Deploy 2019.1.10 (Feb 25, 2019)
- Highlights:
- Spaces:
- To bring in the new year, we are shipping our latest feature. Spaces is a comprehensive set of user interface, API and permission system changes designed to make it easier to configure deployments in busy organizations.
- Teams & Permissions:
- We have re-designed the way permissions are assigned to Teams, making it easier than ever to configure and manage permissions for your users As part of this we have rewritten much of the code that enforces these permissions so that we can make sure Octopus keeps your data safe There are a few breaking changes involved here, so customers with complex permission configurations may want to pay careful attention to the release notes
- Tentacle Manager UI redesign:
- We have re-designed the UI of the Tentacle Manager to follow the design principles of Material Design
- Issues and Bugfixes:
- Breaking change Increased the speed of artifact retrieval and cascade deletion when there are many artifacts
- Added Tentacle support for spaces Breaking change Deregister commands no longer remove trust for the server
- Tentacle Manager no longer overwrites Tentacle instances with the same name
- Tentacle Manager now properly handles selecting and creating of Roles that include spaces
New in Octopus Deploy 2019.1.9 (Feb 20, 2019)
- Certificate filter doesn't work when there is more than 1 page or results
- Run Condition and Start Trigger sections no longer disappear when a validation error happens when saving a step
- Fix for audit screen and audit shortcuts reporting incorrect lack of permission for users who have EventView scoped
- Expose the K8S Pod termination grace period field
- Allow K8S TLS certificate to be empty
- UI fixing route issues that were causing pages to re-render when filtering
- Fix for server startup error (Error converting value “TaskViewLog”)
- Can't save previously created K8S container definitions
New in Octopus Deploy 2019.1.8 (Feb 19, 2019)
- Fixed the variable preview grid to expand columns to all available space
- Prevent SQL timeouts for auto-deploy triggers
- Fixed "Unbound variable" error when using set_octopusvariable with set -euo pipefail
- Rename "machine name" field on deployment targets to "display name"
- Show type (Polling Tentacle/Listening Tentacle/Cloud Region/etc) when viewing a deployment target
- Removed extraneous slashes in placeholder text for offline drop targets
- Outdated OctopusClient warnings now include user and agent type
New in Octopus Deploy 2019.1.7 (Feb 18, 2019)
- Fix for Tenant scoped users who were incorrectly blocked from exporting certificates
- "Deploy a Release" steps now collect output variables from failed child deployments
- Fixed a bug where Project Viewers could not assign and submit interruptions
- Fixed error "This SqlTransaction has completed; it is no longer usable"
- Added warning logs for situations where an IIS web site deployment will fail to start the web site
- The built-in repository settings are now retained correctly when upgrading from versions prior to 2019.1.x
- Fixed a bug where Packages could be cleaned up by retention policies while still in use by Releases
- No longer leaving orphaned DeploymentActionId when deleting a step as part of deleting a channel
- Resolved performance problem writing to log files introduced in 2019.1.2
- Breaking change Removed the TaskViewLog permission. Any user that has been granted access to a Task through the TaskView permission can also view that Task's logs
New in Octopus Deploy 2019.1.6 (Feb 13, 2019)
- Breaking change:
- Increased the speed of artifact retrieval and cascade deletion when there are many artifacts
- Added Tentacle support for spaces. Breaking change Deregister commands no longer remove trust for the server
New in Octopus Deploy 2019.1.5 (Feb 7, 2019)
- New-OctopusAzureWebAppTarget command slot name parameter is now honoured
New in Octopus Deploy 2019.1.4 (Feb 5, 2019)
- Changes:
- 5266 - Fixed error when health checking Tenant scoped targets in 2019.1.0 and later
- 5268 - Fixed UI bug with exclude unhealthy targets setting
New in Octopus Deploy 2019.1.3 (Feb 4, 2019)
- Issues and Bugfixes:
- 5226 - Breaking change Increased the speed of artifact retrieval and cascade deletion when there are many artifacts
- 5239 - Added Tentacle support for spaces. Breaking change Deregister commands no longer remove trust for the server
New in Octopus Deploy 2019.1.2 (Jan 31, 2019)
- Changes:
- New-OctopusAzureWebAppTarget command slot name parameter is now honoured
New in Octopus Deploy 2019.1.1 (Jan 30, 2019)
- Issues and Bugfixes:
- Breaking change Increased the speed of artifact retrieval and cascade deletion when there are many artifacts
- Added Tentacle support for spaces. Breaking change Deregister commands no longer remove trust for the server
- Upgrading:
- As with any upgrade for self hosted customers, we recommend taking a database backup first. Given there are some breaking changes to how the built in feed is structured on disk, we also recommend taking a filesystem backup too.
- In order to make use of the new Spaces feature, Tentacles should be updated to version 4.0.0, Octopus.Client dependencies should be updated to 5.0.0 and any other integrations should be updated to their latest version.
- Breaking Changes
- Before upgrading to this release, there are some breaking changes in behaviour that you need to be aware of.
New in Octopus Deploy 2019.1.0 (Jan 29, 2019)
- 5226 - Breaking change Increased the speed of artifact retrieval and cascade deletion when there are many artifacts
- 5239 - Added Tentacle support for spaces. Breaking change Deregister commands no longer remove trust for the server
New in Octopus Deploy 2018.12.1 (Jan 24, 2019)
- Polling Tentacle timeout can now be configured via the machine policy, replacing the Octopus.Server.exe.config settings. If you are using those settings, open each machine policy, check the settings and save the policy.
- Added support for touch screens when reordering lists (e.g. when re-ordering steps).
- Attempt to cancel any running tasks when shutting down the Octopus service
- SSH and Tentacle connection timeouts and limits can now be configured via the machine policy.
- External feed URLs are now trimmed to prevent validation errors.
- Squashed null reference error in Deploy Kubernetes Containers step when secret has no data.
- Added support for AWS S3 and CloudFormation steps to run on ssh Linux targets
- Fix for incorrect permission warning on Project overview screen if user only had ProjectView scoped on group dimension.
New in Octopus Deploy 2018.12.0 (Jan 21, 2019)
- 5045 - Reduced the key size of the index IXServerTask_Common so it no longer exceeds the maximum key size
- 5205 - Upgrade to latest version of Azure libraries in Octopus Server means breaking some management certificate support
- 5216 - Turn off context autosave in AzureRM powershell scripts
- 5219 - Allow step templates to be created from a step
- 5222 - Server can now download all NuGet packages created with the latest version of NuGet
- 5227 - Bugfix - Referencing PackageVersion variable from another step is not evaluating correctly
New in Octopus Deploy 2018.11.3 (Jan 17, 2019)
- 5210 - Resolved JSON encoding issue with k8s config maps and secrets
- 5215 - Improved handling of transient I/O errors when writing server logs
- 5217 - Steps can now be cloned to a different project
- 5218 - Fix for resource searching that incorrectly escaped left square brace, resulting in incomplete query results
- 5221 - Downgraded Octopus.Dependencies.AzureCmdlets to v6.8.1
New in Octopus Deploy 2018.11.2 (Jan 14, 2019)
- 4891 - Fix an issue meaning Infrastructure tab didn't load correctly for some permission scoping combinations
- 4929 - TLS certificates can now be configured on Kubernetes Ingress
- 5118 - Resolved issue preventing Kubernetes custom resource YAML containing variable expression from being saved
- 5146 - Bugfix: Support additional values file sourced from helm chart package
- 5177 - Fix and issue where deployments to cloud services would fail to authenticate after migrating from old versions of octopus
- 5179 - Squashed bug resulting from removing package references from cloned steps
- 5199 - Made the capitalization of headings on the project settings page consistent
- 5200 - Fixed an issue on slow connections where attempting to edit a newly cloned step caused a page refresh rather than navigating to the edit step page
- 5201 - Made the Machine Policy field on a new deployment target always visible to reduce confusion
- 5202 - Kubernetes Service fields now displayed before Ingress fields on Deploy Kubernetes Containers step
- 5203 - Ensure K8S lifecycle hooks encode each command line as a string
- 5209 - Fixed an issue preventing new steps from being added and or modified when a step uses an account variable selector such as AWS and Terraform steps
- 5212 - Fix grammar in the summary text for a child step when used in a rolling deployment
New in Octopus Deploy 2018.11.1 (Jan 4, 2019)
- This release is our first fast lane release after the 2018.10 LTS release with long term support. If you're not sure what this means to you, please read the announcement to help decide which lane works best for you.
- Even though it's been released at the start of January 2019, its a wrap up of all the work we did at the end of 2018. It mainly contains UI updates, but also a bunch of important fixes.
- Cloud Dependency Updates:
- All the Cloud dependencies that ship with Octopus have had an update:
- Azure PowerShell modules upgraded to 6.11.0.
- Azure CLI upgraded to 2.0.50
- AWS PowerShell modules upgraded to 3.3.390.0
- AWS CLI upgraded to 1.16.52
- Terraform CLI upgraded to 0.11.10
- Terraform AzureRm plugin upgraded to 1.19.0
- Terraform AWS plugin upgraded to 1.51.0
- Terraform Azure plugin upgraded to 0.1.1
- Database performance updates:
- At the end of the installation process, Octopus will rebuild or reorganize database indexes that are fragmented to ensure the database performs at its best. This may take some time, depending on the size of your database.
New in Octopus Deploy 2018.11.0 (Jan 3, 2019)
- 5126 - Fix for error saying unable to delete a step template that's in use
New in Octopus Deploy 2018.10.0 (Dec 20, 2018)
- Highlights:
- Kubernetes:
- 2018.9 removes the alpha feature-flag from the Kubernetes support in Octopus!
- The following pieces are now fully-supported members of the Octopus family:
- Kubernetes targets
- Deploy Containers to Kubernetes step
- Helm Chart feeds and Help Upgrade step
- Run kubectl script step
- Offline Drop Artifacts:
- Offline Package Drop targets can now be configured to persist the bundle as an Octopus Artifact.
- Offline Package Drop targets could previously only persist the bundle to a file-system directory, which wasn't suitable for Octopus Cloud instances. Artifacts are a perfect fit for this; the deployment bundle is persisted a zip file stored against the deployment in Octopus.
- Cloud Dependency Updates
- All the Cloud dependencies that ship with Octopus have had an update in 2018.9:
- Azure PowerShell modules upgraded from 5.7.0 to 6.8.1. This update fixes some known issues with the 5.7.0 release of Azure PowerShell.
- Azure CLI upgraded from 2.0.42 to 2.0.45
- AWS PowerShell modules upgraded from 3.3.225.1 to 3.3.343.0
- AWS CLI upgraded from 1.16.6 to 1.16.15
- Terraform CLI upgraded from 0.11.5 to `0.11.81
- Terraform AzureRm plugin version 1.16.0
- Terraform AWS plugin version 1.39.0
- Highlights:
- This is the first release of Octopus Server with six months long-term support. It includes everything up to and including Octopus Server 2018.9.
New in Octopus Deploy 2018.9.17 (Dec 18, 2018)
- 5133 - UI Simplifying the Getting Started / Onboarding guides
- 5144 - Resolved issue with migrator partial-export command exceeding 2100 SQL parameters
- 5145 - Added the ability to choose how inlined scripts in deployment processes are exported by Octopus.Migrator.exe including CopyInlineScripts (current behaviour), ExtractInlineScripts, and LeaveInline - learn more
- 5147 - Fixed issue where editing an offline drop removes the encryption password
- 5154 - Updated task logs for subscription processing and auto-deploy to use nesting and add links to the related project / trigger / release
- 5163 - Fix error on project process screen when user does not have LifecyleView permissions
- 5164 - Show empty state info boxes when connecting a tenant to a project or tag set and none exist
- 5165 - Made the Azure account type expander look and work in the same way as other expanders
- 5166 - Improved layout of Upload Package dialog
- 5170 - OctopusClient updated to include information in it's calls that allow filtering in the audit log
- 5171 - Octopus Cloud instances can now be licensed by deployment target just like self-hosted Octopus Server licenses
- 5167 - Gracefully stop Octopus Server if running in terminal and process terminated
New in Octopus Deploy 2018.9.16 (Dec 12, 2018)
- 5143 - Added the Strict-Transport-Security HTTP header to the page shown when Octopus Tentacle is accessed from a Web Browser
- 5148 - migrator.exe import will no longer fail with a unique constraint violation on name when it mistakenly tried to insert a new MachinePolicy or Subscription or Account or Feed with the same name, now it will correctly overwrite the existing document
- 5149 - Clicking on a step in the task summary now navigates you to the correct element in the task log
- 5152 - Added a new update-trust command for Tentacle, this command allows you to update a server thumbprint, without having to remove and then add a new thumbprint which doesn't work for polling Tentacles
- 5153 - Fixed a regression in Octopus.Migrator.exe partial-export introduced in 2018.9.13 which would incorrectly fail to validate the arguments related to exporting releases
- 5155 - Support for Kubernetes Container Lifecycle Events
New in Octopus Deploy 2018.9.15 (Dec 6, 2018)
- Resolved script step package references being incorrectly deleted by retention policy
- Create release page shows project ID rather than name for Deploy Release steps
- Extend brute force login protection to cover API keys
New in Octopus Deploy 2018.9.14 (Dec 4, 2018)
- We fixed how the database collation is calculated while upgrading Octopus Server, which was previously reported to fail under certain circumstances using Azure SQL Database
New in Octopus Deploy 2018.9.13 (Dec 3, 2018)
- 4156 - Fixed highlighting of the selected element in drop downs that allowed filtering (e.g. the Add Member to Team dialog)
- 5116 - Fixed validation around Java package steps that could be saved without selecting a package
- 5117 - migrator.exe now correctly exports all dependencies used by a project and any of its releases, where beforehand any dependencies removed from the project would not be exported subsequently causing the import to fail
- 5119 - migrator.exe now correctly exports all versions of any action templates used by a project and any of its releases, where beforehand only the specific versions in use were exported causing potential errors after import
- 5122 - Tweaked shortcut menu for package feeds to make common actions more discoverable
- 5125 - Long project names will now wrap in the project quick search dropdown
- 5127 - migrator.exe partial-export now supports exporting multiple projects by specifying the --project="MyProjectName argument multiple times, or by project groups using the new --projectGroup="MyProjectGroup1" argument or in any combination of the two
- 5132 - The count of releases and deployments sent to octopus.com as telemetry has been corrected to use the DeploymentHistory table
New in Octopus Deploy 2018.9.12 (Nov 26, 2018)
- 4411 - Fix text color of Tenant Tag tooltip so description is visible
- 4672 - Fix an issue where enter causes the variable editor to save when adding a new variable
- 4947 - Fix an issue where bottom action buttons for lists would be duplicated or constantly appear and disappear
- 5060 - Changing a projects lifecycle now correctly re-renders the phases and environments
- 5091 - Fix F# compatibility with mono version 5.16
- 5103 - Improved summary text for subscription filters
- 5104 - Added Octopus.Machine.Hostname to automatic variable completion list
- 5105 - Added help text for User Profile -> Api Keys
- 5106 - Ensure deployment target icons are shown at smaller screen resolutions
- 5107 - The icon on disabled chips is now grayed out in the same way as the text
- 5108 - Infrastructure page now correctly shows worker pools and workers tabs when user has permission
- 5109 - Fixed missing variable icon overlapping the project name on the tenant variable screen
- 5111 - Long project names no longer overlap the selected environments on the tenant variable screen
- 5112 - Fix an issue where default ports were not provided for ssh and listening tentacles during creation
- 5113 - Helm deployments fail with target using cloud account
- 5114 - API key creation now creates an audit log, regardless of who you create the key for
New in Octopus Deploy 2018.9.11 (Nov 21, 2018)
- 5095 - Resolved issue where project versioning-strategy was being cleared when upgrading from Octopus 2018.8.x to 2018.9
- 5097 - Fix a bug where VariableSet cannot be retrieved through Deployment.ManifestVariableSetId when there is variable scoped to channel
- 5098 - Fix for Service Fabric targets API failing to retrieve store location/name override
- 5100 - migrator.exe now correctly exports library variable sets used by a project and any of its releases, where beforehand any library variable sets removed from the project would not be exported subsequently causing the import to fail
- 5101 - Migrator now correctly remaps tenant tag references when the tag-set exists on the destination
New in Octopus Deploy 2018.9.10 (Nov 19, 2018)
- 4817 - Subscription emails now display events in ascending order by the time the event occurred
- 4846 - Reduced queue time in some instances for tasks resuming from manual intervention
- 4941 - Guided failure for required steps no longer presents the option to skip the step or exclude a machine from the step
- 5077 - Exposed image pull policy settings for K8S containers
- 5078 - Standalone ingress rules now accept variable host names
- 5080 - Fix a bug where wrong permission is used when try changing lifecycle for a project
- 5082 - migrator.exe now correctly handles importing accounts restricted to environments or tenants where some of those environments or tenants do not exist in the target
- 5084 - migrator.exe now correctly handles importing project triggers which filter events for certain environments where some of those environments do not exist in the target
- 5085 - migrator.exe now correctly handles importing deployment targets belonging to certain environments or tenants where some of those environments or tenants do not exist in the target
- 5086 - migrator.exe now correctly handles importing account variables, where before the account variable was not remapped correctly from source to target
- 5090 - Fixed issue with subscription webhooks using wrong http header type
- 5093 - Octopus Cloud licenses are excluded from compliance pre-condition checks when upgrading the database or applying a new license
- 5094 - If a database upgrade script is running for a long time without showing any progress messages, we now log a "still working" message every minute until the script completes
New in Octopus Deploy 2018.9.9 (Nov 14, 2018)
- 5021 - Kubernetes target certificates now reported in certificate usage
- 5052 - User accounts for Octopus Support Staff can now be added to an Octopus Server regardless of license limits
- 5054 - Resolved issue introduced in 2018.9.0 where updating step template usages was causing exception when viewing project
- 5079 - Resolved logging format exception when executing database upgrade script
- 5080 - Fix a bug where wrong permission is used when try changing lifecycle for a project
- 5087 - migrator.exe now correctly handles importing variable values scoped to tenants via tenant tags
New in Octopus Deploy 2018.9.8 (Nov 14, 2018)
- 4920 - Fixed issue with packages not being listed when using TeamCity 2018.1.x legacy NuGet feeds
- 5066 - Fixed an issue with the S3 step where invalid bucket keys were being used when using multiple file selections
- 5072 - migrator.exe now gracefully handles the importing tenant + project + environment connections when the project or environment does not exist in the target
- 5081 - migrator.exe now correctly handles importing subscriptions which are filtered by tenant tags
New in Octopus Deploy 2018.9.7 (Nov 12, 2018)
- 5020 - fixed some rare cases of certificate read failures after upgrading to 2018.8.7
- 5032 - Fix a bug where IE 11 does not render artifacts URL correctly
- 5056 - UI legacy toggle on Azure steps to access older template functionality
- 5058 - Fixed issue with Deploy Release step not always failing when the release fails
- 5061 - Enable full screen mode for the variable editor dialog
- 5065 - migrator.exe now correctly handles the default worker pool selected by certain deployment targets, where the selection would have been dropped during the import process
- 5068 - Folders with Junctions can now be deleted again
- 5069 - migrator.exe now correctly handles the worker pool selected for actions in a deployment process, where the selection would have been dropped during the import process
- 5070 - kubectl config file is now displayed in the verbose logs
- 5071 - The package cache and working directory can now be configured
- 5076 - Fixed up integration with http://Quay.io|Quay.io docker repo
New in Octopus Deploy 2018.9.6 (Nov 7, 2018)
- 5013 - Significant decrease in the amount of data persisted with deployments, especially when using a large number of certificates
- 5059 - Increased the database connection timeout and transaction commit/rollback timeout for database upgrades to 3 minutes, just like it was before 2018.9.0
- 5063 - Fixed validation for kubernetes volumes that referenced external configmaps or secrets
New in Octopus Deploy 2018.9.5 (Nov 6, 2018)
- 5024 - Database upgrade scripts now consistently roll back to the last known good state regardless of which specific kind of upgrade script fails
- 5038 - Database upgrade scripts now use an infinite SQL command timeout consistently - we really want the upgrade to complete even if a particular command takes a longer time than expected
- 5055 - K8S standalone Secret and ConfigMap steps deploy as expected now
New in Octopus Deploy 2018.9.4 (Nov 5, 2018)
- Deployments are now removed from the dashboard again when they or their release is deleted
- The dashboard now correctly shows the updated version number of a release again when it is changed
- Resolved issue introduced in 2018.9.0 where updating step template usages was causing exception when viewing project
New in Octopus Deploy 2018.9.3 (Nov 2, 2018)
- 4969 - Dashboard can be cached longer than 2 seconds
- 5037 - Step template usages are now sorted alphabetically
- 5043 - Show more informative summary text for an Active Directory identity when the specified account has no email address set
- 5048 - Added pod and node affinity settings to the k8s container deployment step
- 5050 - Only show the channel chip on the task summary page if the project has more than one channel
- 5051 - Migrator now remaps Deploy Release step projects
New in Octopus Deploy 2018.9.1 (Oct 30, 2018)
- 5023 - User accounts from certain email domains can be excluded from billing at the discretion of the service provider
- 5025 - Improvements to concurrency protection on variable sets
- 5026 - Call to api/projects?name=[test] fails because of the special chars
- 5027 - Sensitive Template Project variables on a Tenant will now show "value required" warning when they are empty
- 5028 - Now preventing the SQL Database connection string from containing both Integrated Security and SQL Authentication with User ID or Password to prevent confusion
- 5035 - Bundled Tentacle 3.23.2 which fixes a bug in the Tentacle Manager that was preventing showing instances
- 5036 - 2018.9.0 introduced an issue where upgrading was converting offline-package-drop targets to use artifact mode
New in Octopus Deploy 2018.9.0 (Oct 25, 2018)
- The built-in worker command-line interface handles machineuser and domainuser formats more gracefully
- Updated the Azure PS bundle to 6.8.1 and the Azure CLI to 2.0.45
- Offline-Drop targets can now store the bundle as an Octopus Artifact
- The interruption and artifact APIs now have an ETag, lessening the load on the database
- In 2018.8 it was possible to corrupt auto-release-creation and channel rules by renaming package references on script steps
- Allow script step package references to be used for project versioning
- Updated the AWS PS bundle to 3.3.343.0 and the AWS CLI to 1.16.15
- Updated Terraform to 0.11.8, the AzureRM plugin to 1.16.0, and the AWS plugin to 1.39.0
- Fix for error reporting missing variable set snapshot NullReferenceException during deployments and variable set editing
- Built-In Worker settings are now displayed on the Configuration->Nodes->Server Settings page
- Exposed annotations for the pod resources created by the Kubernetes deployment resource
- The path command-line interface now validates paths and tries to create the path if it does not exist
- The Octopus.Server.exe database --upgrade --skipLicenseCheck command actually skips the license check properly now
- Fixed a bug with auto login when only the Active Directory provider was enabled
- K8S service annotations now exposed like Ingress and Deployment annotations
New in Octopus Deploy 2018.8.10 (Oct 25, 2018)
- 4982 - Search field on “Include a Script Module” is now case-insensitive
- 4983 - K8S Secret and ConfigMap resources no longer deployed when the feature is disabled
- 4984 - K8S suggestion lists are now case insensitive
- 4985 - K8S Ingress host allowed variable substitution
- 4986 - Exposed annotations on the K8S deployment resource
- 4987 - Added extra help to the OpenID Connect authentication providers
- 4988 - BugFix: Acquisition of Helm charts fails when the username is empty
- 4992 - Fix for migrator importing proxies
New in Octopus Deploy 2018.8.12 (Oct 22, 2018)
- Fixed an issue with NuGet feeds when migrating from 2.6 to versions later than 2018.8.0
- Machines that trigger an auto deploy event while a tenanted deployment is in progress will now receive that deployment when it finishes
- Fixed a rare crash that occurred when attempting to write log files
- Add backwards support to deploy Service Fabric applications using CloudRegion targets
- Terraform Apply step now supports multi-line output variables
- Added a null check for a missing ActionName in GetPackageVersionsUsedInReleases
- Bugfix: Kubernetes volume mount validation when using raw YAML
New in Octopus Deploy 2018.8.11 (Oct 18, 2018)
- Allow additional Kubernetes resources to participate in the Deploy Containers lifecycle
- Validation rules now prevent creating an Ingress without a Service in the Deploy Kubernetes containers step
- Fixed a race condition in the UI during onboarding
- Fix for tenant variable loading issues with > 2100 tenants
New in Octopus Deploy 2018.8.10 (Oct 18, 2018)
- 4982 - Search field on “Include a Script Module” is now case-insensitive
- 4983 - K8S Secret and ConfigMap resources no longer deployed when the feature is disabled
- 4984 - K8S suggestion lists are now case insensitive
- 4985 - K8S Ingress host allowed variable substitution
- 4986 - Exposed annotations on the K8S deployment resource
- 4987 - Added extra help to the OpenID Connect authentication providers
- 4988 - BugFix: Acquisition of Helm charts fails when the username is empty
- 4992 - Fix for migrator importing proxies
New in Octopus Deploy 2018.8.9 (Oct 16, 2018)
- Fixed issue with running scriptcs on mono version 5.10 or newer
- Fixed exception when using Tentacle show-configuration command when no certificate is configured
- Made the license command more resilient and added a command-line switch to --skipLicenseCheck
- Improved how the license command handles encodings with the --licenseBase64 parameter
- Fixed proxy environment variables for authenticated proxies
- Fix a bug where project cannot be cloned when it has a scheduled trigger
- Fixed issue with application assembly references clashing with Azure PS references
- UI fix for Library Certificates paging issue
- Added addrefresh button to feed selection
- Ensure Helm values supplied by the Key/Value option are properly exploded
- Variable Sets used by a large number of snapshots no longer produce an error when deletion is attempted
- Exposed pod and container security context options for Kubernetes steps
- Tenant tags and tag sets are now correctly displayed in the order defined in the tag set
- Okta authentication provider updated so SSO now triggers login in Octopus portal
- The --instance command line argument is now case insensitive and required in fewer circumstances
- Multi-select drop downs (as used on the Manage Tenant Tags dialog) no longer open by default
- Fix a bug where project setting and create deployment page should not require TenantView permission for untenanted project
- Fixed a bug where onboarding would make duplicate requests after navigating around the UI
- Kubernetes authentication options are now more clearly defined
- Added better error message when kubectl could not be found
- Fixed backwards compatibility in Octopus.Client ProjectEditor.CreateOrModify function
- Azure and AWS logins supported for K8S targets
- The license command now allows licence as an alias
- The license command can now accept the license via a file
- SSH health checks no longer block other scripts from running on the same target
- Added filters to the api/reporting/deployments/xml endpoint
- Fixed an edge case where the ETag would not update
- The Configuration->Nodes page can now be filtered if there are multiple nodes
- New-OctopusKubernetesTarget can now be used to create new K8S targets
- Remove support for Ssl3.0
- Allowed Recreate and Rolling Update strategies to wait for the K8S deployment to finish
New in Octopus Deploy 2018.8.8 (Oct 4, 2018)
- Added ability to run script console on workers or worker pools
- Fix to show some missing usage reporting of Azure accounts in release snapshots
- Fix an issue where editing a lifecycle does not show correctly if the phase does not override the default retention policy
- Fix an issue where default worker pool wasn't selected by default for some steps when first created
- Kubernetes liveness probe scheme selection fixed
- Added additional validation for the Kubernetes target cluster URL
- Resolved issue with channel version rules for script step package references being lost when modifying deployment process
- Fix for incorrect warnings from migrator about missing machines
New in Octopus Deploy 2018.8.7 (Oct 2, 2018)
- 4616 - Log additional detail for failure messages on ARM deployments
- 4764 - Encrypt and write output variables to a file instead of passing them as a base64 encoded string for offline drop targets
- 4894 - Resolved issue with absolute paths to staged packages in offline-drops
- 4905 - Enable the ECR feed type for use in the kubernetes steps
- 4909 - Fix a bug where WorkerPool and Environment is not populated when adding Worker and Deployment Target
- 4912 - Newly added environments now appear on the dashboard correctly
- 4913 - Resolved issue with terraform steps not working through a proxy
- 4914 - Kubernetes Ingress host now accepts plain subdomains (e.g. http://example.org|example.org)
- 4916 - Reword 'Helm Update' command as 'Helm Upgrade'
- 4919 - Fixed an bug that stopped deployments from completing when an error occurred writing to the system log
- 4921 - Fixed "forcibly closed" error occurring in tentacle communications
- 4922 - Resolved issue migrating releases which contain named package references
- 4933 - Resolved issue where packages were not being displayed in release for Deploy a Release steps
New in Octopus Deploy 2018.8.6 (Sep 24, 2018)
- Halved the performance impact of the project dashboard for instances with many deployments
New in Octopus Deploy 2018.8.5 (Sep 18, 2018)
- 4266 - Fixed Halibut issue where connections were kept open by the server
- 4824 - Fixed memory issue in Halibut
- 4844 - Fix for Azure Web App query not returning resource groups
- 4872 - Fixed a error on the tenants screen after updating the name of a tag
- 4888 - Fixed a bug where triggers could create releases with invalid versions
- 4893 - Helm step now visible when Kubernetes steps are enabled
- 4895 - Fixed an issue where a package is reported as not acquired on a Worker even though it was
- 4896 - Variable-substitution and config-transform features enabled for Azure PowerShell script steps and Azure Service Fabric script steps
New in Octopus Deploy 2018.8.4 (Sep 12, 2018)
- Support for proxies in Azure CLI commands in Azure PowerShell script steps
- Variable substitution syntax now support replacement of text using regular expressions
- Support for proxies in AWS CLI in AWS CLI script steps
- Fixed a UI exception when deleting a user
- Added validation to ensure the project is entered on the Deploy Release step
- Added validation to the Windows Service step
- Azure CLI configuration written to subdirectory of Calamari working directory to avoid clashes with Variable Substitution
- Navigation shortcut via overflow menu from User Profile and User Listing pages to the Test Permissions page
- Create a user invite link directly from the Team edit page
- Improved handling of variable merging when using Octopus.Migrator.exe to import to a server where the project already exists
- The Octopus.Upgrader.exe file is now digitally signed allowing automatic Tentacle upgrades to work in environments where untrusted/unsigned executables are prevented from running
- Resolved issue with packages not being acquired when role matched no targets
New in Octopus Deploy 2018.8.3 (Sep 10, 2018)
- 4266 - Fixed Halibut issue where connections were kept open by the server
- 4812 - Improved messaging for different failure scenarios when running the database schema upgrades to be clearer about the state of their database, what they can do to get back up and running, and how to get help if they need it
- 4824 - Fixed memory issue in Halibut
- 4833 - Octo.exe, Octopus.Client and the TeamCity plugin (version 4.41.0+) now use delta compression when pushing packages to the Octopus Server
- 4859 - Variable substitution syntax now support replacement of text using regular expressions
- 4866 - Kubernetes container name validation now accepts variables
- 4867 - Helm Kubernetes Release Name now shows the variable bindings
- 4868 - Kubernetes service port names now accept variables
- 4870 - Fixed an error on the project dashboard if project ids on releases are lowercase
New in Octopus Deploy 2018.8.2 (Sep 5, 2018)
- Provide a bigger dialog when editing in-line ARM, CF and Terraform templates
- The data migration API /api/migrations/import now runs under the correct security context
- Markdown links are now shown correctly in highlight and fatal messages on the the Task Summary tab
- Fix for Azure Resource Group (ARM) step bug
- Packages from AWS ECR feeds will now show option to 'Not Acquire'
- UI adding concept images to help visualise the execution location/strategy in steps
- Server Web Request Proxy configuration now shown in Configuration - Settings
New in Octopus Deploy 2018.8.1 (Sep 4, 2018)
- 4850 - Fixed a bug where environments filter wasn't shown on the tasks page for users with scoped EnvironmentView permission
- 4851 - Updated AWS CLI to version 1.16.6
- 4852 - Fix an issue where a legacy azure web app would show an error when account or web site is bound
- 4853 - Token account type is now visible in the UI
New in Octopus Deploy 2018.8.0 (Sep 3, 2018)
- Highlights:
- 2018.8.0 introduces initial alpha level support for Kubernetes. These new steps, feeds and targets allow you to deploy Kubernetes Deployment, Service, Ingress, ConfigMap and Secret resources. You can find documentation of these features here.
- Client Versions:
- Octopus.Clients, the Octo CLI command line tools and the Team City plugin must be updated to version 4.39.4 to work with the new features in Octopus 2018.8.0.
- CloudFormation:
- We have added a new feature to the deploy CloudFormation Template step which enables the use of changesets. This allows transforms such as AWS::Serverless and AWS::Include to be used and optionally deferring execution in order to review changes as part of a manual intervention step before executing changes.
New in Octopus Deploy 2018.7.14 (Aug 27, 2018)
- Fixed an issue when cloning a project with scheduled triggers scoped to channel
- Fixed an issue where we were trying to deploy a child project after resuming from a manual intervention when that child project shouldn't be deployed due to deployment condition selected
- UI Optimise wasted space on the dashboards
- Octopus Server logs are now manually flushed when shutting down to avoid losing any messages written just prior to shut down
- Added DeploymentProcess link to deployment api response
- mproved descriptiveness of the scheduled task cleaner when it cleans up old task logs
New in Octopus Deploy 2018.7.13 (Aug 22, 2018)
- Service Fabric Script steps now use the new Service Fabric targets
- UI make re-deploy actions more discoverable and deploy actions less scary
- Fixed an issue where a large number of queued tasks would increase the time to start each of those tasks
- Lifecycle phase Required to Progress now respects value entered for Minimum # must complete option
- Added a warning when the first Worker is added to the default pool
- Resolved an issue that caused tasks and background processes to hang and also not cancel
- Reduced the number of times all machines are retrieved from the database
New in Octopus Deploy 2018.7.12 (Aug 20, 2018)
- 4580 - Fix for Audit/Event filtering where permissions conflicted or didn't return expected results
- 4775 - Allow Azure dropdowns to be refreshed
- 4806 - Fixed a bug where tenant variable events were not associated with tenant variable documents
- 4808 - Fixed a bug where removing the sensitive value from a tenant variable would not update the value
- 4809 - Fixed a bug where the step template side panel showed incorrect data when creating a new step template
- 4813 - Fixed incorrect usages of Azure APIs that affected Azure private clouds
- 4819 - Automatic release creation no longer attempts to write to auto deploy logs
- 4823 - Data subject deletion info and export options as part of user management screens
New in Octopus Deploy 2018.7.11 (Aug 16, 2018)
- 4738 - Azure PowerShell Script step now includes Azure CLI
- 4804 - Added a description of the scripts we plan to run when upgrading the database schema
- 4807 - UI soften layout transitions with a fade animation
- 4814 - Subscription number not being picked up when using management certificates
New in Octopus Deploy 2018.7.10 (Aug 14, 2018)
- 4698 - Remove virtual scrolling (and scrollbars) from dashboards and project overviews by default, with an option to turn them on
- 4797 - Fixed a bug where scopes were sometimes not shown in the variable editor for read only values
- 4798 - Fixed error when management certificate were being used for Azure Web App targets
- 4801 - Fixed incorrect account scoping error during health checks when cloud targets were using an account with scope restrictions
- 4803 - Fix incorrect package upload examples
New in Octopus Deploy 2018.7.9 (Aug 13, 2018)
- 4795 - Fixed the dashboard query for case-sensitive SQL servers
New in Octopus Deploy 2018.7.8 (Aug 9, 2018)
- 4765 - Cloud targets now run health checks via workers
- 4769 - Fix for dashboard crashes for users who had it configured to show an incompatible set of projects and environments
- 4770 - Fixed issue with Allow auto user creation being shown as disabled in the portal when it hadn't been explicitly set
- 4773 - Fixed a performance bug where the SQL Connection Pool could be exhausted by when clients are watching the progress of lots of tasks and the task log storage (usually network storage) is saturated
- 4777 - UI adding a save option to the 'unsaved changes' dialog
- 4780 - Fixed an issue that caused cloud target default worker pools to not be used in some situations
- 4786 - Fixed issue with upgrading the database causing a timeout
- 4788 - Reworked the dashboard backends to make them quicker and lighten the load on the SQL server
New in Octopus Deploy 2018.7.7 (Aug 1, 2018)
- [4750](https://github.com/OctopusDeploy/Issues/issues/4750 - Fixed issue where Deployment Target Triggers didn't trigger for projects with Deploy a release steps
- [4759](https://github.com/OctopusDeploy/Issues/issues/4759 - Removed the extra logging blocks in the deployment log when delta compression is performed
- [4760](https://github.com/OctopusDeploy/Issues/issues/4760 - UI refining both the accounts list and on-boarding panels and reintroducing our green primary buttons (#WooHoo)
- [4762](https://github.com/OctopusDeploy/Issues/issues/4762 - Performance improvements to Project Dashboard query
New in Octopus Deploy 2018.7.6 (Jul 31, 2018)
- 4761 - Halved the performance impact of the project dashboard for instances with many deployments
New in Octopus Deploy 2018.7.5 (Jul 30, 2018)
- 4513 - Fixed exception when setting up a scheduled trigger for a specific day of the month
- 4714 - Reduced the CPU usage when deploying to many machine in parallel within the same deployment
- 4733 - Fixed preservation of JAR manifest info during deployment
- 4748 - Reduced the amount of data that is retrieved from the database throughout the application
- 4749 - UI adding an overflow menu option from various documents to the auditing screen
- 4752 - Fixed Azure Web App deployment failure when no Resource Group is provided
- 4753 - Run package scripts during Azure Resource Group deployment
- 4754 - Fixed a bug which limited trial licenses to a single worker and worker pool, when trials are meant to get unlimited workers and worker pools
- 4755 - Target retention during deployment no longer retrieves all the machines multiple times
- 4757 - Send additional licensing and usage details back to octopus.com in addition to existing telemetry
- 4758 - The proxy selection is no longer cleared when expanding the proxy section on the Tentacle details page
New in Octopus Deploy 2018.7.4 (Jul 25, 2018)
- 4708 - Fixed bug preventing cancelling a deployment that is waiting for manual intervention
- 4718 - Reduced the amount of data retrieved from the database server for the the project dashboard and process pages, which reduces load on the database server and makes those pages faster when there are many environments
- 4719 - Fixed a rare issue where equal variable scopes were not be considered equal leading to a variable being added instead of replaced
- 4727 - UI adding a "HasWarningsOrErrors" flag to the tasks screen filters
- 4745 - Added an index to the User table
- 4747 - Fix an issue where OctopusUseBundledAzureModules variable was being ignored
New in Octopus Deploy 2018.7.3 (Jul 24, 2018)
- 4599 - Fixed issue where using Network Service or Local Service account for Windows Service accounts didn't work on non-English systems
- 4704 - UI indication of default values in project variable templates
- 4711 - Improved auditing on actions performed by the node command line operation
- 4715 - Manual intervention completion time is now recorded and logged
- 4716 - UI fix for environment vs target name filtering on the environments screen
- 4722 - Fix a bug where leading zero of a certificate's SerialNumber is truncated
- 4724 - Default to last version during deployment when no valid semver versions exist
- 4725 - Fixed compatibility issues in our Calamari update script using the -Directory parameter on the Get-ChildItem cmdlet on PowerShell 2.0
- 4726 - Fixed compatibility issues in Calamari using unsupported security protocols on servers that only have .NET 4.0 installed
- 4729 - UI adding a delete option to the release overview screen's overflow menu
- 4730 - Fix a bug where project variables not included in binding dropdowns in Start/Stop App in Tomcat step
- 4732 - Fix a bug where a null reference exception is thrown when try to save a project in add project dialog before all data are fully loaded
- 4734 - Fixed Dashboard error "Cannot read property 'projectIndex' of undefined"
- 4737 - Fix for UI bug in channel design rules
- 4740 - Fixed script syntax warning message in Azure and AWS PowerShell steps
New in Octopus Deploy 2018.7.2 (Jul 23, 2018)
- 4742 - Fixed a bug preventing upgrades to Octopus Server 2018.7.0 or 2018.7.1 with a message like Unrecognised document prefix Accounts- - please upgrade directly to 2018.7.2 or newer
- 4743 - Fixed a bug which mistakenly deleted non-orphaned library variable set snapshots when upgrading to Octopus Server 2018.7.0 or 2018.7.1 - please upgrade to 2018.7.2 or newer
New in Octopus Deploy 2018.7.1 (Jul 19, 2018)
- 4739 - Fixed a bug preventing upgrades from Octopus Server 2018.5.7 or earlier directly to 2018.7.0 - please upgrade directly to 2018.7.1 or newer
New in Octopus Deploy 2018.7.0 (Jul 18, 2018)
- 4158 - Octopus now allows multiple external workers, grouped into pools
- 4561 - Added support for specifying slots on Azure Web App targets and steps
- 4634 - Fixed query performance for Azure Web Apps
- 4710 - Fixing an edge-case with Service Fabric targets to deal with self-signed (and password-protected) certificates
- 4712 - Changed S3 multi file selections bucket key prefix to be optional
New in Octopus Deploy 2018.6.15 (Jul 12, 2018)
- 4436 - UI improvements to removable list components (for consistency and easy-of-use)
- 4546 - Cloudformation and Terraform inline script permission required changed to ProcessEdit
- 4647 - Fixed an issue where legacy variable Octopus.Action.Azure.UseBundledAzurePowerShellModule wasn't being honoured
- 4669 - Add an option to exclude a machine from the rest of the deployment when using guided failure
- 4700 - UI improvements to update variable snapshot to make this feature more accessible
- 4705 - Fixed issue where randomly getting "Cannot read property 'projectIndex' of undefined" error
- 4706 - Fixed issue where urls referenced in task logs were converted to lowercase during render
New in Octopus Deploy 2018.6.14 (Jul 9, 2018)
- Fatal error messages are now displayed on the task summary
- Fixed the "Load more" paging button, broken in 2018.6.12
New in Octopus Deploy 2018.6.13 (Jul 5, 2018)
- Tasks running on a node that no longer exists are now marked as failed
- Variables to be passed to a Deploy a Release step are only evaluated after being deserialized from JSON
- Output variables are now collected when resuming a child project from an interruption that is deployed using a Deploy a Release step
- Scheduled Trigger for project with Deploy a Release step no longer fails deployment with error The resource 'users-system' was not found.
- Multiple simultaneous interruptions no longer block a deployment from proceeding
- Send email step and test email can now be cancelled
- Server Task Cap and Maintenance Mode state are now included in the output of the show-configuration command
- The UI now caches the available roles, making editing projects quicker when there are a large number of deployment targets
New in Octopus Deploy 2018.6.12 (Jul 4, 2018)
- 4655 - Automatic machine removal no longer logs a warning if a machine doesn't have a machine policy
- 4657 - Project overview advanced filters now include filter by environment
- 4666 - Release version filters out spaces now
- 4678 - Selected packages in a release is now properly populated when migrating a 2.6 instance
- 4689 - Deployment creation is now faster when there are many previous deployments for that release
- 4692 - Infrastructure|Environments now uses paging to improve rendering performance on large lists
New in Octopus Deploy 2018.6.11 (Jul 2, 2018)
- Octopus Server node deletion is now vetoed when tasks are still running on the node
- The command Octopus.Server.exe node can now be used to configure Octopus Server nodes
- Email step and subscriptions correctly account for team membership via external security groups
- Deployment error variables are now cleared when a new auto-deployment is queued up
- Reinstate variable substitution in TF template files from packages
New in Octopus Deploy 2018.6.10 (Jun 29, 2018)
- 4684 - this.replaceLoop is not a function javascript error is now fixed
New in Octopus Deploy 2018.6.9 (Jun 28, 2018)
- Reduce polling frequency of project and main dashboards when page is hidden
New in Octopus Deploy 2018.6.8 (Jun 27, 2018)
- Lifecycle auto-deploy-environment now work with tenants
- Octopus high availability clusters are no longer susceptible to military coup when tasks running on the leader node take too long
- "Script0001 - Release to VariableSet RelatedDocument.sql" can now handle migration of large numbers of library variable sets in releases
New in Octopus Deploy 2018.6.7 (Jun 26, 2018)
- Output variables created by deployment steps, such as package installation directory, are now passed through to subsequent steps for offline drop targets
- Fixed a bug with channel scoping when evaluating certificate variables
- The dashboard overview is now much quicker if lots of tags are in use
- Fixed an exception loading feeds in Azure steps when lacking the AccountView permission
- Variable evaluation speed has been improved, making (among lots of other things) built-in repository retention much quicker when there are many variables
- fixed permission check on create account
New in Octopus Deploy 2018.6.6 (Jun 25, 2018)
- 4632 - Special characters in package names are now escaped for offline drops
- 4656 - Bugfix - Avoid double variable replacement of scripts. Introduced in 2018.5.5
- 4662 - Dashboard groups are now appropriately resized when filters are applied
New in Octopus Deploy 2018.6.5 (Jun 20, 2018)
- Fixed error when updating releases on sql servers with case-sensitive collations
New in Octopus Deploy 2018.6.4 (Jun 19, 2018)
- Project Switcher filter no longer selects the wrong item
- Fix for HashTable parameter error in Service Fabric Deploy Step
- Fixed an error in the accounts overview in Internet Explorer
- Dashboard groups that don't require a scrollbar no longer scroll a few pixel with the mouse wheel
- Improved the speed of Release deletion
New in Octopus Deploy 2018.6.3 (Jun 18, 2018)
- Set Package Transfer file name with standard name format
- Now correctly excluding disabled deployment targets from licensing limits
New in Octopus Deploy 2018.6.2 (Jun 14, 2018)
- Specific and Excluded targets are retained when a deployment fails and it is then re-tried
- Improvements for when choosing a tag with a large number of tenants on the create deployment screen
- Trials started after 30 March 2018 will not fall back to the free Community Edition https://octopus.com/blog/removing-free-tier
- Fix for unknown environment/certificate issue on Service Fabric targets
- Fixing some daily UX frustrations
- The markdown renderer now ignores _ in the middle of words for formatting purposes
- The variable substitution syntax now supports encoding a variable as Base64
- Fixes an issue preventing auto machine cleaning from adding events for machine deletion
New in Octopus Deploy 2018.6.1 (Jun 12, 2018)
- 4518 - Improved the rendering performance of the dashboard and project overview when there are a large number of cells to display
- 4608 - ApiKeys API paging links corrected to stop error in Octopus.Clients and load all keys in the UI when a user has > 30 keys
- 4610 - Server now checks whether there is enough free space before writing the configuration file
- 4624 - Fixed a bug that prevented Team Add/Edit page from loading
- 4626 - The “running tasks” link on the Configuration->Nodes page now filters for running tasks for that node, rather than all tasks on that node
- 4629 - Added step number to the step edit page
New in Octopus Deploy 2018.6.0 (Jun 11, 2018)
- New Features:
- Laying groundwork for workers
- Laying groundwork for spaces
- Sensitive output variables
- Control types for prompted variables
- Breaking Changes:
- With the foundations for workers going in, we're removing the Octopus.Server.exe external-worker command which allowed a single Tentacle to replace the built-in worker. If you are already using Tentacle as an external worker, we will automatically migrate it as the first worker in the default worker pool. Learn about managing external workers in Octopus Deploy 2018.6 and newer.
- Also, because workers, like deployment targets, can be health checked, one of the arguments to health check and upgrade tasks has been tweaked. If you use the UI, nothing changes. If you insert tasks through the API with an argument, e.g. like ...ExecuteHealthCheck(environmentId: "Environments-21") from the clients library, nothing changes. But if you create health check or upgrade tasks with no arguments, this now means for all deployment targets and all workers. Use restrictTo: "DeploymentTargets" for all deployment targets and restrictTo: "Workers" for all workers.
- Otherwise there aren't any breaking changes in this release so you can upgrade worry free!
- Licensing Changes:
- Back in Febuary this year, we announced we will no longer support the free Community Edition of Octopus Deploy. Starting with Octopus 2018.6 we will be enforcing that decision in the product itself using a cutoff date of 31 March 2018:
- If you already have a commercial license for Octopus Deploy, nothing has changed for you.
- If you are already using the free Community Edition, don't worry, it will keep working!
- If you started a trial of Octopus Deploy before the cutoff date, nothing has changed for you. Your trial will automatically downgrade to the free Community Edition.
- If you started a trial of Octopus Deploy after the cutoff date, you will need to purchase a commercial license once your trial concludes. Don't worry, we've introduced some very affordable commercial licenses.
New in Octopus Deploy 2018.5.7 (Jun 4, 2018)
- 4565 - Fixed the managed account hint text on the terraform step
- 4609 - BugFix - DockerRun command on Windows failing
- 4612 - Extra options on the setup wizard when requesting a trial key
- 4613 - Bugfix - Properly encode non-ASCII characters in scripts
- 4615 - Added ability to attach Terraform logs as artifacts
New in Octopus Deploy 2018.5.6 (May 30, 2018)
- 4576 - Fixes for target ordering in multi-selects and various UX improvements, including minor updates for customers operating at lower resolutions
- 4600 - Fix project variable helper not including project variables for S3 step
- 4603 - BugFix - Tentacle upgrade process fails in 2018.5.5
- 4604 - Fixed bug with custom scripts on Azure RM template step
New in Octopus Deploy 2018.5.5 (May 29, 2018)
- 4509 - Fixed an issue upgrading from versions prior to 3.4 to versions after 2018.4
- 4548 - Fixed problem where offline drop packages were not using the right escape characters for quoting the variable file as part of the Calamari command
- 4568 - Fixed bug when updating an existing Service Fabric or Cloud Service target from cmdlets
- 4572 - Steps now correctly load PowerShell modules when running on the external worker
- 4587 - Changed behaviour for project with no healthy targets and environment with no dynamic infrastructure
- 4592 - Corrected values in Azure Environment configuration
- 4593 - Fixed a bug which prevented Team Edit page from loading
- 4594 - Perform variable replacement for inline scripts on the Target rather than Server
- 4596 - Fixed bug where variable usage was not showing on Azure Accounts
- 4597 - Fixed errors displayed in console relating to missing machine icons
- 4598 - Fixed error with rendering Azure Account variables
New in Octopus Deploy 2018.5.4 (May 28, 2018)
- Fix for a timing problem that was causing browser redirect issues on slow connections
New in Octopus Deploy 2018.5.3 (May 24, 2018)
- Improved long path support, including package extraction and offline drops, see https://octopus.com/docs/deploying-applications/custom-scripts/long-paths for more details
- Allow password to be passed as parameter to offline-drop scripts
- Viewing of Library Variable Sets will now check for VariableViewUnscoped instead of incorrectly checking for VariableEditUnscoped
- Added project groups to configuration options for dashboard filtering
- Add project dialog updated to guide the user to group and life-cycle selection once there are multiple groups or life-cycles, or there is at least one existing project
- SMTP Configuration save and test action is now available in UI to users with ConfigureServer permission
New in Octopus Deploy 2018.5.2 / 3.20.0 Tentacle (May 22, 2018)
- Output-variables can now be flagged as sensitive
- Users can now modify tenant Common Variables if they have access to all projects and/or all environments this tenant is connected to with VariableEdit permission
- Resolved issue using version mask in pre-release tag when creating release
- Fixed issue preventing a script console scripts targeting more than one tenant
- Improved task log messages when a server task is blocked by another server task
- Enforce obfuscation in deployment logs of sensitive variables contributed via machines (CVE-2018-11320)
- The built-in repository now applied retention rules to packages that are dynamically referenced
New in Octopus Deploy 2018.5.1 (May 15, 2018)
- 3637 - Updated Azure SDK dependencies to latest. Updated Azure PowerShell Modules to v5.7.0
- 3731 - Added warnings about Management Certificates for Azure's up-coming June 30th deprecation deadline
- 3821 - Restricting Cloud Services to Management Certificate accounts at the API
- 3860 - Updating Calamari to include latest Azure PowerShell cmdlets
- 4195 - Updating Calamari to .NET452 for latest Azure ARM templates
- 4461 - Adding support for uploading and exporting certificate chains in the PEM format
- 4532 - Updated bundled AWS cli to version 1.15.18
- 3544 - Automatically uploading certificates for Service Fabric clusters
- Specific to 2018.5.1:
- 4346 - Server retention policy now deletes releases as part of the retention policy task instead of creating a task for each document to be deleted
- 4426 - Improvements to package and release search UX
- 4520 - Fixes an issue in using inline Terraform templates
- 4527 - Fixes an issue preventing Terraform steps running on external workers
- 4535 - Fixes an issue preventing AWS S3 steps running on external workers
- 4536 - Fixes an issue in using AWS CLI step on external workers
- 4554 - Refactored Calamari to support multiple authentication contexts
- 4556 - Fixed an issue introduced in 2018.5.0 which prevented including/excluding specific deployment targets in a deployment
New in Octopus Deploy 2018.5.0 (May 14, 2018)
- Features and Highlights *
- Introducing Dynamic Target Provisioning
- Introducing Azure Accounts as variables and new Azure deployment targets
- Azure PowerShell and SDK updated to latest
- See blog post for full details
- Breaking Changes *
- .NET 4.5.2 is now the minimum version (due to Azure SDK updates)
- PowerShell 5.0 is now the minimum version for Azure deployments (minimum required by Azure PS Cmdlets)
- Azure Web Apps now include deployment warnings (management certificates are being deprecated by Azure as of June 30th 2018)
- Azure recently announced that from June 30th 2018 they are retiring support for Service Management API (NOTE: Management Certificates use Service Management API). This affects deployments to Azure App Services.
- Please switch to using Service Principals for your Octopus Azure accounts where possible: https://g.octopushq.com/AzureServicePrincipalAccount
New in Octopus Deploy 2018.4.12 (May 9, 2018)
- 4391 - Fixed error causing tentacles to remove tenanted mode when registered multiple times from the command line
- 4545 - Tomcat network timeouts increased to 5 minutes
New in Octopus Deploy 2018.4.11 (May 8, 2018)
- 4526 - Fix issue where local project variables weren't shown for both terraform and cloud formation templates
- 4534 - Fixed timezone conversion issue with weekly & monthly scheduled triggers
New in Octopus Deploy 2018.4.10 (May 2, 2018)
- 4439 - Fix a bug where Project Switcher highlights the entire container rather than the selected project
- 4523 - Resolved issue with automatic-release-creation when project contains a Deploy Release step
- 4529 - Fix for incorrect start time shown on Scheduled Project Trigger summary
New in Octopus Deploy 2018.4.9 (May 1, 2018)
- Fixed a problem which prevented you from deleting/revoking an API Key which was introduced in 2018.1.0
New in Octopus Deploy 2018.4.8 (May 1, 2018)
- 4524 - When debugging Octopus Variables as part of a deployment, the variables are now printed in alphabetical order by name instead of the order they are added to the variable dictionary
- 4525 - Fix issue where CloudFormation step wasn't properly registered in the UI
New in Octopus Deploy 2018.4.7 (Apr 30, 2018)
- 4454 - Fixed a security hole where target and tenant tag variable scopes were not checked against the list of tenants the user has access to
- 4474 - Fix a bug where environment scoped users without VariableEdit permission can save variable
- 4517 - Fixed a bug where conversion from Sensitive variable type to Certificate variable type was broken
- 4522 - Fixed error when a new pipeline step resumes from manual intervention
New in Octopus Deploy 2018.4.6 (Apr 26, 2018)
- Fixed timezone conversion issue with scheduled project trigger start time
- Offline Drops now escape script parameters, fixing a bug introduced in 2018.3.8
New in Octopus Deploy 2018.4.5 (Apr 26, 2018)
- 4468 - The Tentacle included in this release registers faster when the Octopus Server has many environments or tenants
- 4503 - Fix S3 Package.FileName output variable not set
New in Octopus Deploy 2018.4.4 (Apr 23, 2018)
- Removed parts of the old deployment pipeline, as well as the OctopusActionUseNewExecutionDispatcher variable
- Compatibility fix for Offline Drop output variables on PowerShell 2
- Regression in Terraform destroy step is resolved
- Removed -var-file options from terraform init command
New in Octopus Deploy 2018.4.3 (Apr 20, 2018)
- Deep links containing filters are preserved correctly across the login process
- Use FQDN examples for built-in repository examples
- Fixed a problem where run-on-server-on-behalf-of scoped AWS and Azure steps would sometimes run on the target instead of the server
- The IIS, Windows Server, Terraform and VHD steps now use the new pipeline
- Fixed migration that was deleting library variable snapshots even when they were still in use
- Resolved exception when a null variable is defined as a CloudFormation output
- Fixed an exception in the Configuration, Settings page
New in Octopus Deploy 2018.4.2 (Apr 19, 2018)
- Deep links containing filters are preserved correctly across the login process
- Use FQDN examples for built-in repository examples
- Fixed a problem where run-on-server-on-behalf-of scoped AWS and Azure steps would sometimes run on the target instead of the server
- The IIS, Windows Server, Terraform and VHD steps now use the new pipeline
New in Octopus Deploy 2018.4.1 (Apr 18, 2018)
- 4178 - The built-in repository can now delete unused packages that are dynamically referenced. See the details of this issue for instructions on how to enable this feature
- 4393 - Offline drop now only includes each package once per release
- 4456 - Individual variable files can now be listed in the Terraform step, and the apply and init terraform actions can have additional arguments passed to them
- 4471 - Added tenant selector for running ad-hoc scripts per tenant
- 4477 - The permission required to delete users has been relaxed from AdministerSystem to UserEdit, with the caveat that you cannot delete yourself, and only System Administrators can delete other System Administrators
- 4479 - Fixed SQL error when using taskState in deployments API
- 4481 - Octopus.Action.Terraform.CustomTerraformExecutable can be set to the location of a customer terraform executable
- 4483 - Task details page doesn't crash anymore when the log contains PowerShell code that invokes a static method
- 4485 - Improved performance in reading the stream from SSH targets
- 4488 - The Server Extensibility API has changed and custom extensions will need to be updated
- 4490 - Convert OfflineDrop Write-Host to Write-Output in bootstrapper
- 4491 - Resolved a step execution performance issue when there are lots of variables that was introduced in 2018.3.8
- 4493 - Terraform updated to 0.11.7
New in Octopus Deploy 2018.4.0 (Apr 17, 2018)
- 3633 - Added a new project trigger for recurring scheduled deployments
- 4365 - Deployment Steps can be marked as required, meaning they cannot be skipped when customizing a deployment
- 4422 - Fixed a problem where Variable Sets were deleted even when they were used by existing releases
- 4433 - Release version search in Deploy a Release now displays Load More
- 4448 - Fix for error when filtering Tenants and user does not have view permissions for some Environments
- 4463 - Fix for show and hide empty groups on Project dashboard
- 4473 - Fixes for “Deploy To” button popover on mobile
- 4482 - Added the new AWS S3 upload step for uploading files to an S3 bucket with all the bells and whistles
New in Octopus Deploy 2018.3.13 (Apr 11, 2018)
- Various accessibility updates and improvements to the UX (and fixing broken avatar images on closed networks)
- Fixed a performance problem in Variable Editor where rendering of variables with a lot of values was slow
- HCL parsing logic moved into separate open source library
New in Octopus Deploy 2018.3.12 (Apr 10, 2018)
- Fixed error when viewing tenant variables if user lacked permission to see other associated environments
- 4449 - Fixes an error that stopped users from health checking all environments they had permission to
- 4455 - Update Terraform to 0.11.6
- 4460 - Variable replacement occurs for scripts sourced from packages, fixing a bug introduced in 2018.3.8
- 4462 - Scripts sourced from packages are no longer executed with incorrect arguments, fixing a bug introduced in 2018.3.8
New in Octopus Deploy 2018.3.11 (Apr 6, 2018)
- Fixed an error loading variables, step templates and script modules when there are many machines
New in Octopus Deploy 2018.3.10 (Apr 5, 2018)
- We warn user now when they select a cert file that is empty
- Lists with parameters can now be manually ordered
- Dashboard filters are now stored in the query string in the URL
- Fix a bug where deployment process page crashed if there is an IIS step that has no bindings
- Do not open new window when clicking on links in task log page
- Library variable set filter when including a library variable set in a project is now case insensitive
- When using the service command to start and stop the Octopus Server service and the service does not exist, Octopus and Tentacle will now report an error
- Improved performance when validating tenant connections
- The variable editor now only warns on specific zero width characters, and no longer has false positive warnings for non-ASCII characters
- Fix for events/audit not being returned when user had scoped permissions applied
New in Octopus Deploy 2018.3.9 (Apr 4, 2018)
- 4118 - Switched from 4 to 2 spaces for list indentation in markdown
- 4203 - Fix for issue where when filtering projects or dashboard would cause the header title to disappear
- 4397 - Fix a bug where project variables are not showing in Run a Docker Container step
- 4401 - The Secure flag is now set consistently for Cookies regardless of whether the incoming HTTP request is behind a proxy using SSL offloading
- 4428 - Certificate expiry events are now generated for a certificate that has replaced another certificate if the original certificate had either of the certificate expiry events created
- 4431 - AWS steps now acquire packages correctly when used as child steps
- 4441 - The OctopusBypassDeploymentMutex now does what it is supposed to do, fixing a bug introduced in 2018.3.8
- 4175 - Fixed display issue on Project descriptions that have markdown
New in Octopus Deploy 2018.3.8 (Mar 28, 2018)
- Swagger spec now takes virtual directories into account
- Package notes now show if they are missing, or if the notes can not be retrieved
- Fix a bug where dashboard environment scrollbar loses its position when data updated
- Fixed broken links to triggers and channels in the audit log
- Implemented a new deployment pipeline which lays the groundwork for future features. It is enabled for Run Script, Deploy Package and Run AWS Script steps
- The Step Template -> Run feature now treats sensitive parameters correctly instead of passing them to the server as clear-text
- Support Output Variables for Offline Drop
- Insert variable doesn't throw an error when filter contains regex characters
- Fixed up the package acquisition for AWS CloudFormation steps when workers are used
New in Octopus Deploy 2018.3.7 (Mar 26, 2018)
- Release creation page combines requests for the same package + channel filter combination
- Fix a bug where users can see machines beyond their team’s scoped environments in variable editor
- Default the GitHub Feed url with public GitHub api endpoint
- Updated Terraform executable to 0.11.5
- Fixed the parameters file used when deploying cloudformation templates from a package
New in Octopus Deploy 2018.3.6 (Mar 21, 2018)
- A 400 Bad Request error with reason in response body instead of a 500 Internal Server Error is now returned when trying to create a release on a disabled project
- Added additional logging when a TaskCanceledException is thrown
- Fixed configuration migration issue when upgrading from 3.x
New in Octopus Deploy 2018.3.5 (Mar 20, 2018)
- No longer displaying two horizontal scrollbars in project dashboard
- Admin command line now supports adding groups from Active Directory, and groups/roles from AzureAD and Okta
- Administrators can now control whether users are allowed to edit their own external Logins
- Password required validation no longer appears when creating service account users
- Group claim handling fixed in the Okta and Azure AD authentication providers
- Added steps for planning to apply or destroy Terraform templates
- Fixed bug causing exceptions for offline drops when path is too long
- Teams with EventView scoped to Projects will not receive Subscription output
- "Prompt for value" checkbox in the variable editor is working again
- If you lose your master key you can now use the Octopus.Server.exe lost-master-key command to generate a new master key, scrub all your sensitive data, and get back up and running again
- It is no longer possible to select an invalid value for a certificate variable
- Project ID in Deploy Release step is now correctly mapped when migrating
- Variable channel scopes are now correctly mapped when migrating
- Github external feed testing and object reference null error
- Github feed trailing whitespace
- Checkbox-type variable templates now correctly display default values
New in Octopus Deploy 2018.3.4 (Mar 14, 2018)
- Fixed a bug with row heights in the project overview
- Fixed an exception when a user signs out
New in Octopus Deploy 2018.3.3 (Mar 12, 2018)
- Sort deployment targets by name during rolling deployments so the deployment order is deterministic
- Fixed an issue where the tenants page may sometimes fail to load when there is a large number of projects
- Fixed exception when downloading packages with 4 part version numbers on SSH targets without mono
- Fix for errors incorrectly showing user lacks VariableEdit if that permission was scoped to Projects
- Permanently enabled the Docker and Browser Caching features, and multi-tenancy is enabled when a tenant is first created
- Increased network timeouts when interacting with Tomcat from 30 to 60 seconds
- Terraform steps now include a field to allow a workspace to be defined
New in Octopus Deploy 2018.3.2 (Mar 9, 2018)
- Fixed problem with Variable Editor creating values that can't be saved
- Audit log filtering would error in some cases and this is fixed now
- Ensuring we can render old releases in project overview
- A new log level Highlight has been added that highlights the message in the log and shows it on the Task Summary tab
- Fixed a bug where in some situations, the read only table of variables would extend beyond the available screen width
- Added an upgrade script to clean up orphaned channel version rules
- Fixed subscriptions and web hooks that were not firing for users who had scoped permissions
- Fixed issue when upgrading a system with an Octopus Managers team
- Fixed issue with the AzureAD authentication provider sometimes getting a signature error while validating tokens
- Release page navigation links now work regardless of whether the current URL contains a trailing slash
- Open markdown links in a new window
- Fixed a bug where the tenant tags would be pre-filled on the create deployment page if you had navigated to a create deployment url for deploying to specific tenants
- Stop showing a delete option in the UI if you don't have access to view a particular user
- Additional error logging is generated for network errors when deploying CloudFormation templates
- Fixed error in queueing tasks when 1000's of tasks are ready to run
- Add #{else} to the existing #{if} statement in the variable substitution syntax
- Artifacts now appear under the step heading on the Task Summary page
- Add terraform apply and destroy steps
- Cloudformation dynamic variables form does not recognise specilised lists
- Cloudformation step will exit early if there are nested stacks
- Fixed a bug where the environments filters would disappear if no environments matched the current filter
- Fixed an issue where searching through certificates might fail for some types of certificates
- Removed redundant call to /api/projects/all from getting-started component
- Fixed metrics logging to not use quotes around numbers
- Added a field to allow additional files to have variable substitution applied to them from Terraform packages
- Additional file extensions are now downloaded from Maven repositories
- Null reference exception removed when the AWS region is incorrect
- Fix for the error about missing EventView permission on the release page when it is scoped to Projects
New in Octopus Deploy 2018.3.1 (Mar 8, 2018)
- Fixed problem with Variable Editor creating values that can't be saved
- Audit log filtering would error in some cases and this is fixed now
- Ensuring we can render old releases in project overview
- A new log level Highlight has been added that highlights the message in the log and shows it on the Task Summary tab
- Fixed a bug where in some situations, the read only table of variables would extend beyond the available screen width
- Added an upgrade script to clean up orphaned channel version rules
- Fixed subscriptions and web hooks that were not firing for users who had scoped permissions
- Fixed issue when upgrading a system with an Octopus Managers team
- Fixed issue with the AzureAD authentication provider sometimes getting a signature error while validating tokens
- Release page navigation links now work regardless of whether the current URL contains a trailing slash
- Open markdown links in a new window
- Fixed a bug where the tenant tags would be pre-filled on the create deployment page if you had navigated to a create deployment url for deploying to specific tenants
- Stop showing a delete option in the UI if you don't have access to view a particular user
- Additional error logging is generated for network errors when deploying CloudFormation templates
- Fixed error in queueing tasks when 1000's of tasks are ready to run
- Add #{else} to the existing #{if} statement in the variable substitution syntax
- Artifacts now appear under the step heading on the Task Summary page
- Add terraform apply and destroy steps
- Cloudformation dynamic variables form does not recognise specilised lists
- Cloudformation step will exit early if there are nested stacks
- Fixed a bug where the environments filters would disappear if no environments matched the current filter
- Fixed an issue where searching through certificates might fail for some types of certificates
- Removed redundant call to /api/projects/all from getting-started component
- Fixed metrics logging to not use quotes around numbers
- Added a field to allow additional files to have variable substitution applied to them from Terraform packages
- Additional file extensions are now downloaded from Maven repositories
- Null reference exception removed when the AWS region is incorrect
- Fix for the error about missing EventView permission on the release page when it is scoped to Projects
New in Octopus Deploy 2018.3.0 (Mar 7, 2018)
- Fixed problem with Variable Editor creating values that can't be saved
- Audit log filtering would error in some cases and this is fixed now
- Ensuring we can render old releases in project overview
- A new log level Highlight has been added that highlights the message in the log and shows it on the Task Summary tab
- Fixed a bug where in some situations, the read only table of variables would extend beyond the available screen width
- Added an upgrade script to clean up orphaned channel version rules
- Fixed subscriptions and web hooks that were not firing for users who had scoped permissions
- Fixed issue when upgrading a system with an Octopus Managers team
- Fixed issue with the AzureAD authentication provider sometimes getting a signature error while validating tokens
- Release page navigation links now work regardless of whether the current URL contains a trailing slash
- Open markdown links in a new window
- Fixed a bug where the tenant tags would be pre-filled on the create deployment page if you had navigated to a create deployment url for deploying to specific tenants
- Stop showing a delete option in the UI if you don't have access to view a particular user
- Additional error logging is generated for network errors when deploying CloudFormation templates
- Fixed error in queueing tasks when 1000's of tasks are ready to run
- Add #{else} to the existing #{if} statement in the variable substitution syntax
- Artifacts now appear under the step heading on the Task Summary page
- Add terraform apply and destroy steps
- Cloudformation dynamic variables form does not recognise specilised lists
- Cloudformation step will exit early if there are nested stacks
- Fixed a bug where the environments filters would disappear if no environments matched the current filter
- Fixed an issue where searching through certificates might fail for some types of certificates
New in Octopus Deploy 2018.2.7 (Feb 28, 2018)
- Each Octopus server node may execute one (non deployment or health check) task beyond its task cap, so that tasks such as subscriptions are not blocked by long running deployments or health checks
- Use octopurls for documentation urls
- "MaxConcurrentTasks" is now the sum of all server node's task caps. Command option Octopus.Server.exe configure --maxConcurrentTasks ... is deprecated
- Tentacle auto-upgrades are now blocked for a machine that is being auto-deployed to
- Tasks are allocated more evenly to Octopus server nodes in High Availability Octopus
- Displayed the deployment start time instead of the queued time on the dashboard and release pages
- Deploy Release step task log now includes link to child deployment
- Only run autocomplete hack for Chrome on Sign-In screen
- CloudFormation steps now populate the proxy configuration
- Correctly handle missing deployments when processing auto deploy events
- Disabled child steps can no longer have a duplicate name
- Fixed an error on the Release Detail page when a user does not have TaskView permission
- Improved log message when importing certificate-chain which already exists
- User login bans, due to too many failed attempts, now appear in the Audit log
- Update our SSH library so that it works on Octopus servers with FIPS enabled
- Explicitly reject all HTTP TRACE requests rather than treating them as a GET in some cases
- Tenanted deployments will always be executed in the order that they appear in the task queue
- Account Edit page now loads usage data asynchronously to avoid blocking the UI
- Default values on Tenant Variables are not displayed on V4 Variable Editor
- Fix for TypeError: Cannot read property 'State' of undefined on Release page, for users with TaskView permissions scoped to Environments
- Added metrics command for configuring metrics logging
- Fixed High CPU usage when there are not tasks in the queue or the node is in maintenance mode
- "Deploy a package" step now has access to Maven feeds
- Removed the word "anonymous" from the installation wizard's consent to collect usage data - the word "anonymous" was mistakenly added in Octopus 3.12.0
New in Octopus Deploy 2018.2.6 (Feb 22, 2018)
- Each Octopus server node may execute one (non deployment or health check) task beyond its task cap, so that tasks such as subscriptions are not blocked by long running deployments or health checks
- Use octopurls for documentation urls
- "MaxConcurrentTasks" is now the sum of all server node's task caps. Command option Octopus.Server.exe configure --maxConcurrentTasks ... is deprecated
- Tentacle auto-upgrades are now blocked for a machine that is being auto-deployed to
- Tasks are allocated more evenly to Octopus server nodes in High Availability Octopus
- Displayed the deployment start time instead of the queued time on the dashboard and release pages
- Deploy Release step task log now includes link to child deployment
- Only run autocomplete hack for Chrome on Sign-In screen
- CloudFormation steps now populate the proxy configuration
- Correctly handle missing deployments when processing auto deploy events
- Disabled child steps can no longer have a duplicate name
- Fixed an error on the Release Detail page when a user does not have TaskView permission
New in Octopus Deploy 2018.2.5 (Feb 19, 2018)
- Reducing reflow of dashboard status tables to improve performance
- Disabling keyboard form submissions on Script Console / AdHoc script
- Bring back predictable order to the Add Step page
- Fixed a deployment error when using script modules with paths that have ' in them
- Improve the database indexes used during auto deploy creation
- Fixed bug introduced in 2018.2.0 that caused Calamari upgrade to loop indefinitely if the customBundledPackageDirectory option is used
New in Octopus Deploy 2018.2.4 (Feb 19, 2018)
- Fix a bug where Deploy to button is missing from the Task page
- Excluded steps are now preserved between retries
- Fixed a problem where teams scoped to an environment couldn't add project variable templates
- Now you can add an environment to a lifecycle phase without having EnvironmentCreate permission
- Added inline note that explains when tenanted deployments are available
- Code editor full screen toggle no longer overlays scrollbar
- Custom Install Directory feature shows now correctly whether files will be purged or not
- Don't specify /bin/bash when performing a raw file transfer to an SSH target
- Prevent child releases to many tenants exhausting the task cap
- Fixed text-wrapping behaviour in long section titles
- Allow channel version rules based on deploy release steps
- Variable Template heading displays now Label instead of Name when Label is available
- Azure account scoped to both tenanted and untenanted can now deploy to untenanted deployments
- Prevent the deploy release step from being added as a child step
- Fixed UI issue where changing settings asked for AdministerSystem permission instead of ConfigureServer
- Reduce strictness of package filename encoding to allow + characters in path
New in Octopus Deploy 2018.2.3 (Feb 14, 2018)
- Project name is now a link (when not bound to a variable)
- Added metric logging to track api calls and tasks
- Resolved error when creating release for projects containing a Deploy Release step
New in Octopus Deploy 2018.2.2 (Feb 13, 2018)
- Package selector and Release selector are not showing double scrollbars anymore
- Added validation to ensure that Deploy to IIS steps include package details
- Powershell AWS modules are now exposed to the AWS CLI script step
- Fix a frontend crash when the project dashboard can't find the channel for a dashboard item
- Fixed a bug which prevented variable value from being displayed in the variable editor popup
- Fix a frontend crash on the project triggers page when an invalid ARC step is selected
- Allow prompted variables in child deployments to be bound from variables on the parent
- Fix bug causing channels with version rules to sometimes not auto-select latest package
New in Octopus Deploy 2018.2.1 (Feb 8, 2018)
- When scrolling through many environments in project overview, the releases column is now fixed
- Fixed missing audit entry when a variable scoped to a single environment and that environment is deleted
- Fixed role deletion mechanism, it will now be removed from teams that were referencing it, after the user is shown a warning
- Add account usage UI to /infrastructure/accounts/[account]
- Packages API does not meet the requirements of our expanding feed types
- Projects overview table first column is now fixed width
- Added new step: Deploy a Release
- Modify the cache naming format to allow for new feed formats
- Added additional steps and account types to support AWS scripts and CloudFormation deployments
- Fixed a bug where deleting a channel could result in orphaned channel version rules and break the project dashboard
- Fixed a bug with incorrect target counts on the infrastructure dashboard under tenant target sets
- When AutoDeployLastProcessedEventAutoId is null Octopus attempts to process all previous events
- .2 Bug Bash Feeback: Delete Account
- Fixed permission issue where users deploying a project they had permissions for would fail
New in Octopus Deploy 2018.2.0 (Feb 8, 2018)
- When scrolling through many environments in project overview, the releases column is now fixed
- Fixed missing audit entry when a variable scoped to a single environment and that environment is deleted
- Fixed role deletion mechanism, it will now be removed from teams that were referencing it, after the user is shown a warning
- Add account usage UI to /infrastructure/accounts/[account]
- Packages API does not meet the requirements of our expanding feed types
- Projects overview table first column is now fixed width
- Added new step: Deploy a Release
- Modify the cache naming format to allow for new feed formats
- Added additional steps and account types to support AWS scripts and CloudFormation deployments
- Fixed a bug where deleting a channel could result in orphaned channel version rules and break the project dashboard
- Fixed a bug with incorrect target counts on the infrastructure dashboard under tenant target sets
- When AutoDeployLastProcessedEventAutoId is null Octopus attempts to process all previous events
- .2 Bug Bash Feeback: Delete Account
New in Octopus Deploy 2018.1.5 (Feb 7, 2018)
- Fixed issue where task creation required higher level permissions than needed
- The built-in repository can now be configured by a user with the ConfigureServer permission instead of requiring the AdministerSystem permission
- All nodes can now be drained at the same time
- Scrollbars are restored after using code editor in fullscreen
New in Octopus Deploy 2018.1.4 (Feb 5, 2018)
- Package Acquisition no longer fails with a Object reference not set error when multiple deployments attempt to access the package cache
- Ensure the artifact list does not reset when the page auto-refreshes
- Octopus.Machine.Hostname system variable is now available on transient target
- Fix a bug where ‘Include Library Variable Sets’ in Project Library Sets page deselects existing Library Variable Sets when opened before Sets are rendered
- Run-on-server script steps can now be run on a Tentacle that runs a under a different user account
- The project dashboard release filter can now be specified by version number in the query string
- Making deployment target discovery UI more intuitive
- Replaced the Start Mode section in the IIS deployment step with bindable checkboxes in the Web Site and Application Pool sections
New in Octopus Deploy 2018.1.3 (Feb 1, 2018)
- Allow configuration of LicenseNotificationMode via configure command
- Fixed issue where tag sets re-order feature is missing from the portal
- When collecting an artifact using New-OctopusArtifact, we now allow other processes to access the file
- Fixed issue where updating Calamari required higher permissions than necessary
- Add Feed button not visible without AdministerSystem permission
- Fix a bug in JsonEscape variable substitution filter
New in Octopus Deploy 2018.1.2 (Feb 1, 2018)
- Database upgrade licence check now detects pre-3.4 versions and is skipped
- Fixed the validation error when a variable is used for authentication method in the IIS step
New in Octopus Deploy 2018.1.1 (Jan 25, 2018)
- Add configuration setting to enable long path support in Calamari.Azure
- Fixes an issue introduced in 2018.1.0 that prevents IIS steps from being saved if the website or app pool name fields use a variable binding expression
New in Octopus Deploy 2018.1.0 (Jan 25, 2018)
- New Features:
- This January release of Octopus Deploy is primarily a security release driven by Octopus Cloud and will also benefit each of our customers running Octopus Deploy on-premises. We highly recommend upgrading.
- You'll also notice our new versioning strategy: what would normally have been Octopus 4.2 is actually 2018.1. Read more about why we changed.
- Improvements:
- When installing Octopus Server and using a Custom Windows Account to run the service, the installation wizard will configure SQL Server correctly so the Custom Windows Account can access the database
- Steps may now be explicitly configured to run before or after package acquisition
- The built-in worker, which executes deployment steps and scripts on the Octopus Server, can now be configured to run using a different, lower-privileged user account
- Fix for infrastructure overview not correctly flowing tag sets from associated tenants
- Import using the Octopus migrator finds the correct deployment process for scripts from similarly named projects
- Existing orphaned channels and releases are removed from the database
- The check to see whether a step template is in use is now much quicker
- Environments, channels and tags now cannot be deleted if they are used by a disabled step in a project's current process
- Package notes are fetched in bulk and in async, meaning a release can be deployed without all notes being downloaded first
- The installed version of Octopus Server is now tracked to help us provide support when data issues occur and is a precursor to raising and event on upgrade
- Breaking Changes:
- Auto machine removal now happens as part of health checks. Minor breaking change API endpoint for machine removal logs is removed and machine removal logs are no longer stored on the Octopus server
- Changes:
- When installing Octopus Server and using a Custom Windows Account to run the service, the installation wizard will configure SQL Server correctly so the Custom Windows Account can access the database
- Auto machine removal now happens as part of health checks. Minor breaking change API endpoint for machine removal logs is removed and machine removal logs are no longer stored on the Octopus server
- Steps may now be explicitly configured to run before or after package acquisition
- The built-in worker, which executes deployment steps and scripts on the Octopus Server, can now be configured to run using a different, lower-privileged user account
- Fix for infrastructure overview not correctly flowing tag sets from associated tenants
- Import using the Octopus migrator finds the correct deployment process for scripts from similarly named projects
- Existing orphaned channels and releases are removed from the database
- The check to see whether a step template is in use is now much quicker
- Environments, channels and tags now cannot be deleted if they are used by a disabled step in a project's current process
- Package notes are fetched in bulk and in async, meaning a release can be deployed without all notes being downloaded first
- The installed version of Octopus Server is now tracked to help us provide support when data issues occur and is a precursor to raising and event on upgrade
New in Octopus Deploy 4.1.10 (Jan 23, 2018)
- The database upgrade now checks whether the licence would be non-compliant after upgrade and aborts the upgrade in order to prevent getting stuck with an expired licence and not being able to deploy
- Digitally signed Octo.exe and Octopus.Clients.dll so that AV respects it more
- Added support for passing password on the commandline to docker login
- Added option to filter by phase name in lifecycles page
- Project and tenant name will now be trimmed during creation and modification
- Now we only test the connection to the master database when creating or deleting the Octopus database, which in turn fixes a problem we introduced in 4.1.0 with upgrading Octopus in certain situations
- PowerShell script parameters with a trailing slash no longer break script execution
- Fix a bug where metadata component in release version is not working with SemVer 2.0 template
- Added the ability to prevent package scripts from being run by specifying the Octopus.Action.Package.RunScripts variable and setting it to false
- We no longer attempt to deploy packages when acquisition fails
- Fix for deployment process screen where viewing email step that references a deleted team
- Don`t show username for external groups in teams area
- Dynamic package feeds now working again with channel rules
- Check for $JAVAHOME now uses [[ -n "${JAVAHOME}" ]] instead of -v to support older versions of bash
New in Octopus Deploy 4.1.9 (Jan 16, 2018)
- Fix a bug where tasks with manual intervention are listed as the queued behind tasks on Task page
- Increased number of possible PowerShell variables in scripts to maximum available
- Corrected the help message explaining what a valid version number looks like
- Increased contrast of form elements and content hierarchy
- Validate that environment and project ids exist when creating or modifying tenants
- Swagger documentation now works if Octopus is running in a virtual directory
- Improved the performance of the project Library Variable Sets page when there are many variable sets
- Fix a bug where task summary does not show on Task page when it is waiting for manual intervention
- Selecting a single date on the Audit page now shows the correct date range
- Prevented the filter panel from opening when you set a quick filter
- Improve performance of tenant variables when large number present
- UI data refresh is now triggered almost immediately after a tab becomes active again if it has been longer than the normal refresh interval; The refresh will also occur if the tab is in the background at a 12th the normal rate
- Fixed a security vulnerability where incorrectly configured user roles and teams would allow members of those teams to escalate their own permissions - Octopus now actively prevents any user from escalating their own effective set of permissions - CVE-2018-5706
New in Octopus Deploy 4.1.8 (Jan 10, 2018)
- Deployment page will now show the explanation for tenanted deployment if the channel has tenant restriction
- Deployment page now has the ability to deploy to all applicable tenants and skip those which already have the release as the current version for the environment
- Fixes for paging parameters in API link collections
- The full value is now displayed for variable template TextBox controls
- Default value on the multiline text variable template no longer overlays
- Make the following scenarios easier
- Deploying to all applicable tenants for the environment
- Skipping those tenants which already have the release as the current version for the environment
- Added warning and error text hints to Checkboxes
- Channel rules testing no longer fails when feedId is a bounded value
- Logo missing on the previous step template version no longer prevents the current version from being saved
- Fix problem in Firefox where selects required two clicks
- Removed empty value warning/info icons from variable editor
New in Octopus Deploy 4.1.7 (Jan 4, 2018)
- Disabling a step no longer deletes the channel version rules for that step
- Fixed package selection in IE 11
- Create step template now renders the selection text
New in Octopus Deploy 4.1.6 (Jan 4, 2018)
- Azure account verification is now deferred until the step runs, which means output variables from earlier steps can be used to resolve the account
- Azure account verification is now deferred until the step runs, so that Cloud Region scoped variables can be used to resolve the account
- Variable filters are now persisted to the query string
- Enable long path support for the Migrator
- Add release notes to Releases page
- Fixed a bug where package versions would give an exception for a package with >2100 versions
- Fix a bug where Release page will crash if the package feed type is resolved from a scoped variable
- Packages with a + can now be deleted via the API
- Package Acquisition no longer fails with a Object reference not set error when multiple deployments attempt to access the package cache
- Fixed potential scoping bypass when referencing Azure accounts (CVE-2018-4862)
New in Octopus Deploy 4.1.5 (Dec 20, 2017)
- Retries during SSH deployments will now re-attempt to establish the connection
- Rolling deployment window size can now be set using bound fields selector
- Healty Check step now shows the correct mandatory roles for execution plan
- Fixes for dashboard width and alignment issues
- Fixed an issue that caused deployments to disconnected SSH targets to run forever
New in Octopus Deploy 4.1.4 (Dec 18, 2017)
- Making variable groups and overflow actions clearer in the variable editor
- Do not collapse the lifecycle in Release page if there is pending interruption
- Machine events now include show/hide details
- Accessing phases containing Environments outside of logged in User's Team Scope not longer throws an exception
- Lifecycle automatic deployment logs can now be found in Configuration > Diagnostics > Auto Deploy Logs
- Lifecycle automatic deployments may now take up to 30 seconds to respond, instead of immediately
- Steps used in Automatic Release Creation can't be disabled anymore
- Show full channel name on releases list and deployment details pages
- Tenant Tag Sets and Tenants in Infrastructure Summary now show the correct deployment target counts
- Release filter doesn't truncate long release numbers any more
- Adding or removing a variable set from a project no longer removes script modules from the project
- Group by Channel in Project Overview screen no longer throws error
- Variables can now be inserted to bound text fields via the list picker
- Users can now see environments that are scoped at the team level
- Missing resource tooltip displays the correct resource id now
- Update to version 3.0.1 of the versioning library
New in Octopus Deploy 4.1.3 (Dec 13, 2017)
- HEAD http requests now return the correct status code instead of 500
- Release progression section now shows "Redeploy" and "Try Again" buttons against each environment
- Sort variable values predictably in the variable editor based on their scope, value and source
- /api/machines and /api/machines/all API endpoints now allows filtering by machine IDs by way of the querstring ids passed in as a comma-separated list of IDs or specified multiple times
- Fixed community step update process
- Only include IIS related information if we're running on Windows when using a custom installation directory and encounter an unauthorized access exception
- Updated versioning library
- Common Variables in v4 no longer shows Variable Sets with no templates
- The output of the show-configuration command now includes license details
- Provide a column specific error message if two projects with different names resolve to the same Slug during migration and failed on the unique constraint check
New in Octopus Deploy 4.1.2 (Dec 12, 2017)
- SSH Targets now support transferring data larger than 2GB
- Fixed a bug introduced in Octopus 3.17.8 that would cause the Octopus Server to crash if the SQL Server connection became unavailable for a period of time
- Better experience when changing variable type to certificate
- Fix for the DateRange component’s width calculations (causing wrapping of day-cells in Firefox)
- User password complexity enforcement in the API is now being applied correctly
- Environment names in v4 dashboard no longer overlap
- Guest user gets created/enabled correctly when the authentication provider is enabled/disabled via the API
- Resolved issue with incorrect password when downloading certificates
- New portal updated to not allow password change for service accounts or the Guest account
New in Octopus Deploy 4.1.1 (Dec 7, 2017)
- The timeout for subscription webhooks can now be configured
- Windows Service deployments now retry starting and stopping services
- Sorting environments will now be reflected immediately on previous screen when you perform save action
- Reducing excessive warnings in variable editor for empty value scenarios
- Any orphaned tenanted deployments will be cleaned up when you upgrade to this version of Octopus Server
- Fixed a bug where the cursor would jump to the end of an input while typing in the variable editor dialog
- The email priority can now be chosen for email steps and email subscriptions
- Fix for test permission exporting failing if the users teams had permissions restricted using empty groups
- Allow users to remove a variable set from a project within the variable set row
- Fixed a race condition that could cause the list of steps to exclude in a deployment to be empty
- Fix tenant chips are not showing correctly in deployment page preview section
- Fix regression where steps that should not be able to be excluded from a deployment could be excluded
New in Octopus Deploy 4.1.0 (Dec 5, 2017)
- Added event group MachineHealthChanged, replacing the event category of the same name
- Task log, package feed and artifacts folders are now shown in the show-configuration command and in the settings UI
- Task log, package feed and artifacts folders are stored as relative to the Home directory when they can be, to make moving the folder structure easier
- Add support for exporting certificates for Java app servers
- Add support for Maven repos as external feeds
- F# and ScriptCS support fixed in Azure script steps
- Fixed an API exception from occurring when a variable name was null
- Fix for audit screen’s default date range not including today
- Fix for maintenance mode banner’s transparency problems
- All SQL Server and Database management is now performed through a single component for consistency
New in Octopus Deploy 4.0.11 (Dec 4, 2017)
- Added the ability to resize columns in the variable editor
- Getting started no longer crashes Octopus if the first release is not on one of the first 5 created projects
- Introduce a delay between connection retries if the connection to the Tentacle is refused as the Tentacle might not be ready to accept connections just yet. Many thanks to @frese for the contribution!
- Updating project overview to include wildcard for finer-scoped EnvironmentView permissions
- Removed unnecessary word-breaking CSS that was causing the design to break in various scenarios
- Update the mouseover popup on scheduled tasks to display the precise scheduled time, and display the scheduled task time in the tasks table
- Added missing option for re-deploying already installed packages
- Fix for showing you an error when you have 2 certificates variables with same name and both are missing from the library
New in Octopus Deploy 4.0.10 (Nov 30, 2017)
- Made it easier to skip steps on the deployment page
- Project overview now shows the executing status for a redeploy
- Fixed various issues with time and date selection for scheduled deployments
- Fix for Tenant edit screen where error would prevent editing connections to Projects
- Reduced the verbosity of auto deploy logs
- Text search on the Users multiselect dropdown no longer crashes due to name being undefined
- Fix to restore the missing Add Channel, Add Trigger, Create Release actions for users who had sufficient but not admin permissions
- Adding null checks to fix multi-selects and the Add Certificate screen
- Fixed a bug where new roles would always be added in lower case
New in Octopus Deploy 4.0.9 (Nov 29, 2017)
- Fixed a bug where filtering by tenant tags in dashboards might give you no results if you were also grouping by a tenant tag
- Fixes for the audit screen to remember filters when paging
- Save button is now enabled by default for steps based on a custom template
- Fixes problem where Markdown lists where not rendered correctly
- Updating task detail cells so they don’t wrap long version numbers
New in Octopus Deploy 4.0.8 (Nov 28, 2017)
- Tenant configuration transform files are now run automatically by naming convention, just like environment configuration transform files
- Migrator skips machine events that relate to missing (deleted) machines
- Fix for dashboard configuration screen where a filter on a project which is no longer visible due to permissions would crash the screen
- Add the ability to set the default failure mode action on a project
- Fix for a crashing active deployment screen for users who could had a set of view only permissions, and could not action interruptions
- Fix users with permissions restricted to a project group not having those permissions on newly created projects
- Multiselect can display thousands of items now (e.g. Projects, Environments, Tenants)
- Active Directory integrated authentication cookie timeout has been increased from 20min to 20days
New in Octopus Deploy 4.0.7 (Nov 27, 2017)
- Improved error handling and message related to incorrect configuration of OpenID Connect Issuer values
- Made the user experience and messaging more consistent for associating tenants with deployment targets, accounts, certificates, steps, and channels
- Code editor in 4.0 now inserts variable at cursor position
- Making loading bars less intrusive and changing to a refresh indicator for task screen refresh intervals
- Checkbox can now be unchecked in Action Template Parameters
- Fixed a bug where you could not edit tenant tags on variable scopes in library variable sets
New in Octopus Deploy 4.0.6 (Nov 23, 2017)
- Fixed a performance problem with very large installations related to the on boarding features we shipped in Octopus 3.12, which would cause high memory use and higher load on the Octopus database
- Output variables are now correctly scoped to Cloud Regions when they are being used for Azure deployments
- The template for the machines/{id}/tasks endpoint now includes the take parameter
- Now we don't strip invalid characters when SSL thumbprint in IIS Step is bound to a variable
- Fixed a bug which stopped you from adding an HTTPS binding for the Octopus Server using a certificate in the WebHosting certificate store via the command-line or using the Octopus Server Manager UI
- Fix disabled steps are able to be added to excluded steps list during deployment which causing server cannot identify the step action
- Fix for UI error preventing the Add a Deployment Target screen from loading, when accessed on a slower connection
- Fix for displaying errors correctly, usually seen while trying to deploy and lacking permission or data for deployment process is flawed
- Fix on test permissions screen where quick successive user changes would result in an error
- Project releases list is now paging data correctly when filtered by channel
New in Octopus Deploy 4.0.5 (Nov 22, 2017)
- Packages on deployment targets can now be found in the package cache when delta compression is disabled
- Fix step templates having some values reset to their defaults when loaded
- We are now displaying all available channels in filter dropdowns and as chips
New in Octopus Deploy 4.0.4 (Nov 21, 2017)
- Viewing releases and creating deployments for Tenanted projects will now correctly factor in permissions
- For all new installations of Octopus Server, the ProjectViewer user role will be granted the ProcessView permission by default
- Fix not handling %2F in URLs
- Fixes disabled deploy release button, it was disabled incorrectly even when users had correct permissions
- Fixed show/hide empty groups button
- Value is now used instead of 1 when Display Value is not defined in Drop down parameter/variable
New in Octopus Deploy 4.0.3 (Nov 21, 2017)
- The Octopus Server and Tentacle certificates are now created more reliably across all of the supported Windows Servers using the SHA256RSA algorithm
- Added a check to Tentacle to only set the window title when the process is run interactively
- If a team references deleted user roles, these will now be highlighted and will need to be removed when making modifications to the team
- IIS binding migration script will now handle old and simpler bindings that may have been migrated as not-enabled
New in Octopus Deploy 4.0.2 (Nov 21, 2017)
- Improvements to guided failure and manual intervention experience
- Removed an error being recorded in auto deploy logs when machines do not match any project triggers
- Tenant, Team, Project, Role, amd Channel chips can now be removed if added to filters, deployments, subscription and notification configurations
- Certificate and Account step template parameters can be now used in steps
New in Octopus Deploy 4.0.1 (Nov 21, 2017)
- Deploy action no longer visible for users who lack the ability on project overview page
- Fix for audit filter buttons overlapping
New in Octopus Deploy 4.0.0 RC (Nov 14, 2017)
- NEW FEATURES:
- Modern UI
- New Variable Editor
- New Infrastructure dashboard
- New Deployment page
- New Configuration API
- BREAKING CHANGES:
- By default Octopus will only attempt to run a step on up to 10 deployment targets at the same time, instead of attempting to run on every matching deployment target simultaneously
- Removed the SynchronizationStatus and IndexingStatus properties returned by the /api/serverstatus/nuget API
- The NancyCookie AuthCookieService.CreateAuthCookie() used by custom authentication providers has been replaced with NancyCookie[] AuthCookieService.CreateAuthCookies()
- The --thumbprint-only option has been removed from the Octopus.Server.exe show-thumbprint command since it is no longer needed
- Octopus.Server.exe regenerate-certificate has been replaced with Octopus.Server.exe new-certificate
- Removed previously deprecated Octopus.Server.exe configure options --masterKey, --storageConnectionString and --webAuthenticationMode.
- Authentication provider information is now treated as a resource and served through it's own API
- The get_octopusvariable bash function now returns an empty string if the variable does not exist
- Removed the /api/letsencryptconfiguration/disable API
- Removed ResourceCollection.IsStale
- Removed unused properties from the BuiltInFeedStats API
- Removed the Page.N entries from the Links list of collection responses and replaced them with some alternatives
- Auto deploy now always re-deploys the most recent successful deployment
- Root document in Octopus API returns now all links
- DETAILED CHANGELOG:
- Octopus UI shouldn't leak memory any more
- The variable editor has been overhauled
- The Wait for packages to be downloaded option only appears for steps ordered before a package step, and the checkbox now retains it's value
- Deploy release page now displays the version previously deployed for each selected environment and tenant
- Added an extra option to the run on option of a step to better differentiate steps that run on the server and those that run on the server on behalf of roles
- It is now easy to create deployments for all tenants which do not currently have the selected version deployed to the selected environment
- Collapsed the tenant tag filter section by default to declutter the UI
- Ctrl-F will now open the browser search function while editing a script
- We have improved the Project Overview when the Project uses multi-tenancy and multiple channels
- Saving and testing of azure accounts shows result more clearly
- The project overview version filter now allows filtering of releases created after the page was loaded
- Resolved issue where selecting both the tenant and a matching tenant-tag resulted in a mis-match
- We have added a gutter to the versions preview that explicitly shows what versions are included or excluded from Channel Version Rules designer
- Clarified what the Run default XML transforms checkbox does when setting up XML Configuration Transforms as part of your deployment process
- We fixed a problem where the introduction to Tenant Tag Sets wasn't displayed properly when hosting the Octopus Server in a virtual directory
- We have fixed a bug where the code editor would not allow you to scroll down to the very bottom in certain circumstances
- We fixed a bug with the Promote button so the options actually make sense for multi-tenanted projects
- We updated the Configuration > License page to show more information relevant to your current license, including usage counts so you know if you are reaching your license limits
- The environments on the Project Overview are now sorted by Lifecycle phase order, then by their order within each phase
- We fixed some noisy JavaScript errors which were appearing in the browser logs
- Updated project sidebar to make it clear when a project is disabled
- Tenant logos now size correctly in Internet Explorer
- The matching tenant count is now shown correctly when reopening the scope of a variable
- Deployment preview now shows which steps will run on a per-tenant basis
- The unsaved changes warning is no longer shown when a step with a run condition is viewed without being edited
- Auto deploy now always re-deploys the most recent successful deployment
- The project search and group filter now always appears on the dashboard
- Breaking Change We removed the Page.N entries from the Links list of collection responses from the REST API and replaced them with some alternatives
- Users can now create projects if they are only members of empty project groups
- StepName property in Release.SelectedPackages has been deprecated (and will be removed in a future release) in favor of the new ActionName property
- Run on Failure steps now show on the task summary tab if it is executed
- The url in the address bar is now formatted correctly when the tenant tag filter is applied on the project overview page,
- We added a new Octopus Server command called ssl-certificate to bind an SSL/TLS certificate to an IP address/port
- Azure errors are now displayed at the top of the page when editing a Cloud Service step
- We changed the audit log so it shows the full date and time instead of a summary like 1 hour ago
- We fixed a bug in the Releases list where the Channel tags would fail to be displayed next to each release
- Breaking Change * Removed unused properties from the BuiltInFeedStats API
- Clarified how the package retention settings work on the dialog
- Added an icon for Unhealthy Azure cloud services
- The target machines for a deployment are now shown per tenant and environment
- Removed ResourceCollection.IsStale
- On deployment creation, tenants that do not match the channel tenant tags can't be selected, and those channel tags are no longer pre-filled on the deployment
- We fixed a series of small bugs that would cause unexpected results when searching for Tenants
- We improved the user experience for editing sensitive variables for tenants
- We fixed several bugs with the Deployment preview and which deployment targets will be included in the deployment
- The machine edit page now makes it clearer that a machine will not be considered for a tenanted deployment if it is not allocated to any tenants
- Improved auto-deploy machine evaluation to prevent machines being missed due to timing issues
- Breaking Change * Removed the /api/letsencryptconfiguration/disable API
- Breaking Change The get_octopusvariable bash function now returns an empty string if the variable does not exist
- The docker steps no longer disappear from the step list when the page is refreshed
- Fixed error that occurs when saving IIS related project steps that were created by earlier versions of Octopus
- The links to Accounts, Users and Proxies now show when you only have the relevant view permissions
- We overhauled the Deploy Release page to make it easier to use when deploying a release to multiple environments or multiple tenants
- The step names now appear correctly in Reorder Steps after removing the all steps from a parent step
- Multiple Exit full screen buttons are no longer shown when editing scripts
- Clarified how to exclude directories when purging a custom installation directory
- We fixed a bug which would incorrectly display the introduction to tenants in the Tenant list screen even if you already have tenants defined
- The variable editor no longer hides unscoped variables when a variable with the same name is scoped to the filter condition
- Breaking Change Authentication provider information is now treated as a resource and served through it's own API
- When cloning a project, you can now choose a different Lifecycle for the cloned project
- Improved Octopus ‘new release’ notifications for expired trial licenses
- Breaking Change Removed previously deprecated Octopus.Server.exe configure options --masterKey, --storageConnectionString and --webAuthenticationMode
- Breaking Change Octopus.Server.exe regenerate-certificate has been replaced with Octopus.Server.exe new-certificate
- Breaking Change The --thumbprint-only option has been removed from the Octopus.Server.exe show-thumbprint command since it is no longer needed
- Breaking Change The NancyCookie AuthCookieService.CreateAuthCookie() used by custom authentication providers has been replaced with NancyCookie[] AuthCookieService.CreateAuthCookies(). This will only impact customers who have written custom authentication providers
- Breaking Change Removed the SynchronizationStatus and IndexingStatus properties returned by the /api/serverstatus/nuget API
- Fixed a bug with the /api/releases/[ReleasesId]/deployments/preview/[EnvironmentId] API which resulted in steps that are scoped to tenants to be returned for un-tenanted deployments
- Breaking Change By default Octopus will only attempt to run a step on up to 10 deployment targets at the same time, instead of attempting to run on every matching deployment target simultaneously
- The package used by a Script Step can now be downloaded directly on the deployment target just like the package used by a Deploy Package Step
- Fixed a bug on the Project Overview screen which would result in an error if you filtered by tenants before filtering by a release
- Snapshotted variables referencing deleted resources will clearly state that the resource is missing from the scope, instead of just not showing it and causing errors downstream
- Root document in Octopus API returns now all links
- Made it easier to deploy a release to multiple environments or multiple tenants using the Octopus UI
New in Octopus Deploy 3.17.14 (Nov 13, 2017)
- Major improvements to migrator memory and speed performance
- Fixed a XSS vulnerability with the Step Template Name
New in Octopus Deploy 3.17.13 (Nov 8, 2017)
- Release Notes are now read from external NuGet feeds if the are returned
- NuGet packages with unsupported metadata elements in its .nuspec file no longer break package transfers
- Return browser security headers when viewing the communications port diagnostic page
- Packages used multiple times in the same project are no longer duplicated in package retention logs
- Server no longer blocks save of the Everyone team if the member list is out of sync with the user table
- Package acquisition will no longer run in parallel with manual intervention
New in Octopus Deploy 3.17.12 (Nov 2, 2017)
- Fixed swagger.json using ints instead of strings for enums
- Added operationId to swagger document for better code gen
- Script module files now gets cleaned up after being imported by the PowerShell bootstrap script
- Variable substitution works now with JSON files that have an array as the root object
- Resolved issue introduced in 3.17.11 where Release Assembled date was being set to the beginning of time when created via octo.exe
New in Octopus Deploy 3.17.11 (Oct 31, 2017)
- Resolved issue where Octopus Manager was not correctly binding 'Include Task Logs' option when migrating 2.6 backups
- Added CommonName certificate variable
- When creating a Release, if Assembled date supplied then use it
- Resolved issue when migrating ServerTask with single MachineId where array was expected
- Fix for Octopus.Server.exe admin command passing email to display name field when creating a user, resulting in blank email
New in Octopus Deploy 3.17.10 (Oct 26, 2017)
- The Audit log will now show no events instead of all events when filtering by a tenant tag that matches no tenants
- Fix for the issue where query string params are missing from all pages besides page 1
- Validated that the arguments for a task created via the API are at least in the right shape
New in Octopus Deploy 3.17.9 (Oct 23, 2017)
- The Octopus Server Manager now starts automatically after the installer completes, just like it used to before we introduced a bug in Octopus 3.17.6
- Tasks that were running or cancelling during a server upgrade are now no longer stuck in cancelling
New in Octopus Deploy 3.17.8 (Oct 19, 2017)
- Variables now allow escaped strings in conditionals in JSON
- Fixed an issue where the current Octopus Server node could not be found during the heartbeat
- OpenID Connect security groups no longer get cleared by the sync task when AD isn't also enabled
- User permissions cache is updated on OpenID Connect login, so groups changes take effect immediately
- Failing a heartbeat now persists demotion to follower
- Fixed a Mutex exception when deploying IIS steps on PowerShell 2.0
- Fixed an exception loading script modules containing certain characters
New in Octopus Deploy 3.17.7 (Oct 18, 2017)
- Further restrict User Invite action to those with TeamEdit and TeamCreate permissions
- When an offline drop target has defined the Encryption password all variables will now be encrypted into the sensitive variables
- The special Guest account is now denied access to certificate private keys, even if that user has been granted the CertificateExportPrivateKey permission
New in Octopus Deploy 3.17.6 (Oct 16, 2017)
- The API now returns a 400 instead of 500 response when an empty body is posted or putted
- Fixed UAC permission elevation in management tool
- Error message when importing a script module that contains a syntax error now points to the actual script module that caused the error
- Fixed issue where adding last node in HA cluster broke the management tool
- Fix Octopus upgrade failure caused by empty value in table Event RelatedDocumentIds column
- Resolved migrator issue where project was prevented from being migrated by deployment step with hidden empty package ID
- Clarified the duplicate variable message to emphasise a user variable is overwriting a step field
- Duplicate variable warning no longer returns a false positive when a variable is scoped to a role
- Fixed an issue that caused unavailable machines to be re-included in a deployment
- Prevented IIS semaphore releasing too many times during high contention deployments
- Added support for down-level login names (domainuser) when performing Tentacle upgrades with a specific account
- OpenID Connect authentication providers correctly update groups from roles on user login
New in Octopus Deploy 3.17.5 (Oct 5, 2017)
- Fixes Missing permission: VariableView error when viewing Library Variable Sets
- New API added for reporting the usages of an account across Machines, Deployment Processes and Releases
New in Octopus Deploy 3.17.4 (Oct 4, 2017)
- The node ping page api/octopusservernodes/ping now returns name, status and version information for the node
- Added a Octopus-Node HTTP header that shows which server served the request
- Added variables for Octopus.Task.QueueTime and Octopus.Task.QueueTimeExpiry
- Scheduled deployments now deploy to the machines available when the deployment is executed (instead of when the deployment is created)
- Fixed a memory issue with LogContext and sensitive variables
- Add retry logic to the send email step to reduce chance of failing a deployment due to sporadic connectivity issues with SMTP server
- Bundled tentacle 3.16.0 that includes --proxy option on Tentacle.exe register-with so a proxy server can be set when registering a tentacle on the command line
- Fixed an error when updating steps after changing a step template variable name
- Package acquisition better accommodates parallel steps
- Guided failure details now display which action and machine failed
- Added the variable Octopus.Action.Output.Manual.Approved to indicate if a manual intervention action was approved
- API returns the correct status codes again for loadbalancer ping (418 when draining) and resource creation (201)
- Fixed an issue collecting machine variables during multi tenant deployments
New in Octopus Deploy 3.17.3 (Oct 3, 2017)
- The node ping page api/octopusservernodes/ping now returns name, status and version information for the node
- Added a Octopus-Node HTTP header that shows which server served the request
- Added variables for Octopus.Task.QueueTime and Octopus.Task.QueueTimeExpiry
- Scheduled deployments now deploy to the machines available when the deployment is executed (instead of when the deployment is created)
- Fixed a memory issue with LogContext and sensitive variables
- Add retry logic to the send email step to reduce chance of failing a deployment due to sporadic connectivity issues with SMTP server
- Fixed an error when updating steps after changing a step template variable name
- Package acquisition better accommodates parallel steps
- Guided failure details now display which action and machine failed
- Added the variable Octopus.Action.Output.Manual.Approved to indicate if a manual intervention action was approved
- API returns the correct status codes again for loadbalancer ping (418 when draining) and resource creation (201)
New in Octopus Deploy 3.17.2 (Sep 21, 2017)
- Empty string may now be provided to override the default value of optional prompted variables
- Server startup migrates users to the new Logins structure
- The API endpoint /api/tasks?running=False now returns the correct results
New in Octopus Deploy 3.17.1 (Sep 14, 2017)
- Fix for permission combination that allowed viewing of variables that user did not have access to
- (https://github.com/OctopusDeploy/Issues/issues/3762) - Fixed Unable to parse sensitive-variables as valid JSON. error in Transfer package step on SSH targets due to decryption password was not being passed correctly
- (https://github.com/OctopusDeploy/Issues/issues/3784) - Sensitive tenant variables that use variable expression can now be changed and set to a custom value
- (https://github.com/OctopusDeploy/Issues/issues/3785) - The system task 'Fail orphaned tasks' has been renamed 'Clean orphaned tasks'
New in Octopus Deploy 3.17.0 (Sep 11, 2017)
- Service account users can be linked to an Active Directory account and will use that account's groups for team membership in Octopus
- External security group synchronization, with authentication providers like Active Directory, has been moved into a scheduled task to fix performance and stability problems
- On startup Octopus will delete obsolete files leftover from old Octopus Server installations
- Maintain certificate friendly-name
- Fixed a bug where the scheduled deployment icon and tooltip in the dashboard would not display
- Added variable OctopusSuppressDuplicateVariableWarning to allow logging duplicate variables warning as verbose
- show-configuration command now includes watchdog status
- Set initial project filter on tenant-project-variables page to alleviate performance issues with large variable count
- Remove 'beta' label from 'Mono not installed' option for SSH targets
- Support for java packages in the built-in package feed
- Deploy Java Archive deployment step
- Tomcat deployment steps
- WildFly/JBoss EAP deployment steps
- Resolved issue with incorrect certificate thumbprint being copied to clipboard
- Fixed a bug where the duplicate variable warning is logged when auto-deploying a release to a machine when redeploy on the trigger is enabled
- Swagger Documentation of live system
- Reduced the frequency of the 'Fail orphaned tasks' task
New in Octopus Deploy 3.16.7 (Sep 1, 2017)
- Fixed an issue causing too much verbose output in the task log
New in Octopus Deploy 3.16.6 (Sep 1, 2017)
- Fixed a problem preventing the Octopus Server from starting successfully which affected customers where their SQL Server Collation is case-sensitive (CS) even if the Database Collation is case-insensitive (CI)
- Adhere to PowerShell common preferences when writing verbose and warning output
- Log warning for duplicate variables between step template and project for steps that run on the server
New in Octopus Deploy 3.16.5 (Aug 29, 2017)
- Teams scoped to empty project groups have access to no projects now
- Fixed a SQL query that was passing too many parameters to SQL, hitting the limit
- API accepts now channel version rules that reference actions by Id or Name
- Fix for error Unexpected character encountered while parsing value when saving deployment process
- All steps types that have roles can both have and be child steps
- Added missing dll required for the watchdog command to the server package
New in Octopus Deploy 3.16.4 (Aug 25, 2017)
- Fixed an issue creating deployments for tenants that was introduced in 3.16.3
New in Octopus Deploy 3.16.3 (Aug 23, 2017)
- Fix binding to ARM template fields that have allowedValues
- Add supported OS versions to app manifest to ensure correct OS is reported in logs
- Validation on required bindings for IIS related deployment steps
- Deployments triggered by auto-deploy environment in lifecycle should be assigned the user that created the release
- Release retention policy now correctly considers all deployments to all tenants when deciding which releases are “still on the dashboard”
- Add a check to the Octopus server startup to ensure that the Octopus database is using a case-insensitive collation
- Data on extra step features will be cleared when feature is disabled
- The SQL Database schema upgrades are now performed within a single transaction, meaning all upgrades will either succeed, or roll-back as a whole returning the database to its last known good state
- Fix for unexpected deployment errors when steps or actions had the same name by now ignoring case when validating that steps and actions have unique names
- Clarified log message when Calamari is not installed on a target
- Add help text to environment selector on Run Step template page to make it clear no environment variables are available
- Resolved issue migrating ExtensionConfiguration
- Provide helpful error message if package file with length of 0 is pushed
- Allow azure script steps to have child steps
New in Octopus Deploy 3.16.2 (Aug 10, 2017)
- The server side cross check of downloaded packages versions now uses semantic version rules instead of a strict string comparison
- Octopus now ensures only a single database schema upgrade is running at any given time, making Octopus HA upgrades more robust
- Tentacle retention policy now applies to packages used in Run a Script steps
- The task page now provides better insights into why a task hasn't started yet
New in Octopus Deploy 3.16.1 (Aug 10, 2017)
- Fall back to SHA1 certificates on Windows 2008 32 bit if SHA256 is not supported
- Duplicate variable message is now logged as a warning to make it more discoverable for customers
- Polling tentacles now log errors in the main connection retry loop
- Include guest account enabled state in anonymous metrics reporting
New in Octopus Deploy 3.16.0 (Aug 2, 2017)
- New Features:
- Octopus 3.16 removes the requirement to install Mono when deploying to Linux and MacOS targets. It does this by using a self-contained .NET Core build of Calamari.
- Improvements:
- Support for Okta as an authentication provider
- ScriptCS has been upgraded to version 0.17.1
- Resolved issue introduced by Let's Encrypt API change
- Breaking Changes:
- The latest version of ScriptCS has introduced some breaking changes so it's important to review their release notes before upgrading. This only affects projects with script steps written using C#, which are powered by ScriptCS under the hood.
- Changes:
- Improved handling of key retrieval and caching in the OpenID Connect provider
- Tentacle installer download links on Create deployment target for Listening or Polling Tentacles now point to the correct URL
- Allow the use of Virtual Directories when configuring Let's Encrypt
- Ensure advanced settings are expanded by default on Let's Encrypt dialog when previous values exist
- Minor Breaking Change Updated ScriptCS to 17.1, which contains some minor breaking changes
- Changed the ServerTask table to refer to OctopusServerNode by Id instead of Name
- Fixed a potential memory leak when making heavy use of subscriptions under certain circumstances
- Redesigned SQL Indexes for ServerTask to improve performance of everything that queries tasks
- Ensure 'restart required' message is shown when disabling web sockets
- Allow using self-contained .NET Calamari for SSH Targets (this means no Mono dependency)
- Added support for Okta as an authentication provider
- Resolved issue that caused the WebUI to become unresponsive when deploying to 100+ tentacles
- Fixed Let's Encrypt support after a breaking change in the Let's Encrypt API
New in Octopus Deploy 3.15.8 (Jul 24, 2017)
- Add audit events when a package is deleted from the built-in repository and keep 1 weeks worth of package repository retention logs
- The --console switch is no longer required by scripts automating the Octopus or Tentacle command-line interface, but is still supported for starting either service interactively if so desired
- Fixed a bug that would sometimes result in a null reference exception when setting a password in a step
- Life Cycle listing in the Library will now be available to those with permission LifecycleView, it used to require LifecycleEdit
- Fixed a bug which was preventing the task list from being filtered by Server Node after upgrading to Octopus 3.15.x
- Corrected Azure account variables masking in log
- Add an audit event when the server retention policy deletes a release
- Ensure 'restart required' message is shown for all relevant configure commands
- Improve error message when Docker feed test cant connect successfully
New in Octopus Deploy 3.15.7 (Jul 24, 2017)
- You can now filter audit events for specific tenants
- Fixed a problem which could cause a SQL Connection leak when synchronizing Active Directory groups under certain circumstances
- Fixed a problem where certificate variables were not being scoped by tenant tags
- Default value of sensitive project variable templates is now preserved between updates
- Using our production certificate when signing the Tentacle files in TeamCity
- Fix for ids filtering in projects, tenants and library-variable-sets API
New in Octopus Deploy 3.15.6 (Jul 17, 2017)
- Avoid requirement to load project information on tenant project variables screen
- Project Variable Templates are now also cloned along with the other project properties and data
- Adding ‘ids’ filtering to the API (added to CustomQuery and Index responders)
- Updated Let's Encrypt integration to support specific IP certificate bindings
- Default value of sensitive variable templates is now preserved between updates
- Handle Let's Encrypt http challenge when ForceSSL is enabled and https is configured on a custom port
- Fixed a problem where the project settings page took a long time to load on large installations after installing any Octopus versions between 3.14.15926 and 3.15.5
- Update the ForceSSL redirection to redirect from HTTP -> HTTPS before redirecting the the /app endpoint
New in Octopus Deploy 3.15.5 (Jul 13, 2017)
- Project release filter now searches all versions
- Lifecycle must have at least one phase that is not optional
- Both API and UI for Library Variable Set enforce now the same scoping rules
- Fixed a problem causing intermittent System.AccessViolationException errors when using the built-in Octopus Certificate features
- The permissions for cancelling a task have been simplified, so now you only require the TaskCancel permission in order to cancel a running task
New in Octopus Deploy 3.15.4 (Jul 12, 2017)
- Fixed missing Microsoft.Threading.Tasks error when setting up or health checking Azure steps
- Prevent a potential security vulnerability in the Built-In package repository by validating supplied PackageId’s according to the same rules as NuGet
New in Octopus Deploy 3.15.3 (Jul 10, 2017)
- First steps in a deployment process can now have run conditions
- Corrected "learn more" link for the Let's Encrypt integration
- Improved validation messages around Let's Encrypt bindings and no longer prevent configuration when using reverse proxy
New in Octopus Deploy 3.15.2 (Jul 7, 2017)
- Windows Service step no longer double escapes additional parameters
New in Octopus Deploy 3.15.1 (Jul 6, 2017)
- Backslash character in windows service password are now escaped
- Quotes around window service exe path were missing
- Start-Service was treating [ as a special character and was unable to start the service
- Passwords with $ characters in Windows Service deployments are now escaped properly
- Corrected VariableEdit permission description
- Fix JS bug introduced in 3.15.0 causing portal loading issues in IE11
- Resolved spurious 'No enabled deployment targets' warning on tenanted deployment previews
New in Octopus Deploy 3.15.0 (Jul 5, 2017)
- New Features:
- This month, we bring you some much requested improvements to multi-tenant deployments, as well as Octopus Server integration with Let's Encrypt and more!
- The way machines, accounts and certificates participate in tenanted-deployments can now be explicitly specified. This includes allowing un-tenanted projects to be deployed to tenanted machines. This has been a long-standing gripe with tenanted deployments which we're very happy to resolve.
- Our new integration with Let's Encrypt means you can setup an SSL certificate for your Octopus Portal and it will automatically be renewed when it expires. No need to worry about buying a certificate or manually reconfiguring your server.
- Improvements:
- If you're automating the setup of the Octopus Server or Tentacles, you'll be happy to hear that we've put some solid effort into cleaning up our console logging. It will now be much easier to get the information you need without having to do string parsing.
- Granting Edit permissions now automatically assigns View permissions. It always helps to be able to see what you're changing.
- Breaking Changes:
- Console output has changed (for the better!), so we advise testing any automation before upgrading to this version.
- Octopus.Client version 4.19.0 contains API changes corresponding with the multi-tenant deployment participation change, a minor breaking change for anyone using the MultiTenantDeploymentMode on Project resources via the client.
- Upgrading:
- This release contains a post-install data fix that may take some time (depending on the size of your Events table), so please ensure you allow time for this to complete. If you are running the watchdog service, please ensure this is stopped during the upgrade.
- As always, read the upgrade guide for more details on upgrading to Octopus 3.15.
- CHANGES:
- Enable untenanted projects to be deployed to tenanted deployment targets
- Acquire package and retention policy steps now show step number and name in variables
- Unscoped variables deleted when user doesn't have VariableViewUnscoped permission
- Added support for managing the Portal SSL certificate using Let’s Encrypt
- Resolved issue with Azure Service-Principal accounts not being available for selection as value of tenant variable template
- The command-line interface for Octopus and Tentacle will now warn you if a service restart is required after certain configuration changes
- Clean up corrupt entries in the events table left behind by a previously resolved issue
- Migrator now maps TenantId when migrating Deployments
- Improved command-line interface for Octopus and Tentacle
- Prevent automatic Tentacle upgrades from restarting the host machine
- Bugfix: Release filtered dashboard does not show environments that deployment can be progressed to
- Certificates with long IDs can now be assigned as Tenant Variable values without throwing a StringTooLongException
New in Octopus Deploy 3.14.15926 (Jun 30, 2017)
- Advanced project settings are shown by default after a users first successful deployment
- Added Support to override Azure Service Management (Storage) Endpoint Suffix
- Tentacle will now ignore partially downloaded packages that are a result of network failure or deployment cancellation
- Improved UI to make it clearer that steps run ‘on behalf’ of roles are optional
- Cloud Service Storage account list handles Azure service management endpoint override correctly
- Resolved an exception starting Octopus Server when the current node name contains certain characters
New in Octopus Deploy 3.14.1592 (Jun 28, 2017)
- Tasks running on an HA node that fails to check in will be marked as failed
- Offline drops now detect if a sensitive variables file is available, and prompts for the password automatically
- Fixed a problem that would show an annoying error message when trying to upgrade from Octopus 2.6.5 to Octopus 3.14.x
- Fixed an issue introduced in 3.14.159 that caused prompted variable not to be set at deployment time
New in Octopus Deploy 3.14.159 (Jun 27, 2017)
- Improved the performance of the update variables process at the end of each deployment step
- Azure resource group deployment names are unique and less than 64 characters long
- Task log headers now indicate whether an action was run on behalf of a targer instead of on the target itself
- Most list api endpoints now support a take query parameter to control the page size, allowing more than 30 results to be returned at a time
- Azure Web App step correctly reloads the site list when editing
- Show additional configuration values on the Configuration -> Nodes -> Configuration Settings page
- User invitations can be used only once now
- Step Update works now when the update is performed while the template is being modified
New in Octopus Deploy 3.14.15 (Jun 21, 2017)
- Running a step template now populates its default parameter values
- Cloned projects now include the correct lifecycle
- OpenID Connect authentication provider now supports IPs that only use RSA keys
- A new HA node leader will be elected when there are only follower nodes
- Recover from hung state when IIS based deployments are cancelled
- All error messages are now written to stderr even if the --noconsolelogging switch is used with Octopus.Server.exe or Tentacle.exe
- Improved the master key validation we apply when connecting an Octopus Server instance to an existing database
- Octopus Server, as part of upgrading, now detects if the SQL Database schema upgrade can be performed before attempting them
- Fixed a problem where an audit event could be formatted incorrectly, causing the audit query to break
- Clarified that Roles group Permissions
- Add commands to create and backup certificates used by the Server for Tentacle communication
- Azure Cloud Service deployments will now set OctopusAzureCloudServiceDeploymentID and OctopusAzureCloudServiceDeploymentUrl output variables when the deployment is completed.
New in Octopus Deploy 3.14.1 (Jun 12, 2017)
- Improvements:
- We've updated our ‘Deploy to IIS’ step to add support to control how your web sites and app pools are started after a successful. deployment. This is a great addition to one of most popular steps.
- Octopus is now generating all its certificates using using SHA256, instead of the older SHA1. We blogged about this previously when the SHAttered security vulnerability was announced and we've updated Octopus as promised.
- Octopus Server and Tentacle will now be released on a separate cadence. Tentacle will now be versioned/released independently and it will now come with its own release notes. This is a minor point but it should make it easier to upgrade Octopus going forward!
- Octopus Server database schema updates are now more transparent. Now when you upgrade Octopus to 3.14.0, or newer, the database schema upgrade will be performed immediately after the software upgrade, clearly showing the progress of the schema changes.
- We've added some new database indexes and we greatly reduced the memory usage on all HTTP requests. This means Octopus can spend less time cleaning up after itself, and more time being productive on your behalf.
New in Octopus Deploy 3.13.10 (Jun 7, 2017)
- New Features:
- We are excited to announce that Octopus now includes first-class support for Deploying Azure Service Fabric applications.
- New deployment steps include:
- Deploying a Service Fabric App (learn more)
- Running a Service Fabric SDK PowerShell Script (learn more)
- Improvements:
- You can now enable HTTP Strict Transport Security (HSTS)
- You can now configure optional lifecycle phases
- We have improved browser caching of expensive operations like loading the dashboard
- The message on the deployment overview can now be customised, refer to failing a script with a message
- You can now edit the state of a task from the task screen by providing the new task state and the reason for the change.
- You can now configure channel-indexed version templates so you can use a consistent version scheme across channels
New in Octopus Deploy 3.13.9 (Jun 2, 2017)
- New deployment steps include:
- Deploying a Service Fabric App (learn more)
- Running a Service Fabric SDK PowerShell Script (learn more)
- Improvements:
- You can now enable HTTP Strict Transport Security (HSTS)
- You can now configure optional lifecycle phases
- We have improved browser caching of expensive operations like loading the dashboard
- The message on the deployment overview can now be customised, refer to failing a script with a message
- You can now edit the state of a task from the task screen by providing the new task state and the reason for the change.
- You can now configure channel-indexed version templates so you can use a consistent version scheme across channels
- Breaking Changes:
- Please note there is a minor breaking change in this release around the show-configuration command. This will only affect customers who use the show-configuration command for things like automating Octopus Server installation and configuration.
- Changes in 3.13.9:
- Improved Lifecycle API validation to ensure environments are valid
- Only child steps can be moved into rolling deployments. Azure Resource Group steps can now be child steps as well
- Azure Resource Group deployments now generate unique deployment names
- Bugfix allowing blocked deployments to continue phase progression
- Fixed error 65532 when running Tentacle upgrades on PowerShell v2
- You can now upgrade the database schema using the Octopus.Server.exe database --upgrade command
- Fixed orphaned tenanted deployment integrity check - now it ignores un-tenanted deployments from the test
- Improved performance of writing task logs by about 10%
- Fixed a JavaScript problem with the Azure Service Fabric step's hamburger menu
- Improved performance for each HTTP request by reducing memory allocations
New in Octopus Deploy 3.13.8 (May 29, 2017)
- 2943 - Allow some files to be retained when purging a custom installation directory
- 3048 - Selecting release on multi-tenant project dashboard will now update the dashboard
- 3101 - Tenanted deployments are now cascade deleted when the tenant is deleted
- 3210 - Errors when applying retention-policy on deployments targets now treated as warnings, and will not fail the deployment
- 3249 - Resolved issues with filtering tenants list in portal
- 3347 - Log relevant error message if trying to import certificate into Root store for user
- 3401 - The audit log can now be filtered by document type
- 3402 - Improved description of the permissions table on the permission test page
- 3479 - Added a link to help for dynamic package feeds
- 3496 - We now explicitly mention that IIS step supports Websites, Web Applications and Virtual Directories
- 3504 - Add the ability to export the audit log as a CSV file
- 3508 - 'Send an Email' step summary shows now only teams selected by the user
- 3510 - We now explicitly tell the user that release deletion will remove deployments from all dashboards
- 3514 - Fix Lifecycle required to progress details not saving correctly
- 3516 - Made it easier to see the options to upload packages to the built-in package repository
- 3528 - Ensuring a channel belongs to a project upon release creation is now case insensitive
New in Octopus Deploy 3.13.7 (May 22, 2017)
- We are excited to announce that Octopus now includes first-class support for Deploying Azure Service Fabric applications.
- New deployment steps include:
- Deploying a Service Fabric App (learn more)
- Running a Service Fabric SDK PowerShell Script (learn more)
- Improvements:
- You can now enable HTTP Strict Transport Security (HSTS)
- You can now configure optional lifecycle phases
- We have improved browser caching of expensive operations like loading the dashboard
- The message on the deployment overview can now be customised, refer to failing a script with a message
- You can now edit the state of a task from the task screen by providing the new task state and the reason for the change.
- You can now configure channel-indexed version templates so you can use a consistent version scheme across channels
- Breaking Changes:
- Please note there is a minor breaking change in this release around the show-configuration command. This will only affect customers who use the show-configuration command for things like automating Octopus Server installation and configuration.
- Octopus.Storage.NodeName has been corrected to be Octopus.Server.NodeName.
- Upgrading:
- Read the upgrade guide for more details on upgrading from your current version to Octopus 3.13.
- Changes in 3.13.7:
- Step template can't be deleted now if any of its versions are in use
- Resolved slow deployment times introduced in 3.12.8, caused by Calamari checking certificate-revocation-lists for signed assemblies
New in Octopus Deploy 3.13.6 (May 18, 2017)
- Display help text for project variable template when viewing tenant variables
- Fix syntax highlighting for variable value editor
New in Octopus Deploy 3.13.5 (May 17, 2017)
- New Features:
- We are excited to announce that Octopus now includes first-class support for Deploying Azure Service Fabric applications.
- New deployment steps include:
- Deploying a Service Fabric App (learn more)
- Running a Service Fabric SDK PowerShell Script (learn more)
- You can also read our guide on Continuous Integration for Service Fabric.
- Improvements:
- You can now enable HTTP Strict Transport Security (HSTS)
- You can now configure optional lifecycle phases
- We have improved browser caching of expensive operations like loading the dashboard
- The message on the deployment overview can now be customised, refer to failing a script with a message
- You can now edit the state of a task from the task screen by providing the new task state and the reason for the change.
- You can now configure channel-indexed version templates so you can use a consistent version scheme across channels
- Breaking Changes:
- Please note there is a minor breaking change in this release around the show-configuration command. This will only affect customers who use the show-configuration command for things like automating Octopus Server installation and configuration.
- Octopus.Storage.NodeName has been corrected to be Octopus.Server.NodeName.
- Changes:
- Resolved error when deploying old versions of step templates introduced in 3.13.4
- Editing ‘environment scoped’ variables in a variable set no longer needs EnvironmentEdit permission
- Enabled certificate parameters to step templates
- Removed broken 'Create variable' link from certificate step template parameters
- Only remove SSL certitificate from the website that the HTTPS binding is removed from
- Auto deploy will no longer attempt deployment to machines without roles relevant to the deployment
- Error reason will be shown when license signature could not be verified
- Health checks now log any machines that could not be checked because of tenant permission restrictions
- Variables with colons can now be used as Web Site and App Pool names
- will no longer be repeatedly written to deployment logs for IIS deployments
- Fixed typo in the scheduled task tip
- Fixed a performance problem where both an unbounded and paginated SQL query were issued for some requests
- Fixed a Service Fabric upgrade bug where we were using an incorrect argument
New in Octopus Deploy 3.13.3 (May 11, 2017)
- New deployment steps include:
- Deploying a Service Fabric App
- Running a Service Fabric SDK PowerShell Script
- You can also read our guide on Continuous Integration for Service Fabric.
- Improvements:
- You can now enable HTTP Strict Transport Security (HSTS)
- You can now configure optional lifecycle phases
- We have improved browser caching of expensive operations like loading the dashboard
- The message on the deployment overview can now be customised, refer to failing a script with a message
- You can now edit the state of a task from the task screen by providing the new task state and the reason for the change.
- You can now configure channel-indexed version templates so you can use a consistent version scheme across channels
- Breaking Changes:
- Please note there is a minor breaking change in this release around the show-configuration command. This will only affect customers who use the show-configuration command for things like automating Octopus Server installation and configuration.
New in Octopus Deploy 3.13.2 (May 9, 2017)
- Existing action data is displayed correctly and community step updates are versioned now
- Tweaks to Tentacle upgrade process to diagnose error 65532
- Manual action template merge updates now all relevant properties
New in Octopus Deploy 3.13.1 (May 8, 2017)
- Fixed a race condition that caused re-packing of deployments to fail (eg Azure deployments)
- Improved validation around IIS deployment step variables
- Package transfers will no longer appear to be in progress if a task fails or is canceled
- Package transfers from Octopus to Tentacle no longer retry when the task is canceled
- Tentacle can now bypass the proxy when registering as a polling tentacle
New in Octopus Deploy 3.13.0 (May 3, 2017)
- Added ability to override a task status
- Adding verbose logging around Azure module logs
- Deploy a cluster application for Service Fabric
- Run adhoc PowerShell scripts for Service Fabric
- Support Client Certificates as a security mode for Service Fabric
- Support Azure AD as a security mode for Service Fabric
- Automated application versioning for Service Fabric
- On-prem support added for Service Fabric
- Improve performance of dashboard by leveraging browser caching
- Avoid refreshing dashboard page if window is not visible
- Reference versions from other channels in Release Version Template
- Add missing property Octopus.Communications.WebSocketPrefix to output of show-configuration command
- Breaking change: Corrected Octopus.Storage.NodeName property in show-configuration output to be Octopus.Server.NodeName
- Regression in license limiting for special licenses
- IE9 and IE10 users are warned that their browsers won't be supported in Octopus 4
New in Octopus Deploy 3.12.9 (May 2, 2017)
- Excluding a machine from a deployment will no longer exclude that machine from a subsequent auto-deploy of the same deployment
- Audit messages now record extra details (differences) when documents are created and deleted
- Fix not being able to add more than one environment to a machine at a time
- Tenant count is now displayed correctly on the main dashboard
New in Octopus Deploy 3.12.8 (Apr 27, 2017)
- The message on the deployment overview can now be customised, refer to failing a script with a message
- Prevented missing indexed variable from causing a stack overflow
- Support Optional Lifecycles
- Sign Calamari.exe and Calamari.Azure.exe
- Fixed a race condition in sensitive variable masking that caused the process to crash
New in Octopus Deploy 3.12.7 (Apr 26, 2017)
- Improve Markdown support awareness for release notes
- Links in subscription event payloads are now fully qualified relative paths into the Octopus web UI. If you have been using the previous format /r/ResourceID and are parsing them, you no longer need to do this parsing
- Correct versions are now displayed on the main dashboard
- Clearly warn users if deploying to an environment that has a release waiting for manual intervention
- Fix users being able to add an environment to a machine when their Machine Edit permission is not scoped to that environment
- Improve the error message that is logged if the package re-index fails to read a package
- Fixed add child step button
- Packages with the same id but different casing will now be sorted correctly
- Folders with Junctions can now be deleted again
- Fixed issue downloading nuget packages with metadata versions from v3 feeds
New in Octopus Deploy 3.12.6 (Apr 20, 2017)
- New Features:
- User Onboarding
- Global Step Update
- PowerShell debugging support
- Improvements:
- Performance improvements
- Certificate-Chain support
- Improved license notifications
- Upgrading:
- Read the upgrade guide for more details on upgrading from your current version to Octopus 3.12.
- Changes:
- Deploying a release to an already deployed to an Environment skips Lifecycle validation
- Support cleaning up long file paths in Tentacle retention policies on Windows
- License status checks do not generate diagnostic warnings now
- Allow case insensitive value when setting WebAuthenticationMode
- Fixed timing issues when collecting logs from Tentacle upgrade
New in Octopus Deploy 3.12.5 (Apr 18, 2017)
- Fix issue with modifying the everyone team when user had been deleted
- Disable 'move into' step menu item if there are no valid step targets
- Improve warning messages when close to or exceeding license limit
- Updates to subscriptions to improve logging, adding additional batch parameters and moving the processing to a task to improve the load profile in HA environments
- Updated the built-in packages repository page to re-add common ways to push packages
- Fix for ARM template steps to consider ‘Canceled’ state
- fix for octo.exe list-deployments failing in non-tenanted installations
- Improved the performance of the deployment manifest clean-up process
- Added more diagnostic information to the System Report
- Resolved possible database conflict when updating machines
New in Octopus Deploy 3.12.4 (Apr 11, 2017)
- New Features:
- User Onboarding
- Global Step Update
- PowerShell debugging support
- Improvements:
- Performance improvements
- Certificate-Chain support
- Improved license notifications
- Upgrading:
- Read the upgrade guide for more details on upgrading from your current version to Octopus 3.12.
- CHANGES:
- 3110 - Show projects that have channels using a lifecycle in the sidebar when viewing a lifecycle
- 3143 - Changes to tenant variables are now audited correctly
- 3253 - Improved the Physical Path section of the Deploy an IIS Web Site step to make it clearer what it does and what it does not configure
- 3392 - Action editor now always display properties correctly
- 3398 - Improved performance of every HTTP request by making auditing more efficient
New in Octopus Deploy 3.12.2 (Apr 10, 2017)
- New Features:
- User Onboarding
- Global Step Update
- PowerShell debugging support
- Improvements:
- Performance improvements
- Certificate-Chain support
- Improved license notifications
- Upgrading:
- Read the upgrade guide for more details on upgrading from your current version to Octopus 3.12.
- Changes in 3.12.2
- 2290 - Add some logging when an artifact upload is requested to help track down problems
- 2491 - Log a warning when an artifact file cannot be uploaded due to file locking rather than freezing the deployment
- 2841 - New flag on project to support concurrent active channel deployments
- 3163 - Fix for de-register tentacle command, tentacle configuration now updates
- 3304 - Fixing the re-deploy bug in Project Triggers / auto-deploy
- 3338 - Wrap long variable names in the "missing variable values" popup
- 3361 - Improved error message shown when locked files are encountered during package extraction
- 3369 - Aborting manual intervention now requires confirmation
- 3373 - Collecting Tentacle upgrade logs after a failed upgrade is now more resilient
- 3382 - Health check results are now recorded as each machine's health is determined rather than at the end of the health check
- 3385 - Resolved certificate issue Signer 1.3.14.3.2.29 not recognised
- 3388 - Tasks now no longer get stuck in running or cancellation state if there is a intermittent database connection problem
- 3390 - Log the projects and releases that prevent packages from being cleaned up from the built-in package repository
- 3394 - Interruptions endpoint no longer returns interruptions for cancelled tasks when returning pending interruptions
New in Octopus Deploy 3.12.1 (Apr 7, 2017)
- New Features:
- User Onboarding
- Global Step Update
- PowerShell debugging support
- Improvements:
- Performance improvements
- Certificate-Chain support
- Improved license notifications
- Upgrading:
- Read the upgrade guide for more details on upgrading from your current version to Octopus 3.12.
- Changes in 3.12.1:
- Ensure the PackageFilePath variable contains a canonical path rather than including $HOME on SSH targets
- A brief view of the task log can now be viewed again after selecting verbose
- Task logs will show duration of tasks as they run, and total run time when finished
- Server Manager and Admin command now enforce UPN format for AD admin account usernames
- Octopus.Action.Package.InstallationDirectoryPath is now available in the variable menu
- Ensure wildcard configuration transform targets like *.dev.config => *.config match files in a case-insensitive manner on Windows
- Updated namespace reservation error information in the log to correctly reflect the Listen Prefixes
- ShowScript Module link if user has VariableView permission with any scoping
- Resolved error when disabled HTTPS binding uses unavailable certificate
- Updating validation around the issuer field for OpenID login providers
- 'Process' menu item doesn't cover the code editor when editor is in full screen mode
New in Octopus Deploy 3.12.0 (Apr 4, 2017)
- New Features:
- User Onboarding
- Global Step Update
- PowerShell debugging support
- Improvements:
- Performance improvements
- Certificate-Chain support
- Improved license notifications
- Changes:
- Getting started with Octopus is now even easier
- Step properties are displayed now when the step is not using the latest version of a step template
- Empty property value doesn't get reset to default parameter value when a step template change is applied to an existing step
- Step template update can be applied to all steps in all projects
- Improve license expiry visual feedback within Octopus
- Support for PFX files containing a certificate-chain when uploading certificates
- Major performance improvements for large deployments, and general API, CPU, and RAM usage improvements
- Added a new command list-instances to Octopus.Server.exe and Tentacle.exe to list all installed instances
- The Octopus Web Portal now sends its version in a custom header
- Add support for debugging PowerShell step templates and scripts
New in Octopus Deploy 3.11.18 (Apr 3, 2017)
- Improvements around parallel IIS deployments that could hang
- Improved performance of each HTTP request by caching certain web portal configuration values instead of reloading them from the SQL Database on each request
- Import Certificate Step implemented for Offline Package Drop Targets
- Fix javascript error when adding a new Deploy Azure Web App step
- Fix crash on new project screen when no value provided for project name
- Limit the visibility of deployments to a machine to those who have appropriate environment/project permissions
- Dont reset machine policy when re-registering a machine
- Fixed issue where deployment cancelled audit logs were not visible for users with scoped permissions
- Added missing Channels.FindAll API to the Server
- Fixed issue where deployment overview and logs showed null as step names
- Extract files in the /package folder of nupkg files to match pre-3.4 behavior. The /package/services/metadata folder is still ignored
- Fixed a performance issue with the maintenance mode check, in turn removing some load from the SQL Database for every HTTP request
- Docker steps can be now used as child steps
- Fix bug causing new Docker Stop step to default step filter to an empty step
- Improved performance of building TaskLog tree nodes by up to 10X for large log files
New in Octopus Deploy 3.11.16 (Mar 29, 2017)
- octo.exe pack command has verbose logging support showing files added, can also be selected in VSTS extension
- Do not mark a variable for deletion when using the Delete button while editing the variable
- Add Extended API option to NuGet external feeds, which improves Create Release performance on supported feeds
- Improved performance whenever Octopus starts or uses a SQL Transaction by using a single ILog instance, instead of creating a new one each time
- Tentacle upgrade no longer raises a NullReferenceException while waiting for the tentacle to start
New in Octopus Deploy 3.11.15 (Mar 27, 2017)
- Ensure missing linked items are shown in UI, so they can be manually removed
- Fixed an issue where disabled package steps would break channel version rule editing and octo.exe import
- Added health check warnings and errors to the details of health check audit events
- Private-key permissions will not be cleared when importing existing certificate
- Fixed an issue with case sensitive database collation preventing the task queue from popping
- Fix for steps not showing up when re-deploying with previously skipped steps
- Fixed sensitive variables for SSH targets
New in Octopus Deploy 3.11.14 (Mar 23, 2017)
- Only show Delete option in variable context menu if the variable is editable
- Fix NuGet credentials not working after a 307 redirect when downloading packages directly to the Tentacle
- Fixed JSON variable substitution where decimal values would come through as zero
New in Octopus Deploy 3.11.13 (Mar 21, 2017)
- Trim the result of a step run condition expression before checking for truthiness so that " False" is false
- When uploading certificates in a PFX file, bag attributes (e.g. Microsoft CSP) are now maintained
- Automatic Tentacle upgrades from 3.1.7-3.3.22 no longer fail to restart the Tentacle service
- Fix delta compression failing sometimes when there are multiple deployed versions of a package with the same version but different contents
- Fixed issue where the machine deployments tab was not visible for some users
- Fixed issue where feature toggle buttons appeared to change after page load
- Tasks interrupted when the Octopus Server goes offline are now Failed instead of TimedOut
- Provide --clean parameter on Migrator export command
- Beta support for polling tentacles connecting over HTTPS (WebSockets)
- Correctly pass external nuget feed passwords when downloading packages directly to Tentacles
- Improved logging for situations where the SQL Connection Pool is under heavy load
- Substitute variable feature no longer errors if a wildcard path returns a directory
- Improved logging for the work done at the end of each deployment action
- Removed globbing support for now as it broke backwards compatibility and replaced it with extended wilcards (*, **)
- Improved the performance of the variable manifest update at the end of each step
- Improved logging when waiting to update the deployment plan
New in Octopus Deploy 3.11.12 (Mar 20, 2017)
- Tentacle upgrades prevent deployments and health checks from occuring to the same environment
- Fixed a problem which was causing Octopus Server nodes to appear offline for long periods of time in large installations
- The server now attempts to recover from I/O errors when writing task logs instead of continuing to run the task very slowly
- The process no longer crashes if a control message in the deployment output is malformed
- The data migrator now shows a clearer error message when the password provided to the import command is incorrect
- Fixed redirect path on IE11 causing authentication login errors
- From now on the version of Octopus.Client.dll which is bundled with Octopus Server will be the same version the Octopus Server API was tested with
- Offline drop targets that are Unhealthy now show up on the Environments dashboard
New in Octopus Deploy 3.11.11 (Mar 15, 2017)
- Package release notes are now rendered consistently in the UI and the /api/feeds/{feedid}/packages/notes API endpoint returns Markdown instead of HTML
- No longer log at Error level when package diffing fails in a way we can recover from
- Azure steps no longer hold SQL Connections open for the entire step, to avoid SQL Azure connection issues
- Dont show step scoping drop-down for variable set variables
- Project settings page no longer throws JavaScript error when showing details of an untenanted project
- Reduce the logging level for API 404s from Warning to Information
- Fixed issue where project group restrictions were not being merged correctly for users in multiple teams
- Permissions export now includes Tenant and ProjectGroup restrictions
- No longer log connection errors when disabled polling Tentacles connect
- Azure steps can be run concurrently once again (broken in 3.11.10)
New in Octopus Deploy 3.11.10 (Mar 13, 2017)
- Improve the error message when attempting to register a Tentacle in an environment that cannot be found
- Provide ability to set account for running Tentacle updates
- Prevent Halibut from generating enormous Tentacle logs
- Resolved API warning message for non-admin users when Octopus server does an upgrade check
- Support Tentacle register-with to supply custom listening port to server
New in Octopus Deploy 3.11.9 (Mar 13, 2017)
- Ensure that Azure accounts are scoped to the Environment when the Azure step is not scoped to a role
- Fixed upgrade bug that caused a failure when Auto Release Creation was missing a channel
New in Octopus Deploy 3.11.8 (Mar 13, 2017)
- 2633 - Calamari package creation for Linux now uses the Home folder instead of the Program Files folder
- 2937 - The Tentacle retention process now logs which packages and directories are kept
- 3137 - Fixed bug preventing project cloning when channel missing on auto release creation strategy
- 3188 - The Tentacle.exe server-comms command now supports multiple listening/polling configurations
- 3239 - Resolved issue using variable for user name in private-key access-rules in Import Certificate steps
- 3241 - Tentacle upgrade no longer hangs if the exit code file is not written
- 3243 - Better cancellation support during Tentacle upgrade
- 3245 - Project names on the dashboard now wrap at word-breaks instead of mid-word
- 3248 - Display correct certificate details when uploading PFX file containing chain
- 3252 - Resolved issue removing private-key access-rules from Import Certificate steps
- 3255 - No longer query for all versions of a package from external NuGet feeds when loading release notes
- 3259 - Migrator now updates step template parameter IDs if they are null when imported
- 3260 - DB upgrade script added to update step template parameter IDs that are null
- 3261 - Project variables for Azure accounts that are scoped to a tenant tag are now resolved correctly when creating a deployment
- 3263 - Projects are now ordered alphabetically in the included/excluded lists on the dashboard configuration page
- 3264 - Fixed bug with Custom Installation Directory on SSH targets, the root path (/) can now be used again
- 3265 - Fix empty directories not extracting from zip packages
- 3267 - Improved performance of the CleanUnavailableMachines task
- 3269 - Substitute variables in files now supports glob and wildcard pattern matching
New in Octopus Deploy 3.11.7 (Mar 7, 2017)
- Deployment can now be initiated if the previous success deployment task references a deployment that does not exist
New in Octopus Deploy 3.11.6 (Mar 6, 2017)
- Avoid a PowerShell bug that can cause deployment pauses when an app pool is set to suspend
- Prevent project groups from being removed if linked to a team to avoid permission creep.
- Resolved issue with migrating tenant tags
- Added the special variable Octopus.Action.Package.TreatConfigTransformationWarningsAsErrors (defaults to true) to allow flexibility in dealing with config transform warnings
- The Server and Tentacle managers now allow scrolling of the instance list
- Correct pagination on the package index page so that it only takes into account a single version of each package
- Made 'Target roles' validation message more specific so it says which step needs to be fixed
- Order channels in a case-insensitive manner on the project dashboard
- Modals dismissed if url route changes or user logs out
- Modifying IIS bindings now triggers "You have unsaved changes" warning
New in Octopus Deploy 3.11.5 (Mar 3, 2017)
- Fixed deployment overview and logs listing steps out of order
New in Octopus Deploy 3.11.4 (Mar 1, 2017)
- Add Octopus.Action.FailScriptOnErrorOutput variable to fail scripts if they write to StdErr but return a zero error code
- Resolved certificate icon not found on variable grid
- The Force SSL checkbox in the server manager binding window now shows the correct state when it is first opened
- Fix 3.11.0 bug causing prompted variable labels field to go missing from UI
- Skip All with disabled steps result in an error
New in Octopus Deploy 3.11.3 (Feb 28, 2017)
- Data migration (export/import) no longer cares about the MimeType of logos
- Show clearer error messages when Octopus cannot create an SSH working directory
- Resolved issuecertificate variables scoped to Role were not being expanded
New in Octopus Deploy 3.11.2 (Feb 27, 2017)
- Update Docker Feeds to auto-detect version
- Removed vertical wrapping of project names on global dashboard
- Improved server resource usage with hundreds of polling tentacles
- Project sidebar nav tabs are now accessible on mobile
- Align radio buttons on deploy release page so that they are visible on smaller screens
- Added titles to the Tenant pages so a sensible title appears in the web browser tab
- Fixed a race condition that could cause health checks to stall
- We now actively prevent ClusterWideMutex from exhausting the SQL Connection Pool
- When a deployment resumes a Deployment Resumed event is raised instead of a Deployment Started event
- Resolved issue with certificate private-keys not being found in PFX files when the key was not in the first bag
- Fixed mouse cursor for Active Directory integrated authentication button
- Certificates scoped to environmentstenants are now only visible to users with permissions for at least one of the scoped environmentstenants
- NakedScripting should be renamed to RawScripting
- Restored Guest's user read-only access to data
New in Octopus Deploy 3.11.1 (Feb 25, 2017)
- Allow certificates with subject longer than 200 characters
- Fixed issue with variable prompt settings not displaying in variable value editor
- Fixed variable resolution on the create release page
New in Octopus Deploy 3.11.0 (Feb 23, 2017)
- Introduces certificate management.
New in Octopus Deploy 3.10.1 (Feb 20, 2017)
- Machine connectivity information is now restricted by the MachineView permission instead of MachineEdit permission
- Disabled steps will now be reflected in the deployment preview.
- Reduced memory usage when applying retention-policy to deployment manifests
- Unscoped variables are now visible again when viewing library variable sets
- Migrator exports now logos of community step templates and missing logos don't break community step templates sync.
- SSH scripts can now be cancelled if they are waiting for another script to execute
- Ensure inaccessible variables are not deleted when saving library variable sets
- Resolved migrator issue importing script-steps when project name contains invalid file-path characters
- Azure Resource Group deployments updated to fix issue with service management endpoint override
- Fixed error when saving action templates if it was last modified in pre 3.4.0.
- Allow skipping SSH health checks to support Naked Scripting
New in Octopus Deploy 3.10.0 (Feb 15, 2017)
- Prevent deploying to a custom directory that is a child of the default extraction path
- Sensitive variables in templates do not return their values through the API
- Fix a Tentacle compatability issue when running Tentacles 3.8.8-3.9.0 with Server older than 3.8.8
New in Octopus Deploy 3.9.0 (Feb 15, 2017)
- More detail is output for errors that occur during a guided deployment
- Added fields to the Azure Accounts to override the endpoints when using alternate Azure environments
- Deployment continues after retrying 10 times in guided failure mode
- Adding a new set of permissions for Project Triggers
- Fix for event-sourcing logic in auto-deploy and subscriptions (for HA scenarios)
- Octo.exe now looks for all supported package types when using --PackagesFolder with the pack command
- Fix to make long release names wrap on the dashboard
- Remove html tags from license error messages
- Allow leading zeros in pre-release versions when creating a release
New in Octopus Deploy 3.8.9 (Feb 13, 2017)
- Fix to show the Azure Web App name when editing the deployment step
- Bugfix causing deployment step to think changes need to be saved after initial page load.
- Improving the Azure Resource Group step's template validation for array types
- Allow changing the machine endpoint type when registering an existing machine name with the Tentacle installer
- Adding information to Azure step type screens for scenarios when target roles are selected
- Bugfix to handle Docker for Windows requiring long name parameters
- Correctly redirect 3rd party login to dashboard after logging out and back in again.
- Fixed spelling mistake in task logs when a step is disabled
- Improve the performance of creating a polling Tentacle with the installer when there are many machines
- Fixed a problem which could cause high CPU usage in retention policy processing with a large number of Projects, Channels, and Lifecycles
- Support the Docker Stop feature with Docker for Windows
New in Octopus Deploy 3.8.8 (Feb 10, 2017)
- 2867 - Packages from the built-in package repository are now sorted correctly
- 2962 - Fixed error downloading from NuGet V3 feeds on the Tentacle
- 3082 - The Octopus server and Tentacle now check to make sure the temp path is writeable
- 3141 - Ensure that during guided failure retries output variables contain the value from the current retry
- 3142 - Allow health checks to skip machines that can not be checked because they are currently involved in a deployment
- 3150 - Change the step run condition truth rules to match those used elsewhere in Octopus (anything not empty, 0 or "false" rather than "true" only)
- 3151 - Fixed a locking problem where delta compression used a cluster-wide mutex potentially causing SQL Connection Pool exhaustion under high load
- 3152 - Relative path config transformations now work if directory names are repeated
- 3153 - Config transforms with absolute path can now use the . prefix for the destination file path. See the examples in the documentation.
- 3156 - Fixed a locking problem where Calamari upgrades used a cluster-wide mutex potentially causing SQL Connection Pool exhaustion under high load
- 3158 - Fixed a potential race condition when handling simultaneous responses to interruptions (guided failures or manual interventions)
New in Octopus Deploy 3.8.7 (Feb 7, 2017)
- Projects can be configured to allow deployments to commence while there are no targets
- Fix deployments crashing when there is a variable called ##
- Script step run as Source Code always sets "Wait for packages to be downloaded" to false
- Do not show variables in library variable sets that are scoped to environments for which a user is not authorized
- Octopus UI resoures (e.g. JS, CSS) have been split into vendor and application bundles
- Error is now displayed when deleting an environment that is used in a lifecycle, deployment step or team
New in Octopus Deploy 3.8.6 (Feb 6, 2017)
- Rolling deployments can have now window size bound to a variable
- You can now configure the retry attempts used when downloading packages from external NuGet feeds
- Improved performance when downloading packages from external NuGet feeds over HTTP, we no longer query the feed for all versions of a package
- Running a health check step for a particular role will no longer exclude machines in other roles from the deployment
- The NetworkStream is now closed properly when downloading packages from external NuGet feeds over HTTP
- Fixed step failures due to network problems with polling Tentacles not being promptly reported
- Added table support to the Markdown filter in variable replacement
- Resolved issue with task logs not being migrated for 2.6 > 3.x migrations
- Web Application and Virtual Deployment step now retries if there is an error finding the parent site
- Fixed a problem causing high CPU usage during the "Apply Retention Policy" task
- Resolved Octopus Manager import error importing feeds when feed exists in target
- On Server 2016 Tentacles Calamari now supports extracting packages resulting in long paths
- image/x-icon and image/svg+xml MIME types are now supported for Octopus Manager export/import
New in Octopus Deploy 3.8.5 (Feb 2, 2017)
- 2959 - Credentials are no longer cached for NuGet feeds
- 3098 - Upon cancellation tasks now wait until all sub tasks are complete before being marked as cancelled
- 3118 - Update UI to avoid browser reloading between project tabs
New in Octopus Deploy 3.8.4 (Feb 1, 2017)
- 2425 - Long target names don't overlap each other anymore.
- 3112 - Allow saving project variable templates when user is scoped to projects or environments
- 3114 - Variables can be scoped now to disabled steps
New in Octopus Deploy 3.8.3 (Feb 1, 2017)
- 2468 - Immediately return logs if an automatic Tentacle upgrade fails
- 2811 - Add support for Nuget and Zip packages greater than 4Gb in size
- 2905 - Deployment now fails when the type of a custom package deployment script (not one bundled inside the package) is not compatible with the target machine
- 3029 - Show a confirmation dialog when deleting an environment if there are variables that are scoped just to that environment
- 3089 - Correctly evaluate #{if Variable} substitutions if there is whitespace between the variable and the closing brace
- 3104 - Fixed UI bug that was incorrectly showing the environment condition control on rolling steps.
- 3108 - De-duplicate email lists provided to the email Step
New in Octopus Deploy 3.8.2 (Jan 25, 2017)
- Fixed validation on step deletion, so steps that are being used for Auto Release Creation or Release Numbering cannot be deleted
- Check all columns use default database collation before upgrading
- Fixed a bug where the NancyContext would not be disposed if the underlying HttpListenerRequest failed to close
- Try to log web request context when unhandled exceptions are thrown in the web server
- Fixed a bug where a SQL Database transaction was held open for the life of the Octopus Server which was a potential cause for tempdb growth
- Resolved issue where no tenants were available for deployment when tenant view permissions did not match tenant deploy permissions
New in Octopus Deploy 3.8.1 (Jan 21, 2017)
- Correctly populate Octopus.Deployment.PreviousSuccessful.Id when the previous deployment failed
- Tenant counter is now visible on the dashboard
- Created a set of system variables containing information about the last successfully installed package
- Fixed a regression with the console output for the show-configuration command
- Fixed timeout with health checks on tenanted machines
New in Octopus Deploy 3.8.0 (Jan 21, 2017)
- Fix for auto-deploy to be more inclusive of machines when dealing with deployment-blocked scenarios
- Fix Javascript issue breaking the rolling deployment step page.
- Server side package download is not stopped when the deployment is cancelled
New in Octopus Deploy 3.7.10 (Dec 28, 2016)
- 2995 - Allow teams with project group permissions to clone projects in those project groups
- 3003 - Include project groups in team permission test
- 3005 - Teams restricted to project groups are now not able to view, edit or delete other project groups
New in Octopus Deploy 3.7.9 (Dec 28, 2016)
- 2854 - Add ability to select specific machines to exclude from a deployment
- 2910 - Adding configurable timezone for dates shown in subscription emails
- 2938 - Fix to subscription and machine policy timespan properties to properly support days, hours and minutes
- 2983 - Adding license configuration options for administrators to control the bullhorn/update notifications
- 3011 - 'Send an email' step now includes the ability to select teams
- [3018] - Calamari is now versioned correctly and reports the correct version number in the Task Logs
New in Octopus Deploy 3.7.8 (Dec 28, 2016)
- 2978 - Fixed ellipsis css and added tool tip for viewing longer names
- 3014 - Added strikethrough to make non-matching versions clearer in channel ‘design version rule’ dialog
- 3015 - Subscription edit screen will only show a warning about SMTP configuration if the SMTP configuration is truly incomplete
- 3019 - Published Octopus Server and Tentacle DSC to http://www.powershellgallery.com|www.powershellgallery.com
New in Octopus Deploy 3.7.7 (Dec 28, 2016)
- 2335 - Active Directory group search and security group loading working when Trusted Domains are being used. Users in trusted domains will need to log out/in of Octopus after patch to get security groups loading
- 2969 - Email addresses assigned directly in Octopus will not be cleared if an external authentication provider doesn't provide an email for the user
- 2988 - The Azure AD authentication provider now uses email then upn to find the matching Octopus User
- 3016 - Create user correctly assigns password for new non-service accounts
New in Octopus Deploy 3.7.6 (Dec 28, 2016)
- 3001 - Fix users being unable to delete Accounts if their AccountDelete permission is restricted to an Environment
- 3004 - Retry cleaning the temporary directory after accepting a pushed package
- 3008 - Fix deployment failing on Windows Server 2003 R2 if the nupkg file has files with % in their name
- 3009 - Fixed broken in 3.7.0 Previous step name dropdown
New in Octopus Deploy 3.7.5 (Dec 28, 2016)
- 2981 - Tenant tags are now spaced correctly on the Tenants page
- 2996 - Tag Sets can no longer be named with /, , ? or " characters.
- 2997 - Fix deployment steps being run twice in some cases where there are disabled steps before them
- 3000 - Linked templates have now their version updated correctly
New in Octopus Deploy 3.7.4 (Dec 9, 2016)
- Handle unexpected indexes on the Octopus database for a smoother database upgrade experience
- Fixed a bug preventing external NuGet feeds from working via a proxy server
- Display complete error message when testing Azure account
- Add variable path to exception msg when recursive-loop encountered
- Gracefully handle error evaluating package ID when applying retention policy
New in Octopus Deploy 3.7.3 (Dec 8, 2016)
- 2913 - New authentication providers handle paths correctly when Octopus Server is behind a reverse proxy / load balancer. Fixes issues including Http 404 error when trying to add AD groups to Teams.
- 2980 - Fixed an issue where retrying a failed save due to network error could delete the wrong variables
- 2982 - Fixed hitting tab when creating a new variable moving selection to the first row of the variable editor
- 2986 - Add variable path to exception msg when recursive-loop encountered
- 2987 - Gracefully handle error evaluating package ID when applying retention policy
New in Octopus Deploy 3.7.2 (Dec 8, 2016)
- 2979 - Step templates will be linked even if the version doesn't match
New in Octopus Deploy 3.7.1 (Dec 8, 2016)
- 2928 - Improvements to High Availability logging when a new node becomes leader
- 2940 - Tentacle Manager now includes support for API keys during Polling Tentacle registration
- 2977 - The upgrade notification now deep links directly to the Octopus Deploy version comparison page making it easier to understand what an upgrade actually means to each customer
New in Octopus Deploy 3.6.2 (Dec 8, 2016)
- 2974 - Fixed a problem which prevented registering Polling Tentacles when the ActiveDirectory authentication provider was used
New in Octopus Deploy 3.6.1 (Dec 8, 2016)
- 763 - Permissions can now be assigned based on project groups
- 2881 - Added helpful documentation link to the "licence limits exceeded" message
New in Octopus Deploy 3.6.0 (Dec 8, 2016)
- 2829 - Unhealthy machines will be displayed as Unhealthy even when Tentacle or Calamari need updating
- 2887 - Adding environment information logging (verbose level) to both Octopus and Calamari
- 2901 - Allow selection of specific events when configuring automatic deployment triggers
- 2917 - Updated wording on subscriptions page to better reflect e-mail and web hooks options
- 2968 - Correct a grammatical mistake in the integrity check logs
- 2970 - Fixed issue with wildcard config transforms when wildcard was not at the start of the filename
New in Octopus Deploy 3.5.9 (Dec 8, 2016)
- 2829 - Unhealthy machines will be displayed as Unhealthy even when Tentacle or Calamari need updating
- 2887 - Adding environment information logging (verbose level) to both Octopus and Calamari
- 2901 - Allow selection of specific events when configuring automatic deployment triggers
- 2917 - Updated wording on subscriptions page to better reflect e-mail and web hooks options
- 2968 - Correct a grammatical mistake in the integrity check logs
- 2970 - Fixed issue with wildcard config transforms when wildcard was not at the start of the filename
New in Octopus Deploy 3.5.8 (Dec 8, 2016)
- 2964 - Do not include disabled child steps in a deployment
New in Octopus Deploy 3.5.7 (Dec 8, 2016)
- 2957 - Support moving steps into and out of rolling deployments
New in Octopus Deploy 3.5.6 (Dec 8, 2016)
- 2750 - Updated Azure dependencies used in re-packaging Azure Cloud Services
- 2950 - Fixed an issue that was preventing ARM template parameters from saving when an array parameter had a default value
- 2961 - Fixed an error viewing the node configuration page
New in Octopus Deploy 3.5.5 (Dec 8, 2016)
- 2956 - Fixed incorrect reference in interruptions created in version 3.4.2 of Octopus
- 2958 - Added ability to disable steps in a deployment process
New in Octopus Deploy 3.5.4 (Dec 8, 2016)
- 2807 - Fixed some issues with the scrollbars on the Project Overview screen
- 2831 - Only validate accounts and feeds on actions that will actually run as part of the deployment
- 2878 - You can now Register a Listening Tentacle via a proxy which was previously not possible
- 2880 - Improved the warning message when configuration transform is not applied
- 2889 - The Octopus Server Manager will now configure the Octopus Server service to depend on SQL Server if using a local SQL database which will help prevent problems when starting Octopus Server
- 2898 - OctoPack now uses a custom build of nuget.exe which preserves the version as intended when creating packages
- 2924 - Fixed a bug which prevented automatic registration of a Tentacle via a custom proxy when using Octopus API key authentication
- 2933 - Fixed the link to the Tenant Overview from the Tenant Project Variable page when a project hasn’t been connected to any environments
- 2934 - Fixed a typo on the Library > Packages page
- 2935 - Fixed a bug which prevented users from signing in after putting the Octopus Server into Maintenance Mode
- 2936 - Improved responsiveness of the packages on the Releases page
- 2939 - Added username formatting requirements to Server Manager and the admin command when handling AD usernames
- 2941 - octo.exe now uses a custom build of the NuGet libraries which preserve the version as intended when creating packages
- 2942 - Added a notice that the Red Gate Database Deployment feature has been replaced by DLM Automation
- 2944 - Allow users to be created without a password, as it is not required by some authentication providers
- 2946 - Removed the dependency on our custom NuGet.Versioning package from Octopus.Client which was preventing it from being installed successfully
- 2947 - Fixed a bug on the Sign In page which would render a JSON representation of the certain errors instead of a friendly error message
- 2949 - Fixed a problem preventing OctoPack 3.4.3 from creating NuGet packages when Microsoft.Build.Framework, Version=14.0.0.0 isn’t available on the computer
- 2952 - Deployment action upgrade works now with template parameters missing 'ControlType'
New in Octopus Deploy 3.5.2 (Nov 18, 2016)
- Improved UI messaging around Automatic Release Creation
- Corrected issue where DSC was unable to download Tentacle msi
- Failed deployments with Manual Intervention and/or Guided Failure mode don't break Retention policy anymore
- Fixed issue where zip files containing one or more zip files failed to extract correctly
- Deep link context for Active Directory logins is no longer being blocked
- Active Directory auto login is now triggering correctly
- Corrected interruptions link for tasks on REST API
- Validation for creating service accounts corrected to ignore password data
- Added a Timeout option to the OctopusAsyncClient helper library
- Fixed issue where feeds were not falling back to the default NuGet type when imported using migrator
New in Octopus Deploy 3.5.1 (Nov 8, 2016)
- 2593 - An Azure AD authentication provider is included as a standard server extension
- 2680 - Open sourced Octopus.Client and implemented an async version of the API
- 2718 - Introducing Subscriptions, a new feature that allows you to subscribe to events happening within Octopus and be notified by email or webhook
- 2721 - A GoogleApps authentication provider is included as a standard server extension
- 2793 - Fixed incorrect reference in interruptions created in version 3.4.2 of Octopus
- 2815 - Resolved issue with parallel deployments failing under mono
- 2817 - Improving performance of pagination queries
- 2874 - Provide ability to perform basic Docker Engine commands
- 2877 - Closed database and network connections when an error occurs formatting the response
- 1938 - Library Variable Set page no longer includes Script Modules when paging through the list
- 2193 - Step template summary view in a deployment process now renders the configured values in the step
- 2860 - Auto-deploy performance improvements to better handle long-running deployments (you can also deploy to more than 2100 machines now)
- 2884 - Fixed a problem that would cause random Invalid Nonce errors when signing in with an OpenID Connect authentication provider
- 2890 - Improved how we were accessing the HomeDirectory when starting Octopus
- 2894 - Resolved spurious exception 'An attempt to parse the variable symbol {variable-name} appears to have resulted in a self referencing loop. Ensure that recursive loops do not exist in the variable values'
- 2896 - Image and API urls are now correctly resolved when Octopus Server is hosted using a virtual directory (this was a bug introduced in 3.5.0)
New in Octopus Deploy 3.5.0 (Nov 4, 2016)
- NEW:
- Subscriptions
- Extensible Authentication Providers (Guide)
- Steps and features to deploy Docker Containers (Guide)
- Breaking change: For anyone using the authentication URIs directly, with the introduction of authentication provider extensions we’ve now introduced different URI’s per-provider. You will need to use the hypermedia links provided in the home document
- SUPPORTING FEATURES FOR CONFIGURATION:
- To accompany the new Extensible Authentication Providers some additions have been made for server configuration:
- server configuration display available
- show-configuration export command
- UPGRADING:
- Read the upgrade guide for more details on upgrading from your current version to Octopus 3.5.
- CHANGES:
- An Azure AD authentication provider is included as a standard server extension
- Open sourced Octopus.Client and implemented an async version of the API
- Introducing Subscriptions, a new feature that allows you to subscribe to events happening within Octopus and be notified by email or webhook
- A GoogleApps authentication provider is included as a standard server extension
- Fixed incorrect reference in interruptions created in version 3.4.2 of Octopus
- Resolved issue with parallel deployments failing under mono
- Improving performance of pagination queries
- Provide ability to perform basic Docker Engine commands
- Closed database and network connections when an error occurs formatting the response
New in Octopus Deploy 3.4.15 (Oct 31, 2016)
- Creating a new role no longer adds the text (custom 'new' role) to the role
- Tentacle upgrade now only blocks if there is a deployment running that affects the Tentacle being upgraded
- Steps that were manually skipped during a deployment will also be skipped during subsequent automatic deployments
- All steps applicable to a deployment target, based on roles, will be run during an automatic deployment, even if some of those roles do not form part of the trigger's event filter
- Run steps that are scoped to multiple roles during automatic deployments if the deployment target has any of those roles
- The deploy screen now shows a warning about the impact of manually skipping steps when the project has any auto-deploy triggers
- Temporarily removed auto-deploy trigger steps preview, which could be misleading in certain scenarios, and replaced it with a more accurate description and link to documentation
- When a step targets roles, but there are no matching machines available during package acquisition, the package will no longer be (mistakenly) downloaded to the Octopus Server
New in Octopus Deploy 3.4.14 (Oct 25, 2016)
- When downloading a package directly on the Tentacle, and the download fails, we now clean up the partially downloaded package file
- The package cache clean task now run on all nodes in an HA environment
- Show an info box that running a PowerShell script as part of Azure steps require PowerShell 3
- Improved the error messages shown when the new IIS Web Site/Application/Virtual Directory Step finds unexpected content in IIS
- Improved usability of the new IIS Web Site and Application Step
- Converting an existing physical directory to either a Virtual Directory or Web Application in IIS now works, just like it used to in the old Step Templates
New in Octopus Deploy 3.4.13 (Oct 24, 2016)
- When variable templates are converted from sensitive to insensitive and vice versa, any variables based on the templates will also be converted
- Accounts are now imported when using the Octopus migrator
- Ensure a release goes through the correct Lifecycle phases for a tenant, even if the release has progressed past a phase for another tenant
- Add support for tables and strikethrough where Markdown can be used
- Ensure package is downloaded on the Octopus server for steps that use a package and executes on the server
- Package push instructions are now shown if a user has BuiltInFeedPush and they are scoped to project(s) or environment(s)
New in Octopus Deploy 3.4.12 (Oct 24, 2016)
- Automatic release creation now works for step template package steps
- Queue a Tentacle upgrade task if there are currently deployments running on the Tentacle
- Added delete button to server nodes UI
- Improved data integrity of teams scoped to environments and/or tenants
- Correct Azure subscription written to the task log when multiple subscriptions exist
- Variable scope dropdown is now correctly positioned when opened when editing a variable far down a long list of variables
- Fail a deployment if a custom install directory has been specified but we can’t properly evaluate the path or it is a relative path
- Include project triggers when cloning a project
- The sysdiagrams table is now ignored by the system integrity check
- Fix releases and projects that reference channels irrelevant to the release or project
- Fixed an error that occured when performing JSON transforms with a value of null
- Packages used by package steps based on step templates now follow package retention rules when being considered for removal from the built-in NuGet feed
- The 2.6 to 3 importer now ignores orphaned attachments when mapping documents
- Fix number of retries for package download to match number of attempts shown in log
- Ensure releases are created in a channel appropriate for the project
- Migrator can now import LibraryVariableSets when the VariableSet has an Id longer than 50 characters
- Azure scripts no longer fail if the Octopus working directory has a space in it
New in Octopus Deploy 3.4.11 (Sep 27, 2016)
- Support passing array, object and secureObject type parameter values into ARM templates
- Package acquisition for upgraded Azure steps should now work again
- Increase the amount of time spent retrying downloads from external package feeds
- Only machines applicable to the deployment should be listed when selecting specific deployment targets
- Prevent disabled projects from causing automatic deployments
- Prevent variable that had ever been scoped to steps and then the scope removed from being deleted when the deployment process is saved
- Fixed import order so now deployments with missing channel don't block channels from being imported
- Ensure new polling Tentacles using a proxy make their server registration calls through the proxy
New in Octopus Deploy 3.4.10 (Sep 22, 2016)
- Tenant drop down variables from projects and library variable sets now properly displays the default value if one has been set
- When deploying using the Deploy to all (or the Deploy on an individual Tenant) option from the Project Overview only include the applicable Tenant(s)
- Replacing SQL triggers with code-based triggers (to help us track future deadlock issues)
- Fixed recursive variable definitions causing a stack overflow
- Include variables, scoped variables and all system variable in auto-complete drop-down
- Fixed Tentacles not correctly loading custom proxy settings
New in Octopus Deploy 3.4.9 (Sep 15, 2016)
- Restore missing variables in binding auto-complete list
- Apply health check cleanup per machine policy
- Fix child actions which run on the server on behalf of a role not running for all machines
- Fixed trigger concurrency exception when automatically deleting multiple machines
New in Octopus Deploy 3.4.8 (Sep 14, 2016)
- Set KeepAliveInterval to 30 sec on SSH connections to keep connection to server open during long uploads.
- Avoid reading and writing variables at the same time
- Project Group selector on the Dashboard now sorts alphanumerically
- Log exception stack trace when a deployment action fails
- Populate the variables Octopus.Action.Status.Error and Octopus.Action.Status.ErrorDetail when an action running in parallel fails
- Physical path of IIS Website can be set on OS with PowerShell v2
New in Octopus Deploy 3.4.7 (Sep 12, 2016)
- Exposed IIS and Windows Service functionality as separate built-in steps
- Added Virtual Directory support to Package Deployment step
- Allow scoping library variable set variables to tenant tags when multi-tenancy is enabled
New in Octopus Deploy 3.4.6 (Sep 9, 2016)
- Added machine scoping to output variables that are set by a step that runs on the server on behalf of targets
- Reduce log level of the high number of transaction message
- Now returning the correct HTTP headers when a 401 Unauthorised response is returned
- Channels on project overview is now sorted by default channel and then alphabetically
- Improved error message when pushing a package to the built in repository with a non-SemVer 2.0.0 compliant version
- Health Check Steps now require Target Roles to be specified
New in Octopus Deploy 3.4.5 (Sep 9, 2016)
- Tenanted deployments can now progress through lifecycle phases when the minimum environment phase requirement has been satisfied
- Removed tenant information from triggers when not applicable
- Cascade environment deletion to tenant connections, tenant variables and triggers
- Fixed chocolatey packages by adding checksum information to the chocolateyInstaller.ps1 file
- Prevent the addition of project variable templates from clearing related tenant variables in some circumstances
New in Octopus Deploy 3.4.4 (Sep 6, 2016)
- Prevent incorrect environments from displaying in trigger summary
- Added support to set a custom deployment label for Azure cloud service steps
- Resolved issue downloading package with SemVer 2.0 versions on Tentacle from file-system feeds
- Fixed FilePathTooLong exception when extracting NuGet packages where file names contain unicode characters
- Resolved error deploying packages with SemVer 2.0 versions from remote NuGet feeds
New in Octopus Deploy 3.4.3 (Aug 31, 2016)
- Fixed an error that prevented deploying a release when the user is part of a team with Tenant restrictions set
- NuGetPackageId variable will now be correctly populated for steps after the first deployment step.
- Octopus.Client returns PackageFromBuiltInFeedResource instead of PackageResource for operations involving the built-in package feed
- Resolved error executing script Script0043 - Increase Package Column Widths.sql during 3.4 upgrade.
- Reverted changes to Octopus.Client that caused manual intervention steps to fail if they were awaiting approval before upgrading to 3.4.2
New in Octopus Deploy 3.4.2 (Aug 29, 2016)
- Prevent automatic deployments to tenanted targets when the tenant has been disconnected from the project or environment
- Prevent automatic deployments to tenanted or untenanted targets when a project is toggled to only tenanted or untenanted mode
- Resolved packages with different SemVer 2.0 metadata conflicting
- Reimplemented OctopusSuppressNestedScriptWarning variable
- Log a friendlier message if the health status of a machine is null when running our DB migrations
- Resolved issue downloading NuGet packages with 4-part versions from file-system feeds.
New in Octopus Deploy 3.4.1 (Aug 25, 2016)
- Automatic Release Creation settings will no longer be hidden if they have values
- Fixed an issue with VSTS/TFS creating releases
- Link to deployment triggers troubleshooting documentation is now more pronounced
- Update Step Template variables to use new generic package variable names
- Project triggers can be accessed with ProcessView and ProcessEdit permissions rather than ProjectEdit permissions
- Fixing edge case in auto-deploy regarding skipped deployment steps
- Ensure TenantView permission is given to all built-in project roles
- Tenants and TenantTags fields are now visible in the TeamCity plugin
- Fixed a bug which prevented editing Accounts if the multi-tenant deployments feature was not enabled
New in Octopus Deploy 3.4.0 (Aug 24, 2016)
- NEW FEATURES:
- 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 pp deployment targets. See below for more details.
- Deprecation notice: We are deprecating the MachineResource.Status property in favour of the new MachineResource.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: 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 excluded 1.0.0-alpha. It will now include it.
- 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.
- 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.
- 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.
- CHANGES:
- You can now manage tenants and tenanted deployments with Octopus Deploy
- Fixed issues around event table deadlocks
- Releases by channels are now shaded appropriately by channel on the project dashboard
- 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
- Warning we will deprecate Azure Targets in 3.4
- Octopus Server now returns 409 Conflict instead of 400 Bad Request when pushing duplicate package to the built-in package feed
- Upgrade to WebDeploy 3.6
- Upgrade NuGet libraries to 3.0
- Cloud Region target type
- You can now manage elastic and transient environments more easily with Octopus Deploy
- Improvements around SQL query plan caching
- Expanded proxy support to allow proxies in Tentacle communications
- Support for SSH connection through proxies
- Support SemVer 2.0
- 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
- You can now write custom scripts using F# (.fsx)
- Update to Tentacle registration to account for new MachineResources
- Project overview dashboard filtering, grouping and empty state improvements
- Only download a package once on a machine when it is used multiple times
- Remove project permission restrictions on health checks for environments
- Updated Azure PowerShell modules to version 1.6.0
- [DeployedBy] field on [Deployment] set to non nullable and deployment will fail if instigating user is undefined
New in Octopus Deploy 3.3.27 (Aug 11, 2016)
- When performing variable substitution on a file, try to continue when a parse error occurs rather than not performing any substitutions
- Patching our SQL alias generator to use predictable strings instead of random strings
New in Octopus Deploy 3.3.26 (Aug 9, 2016)
- Add thumbprint-only option to the show-thumbprint command to suppress explanatory text
- Ensure System Administrator role gets updated at server start to have all new permissions
New in Octopus Deploy 3.3.25 (Aug 8, 2016)
- When registering Tentacles, we now have validation to ensure the Tentacle+Server versions are compatible
- Added ability to handle long (> 100 characters) paths in .tar files
- Added a new permission AuditView to view audit log page (instead of requiring AdministerSystem permission)
- Added Azure Key Vault support to Azure Resource Group step
- Prevent [enter] on bound fields from showing the variable pop-up
- Refresh views to fix schema integrity check failing for some customers
- Show configuration menu for users who have audit/team permissions
- Handle absolute paths in config transforms
- Add additional logging to Tentacle to help diagnose startup issues
New in Octopus Deploy 3.3.24 (Jul 28, 2016)
- Clarify help text for skipping previously deployed packages
New in Octopus Deploy 3.3.23 (Jul 26, 2016)
- OctoStache update to include variable use in indexer and conditional comparison changes (see issue for usage)
- Filter environments shown on the Promote button according to the users permissions
- Don't alter variables when sanitizing entered hostnames for IIS bindings
- Octopus now supports substituting objects, arrays, boolean and numeric values in JSON files
- Octopus now supports substituting properties with colons in their name in JSON files
- Azure Web App step now supports specifying Resource Group
- Fix running Powershell tasks blocking the Tentacle port if Tentacle restarts
- Fix Calamari saving ASCII files as UTF-8 with a BOM when doing substitutions on Linux
- Block deletion of Environments that have deployment steps scoped to them, rather than removing the steps
New in Octopus Deploy 3.3.22 (Jul 14, 2016)
- Adding flags to the migrator to allow exporting and importing of task logs
- Errors are now logged more consistently regardless of whether the failed deployment step was running on a Deployment Target or the Octopus Server
New in Octopus Deploy 3.3.21 (Jul 13, 2016)
- Allow the Deployments API endpoint to be filtered by ChannelId and return ChannelId in the result
- Retention policies now retain the correct number of undeployed Releases for each individual Channel
- Fail deployment when an included Script Module has a syntax error
- Added ability to pass parameters to custom script files
- Fixed an issue with Halibut that would cause Polling Tentacle upgrades to stall/freeze under certain conditions
- Set Octopus.Action.PowerShell.ExecuteWithoutProfile to true on a project to not run the Tentacle service account's PowerShell profile script when running PowerShell script steps
- Updates to the 'Configure dashboard’ screen to be more user-friendly with long project names
- Show projects with running deployments on the dashboard even if they are beyond the 50 project limit
- Release and Task screens correctly retain the page selections for lists (e.g. Artifacts and History)
- The Octopus VSTS plugin now correctly logs deployment progress when Show Deployment Progress is checked
- Removed the time limit for Azure deployment retries, and set it to always retry 3 times
- Tasks that are canceled whilst waiting for other tasks to complete will now cancel when requested
New in Octopus Deploy 3.3.20 (Jun 29, 2016)
- Octopus.Deployment.Error now contains better information if a parallel step fails
- Run the Octopus installer from the command line with RUNMANAGERONEXIT=no to prevent the Octopus Manager from running
- Add a note to Azure account selection when a particular Azure account type is required
- Always show projects with failing deployments on the dashboard and allow the limit to be changed
- Octopus displays a message if queuing a system integrity check fails due to permissions
- System integrity check now ignores objects in the sys schema
- Ensured all database tables are in the dbo schema even when the creating user has a different default schema
- Fixed the population of the events list on the deployment status page
- Logged a warning when the result of an XML config transform results in a file without a root node
- Made the temporary file creation and deletion on deployment more robust
New in Octopus Deploy 3.3.19 (Jun 29, 2016)
- Fixed an error that occurs during the schema integrity check
- Fix Calamari converting ASCII files to UTF8 during variable substitution
New in Octopus Deploy 3.3.18 (Jun 29, 2016)
- Offline deployments now honour retention policies
- Prevent Releases being created when a Project is disabled
- Calamari fixes for file encoding during variable substitution
- Octo.exe now ensures that packageversion, if specified, is a semantic version
- Added additional transaction logging to help investigate potential SQL deadlock situations
- Calamari no longer crashes if Mono fails while finding earlier packages
- Added a system integrity check task that does some basic data and schema validation
- Removed performance bottleneck when evaluating variables after all machines have completed a step
- Database schema fix for potentially incorrect column length
- Fixed an issue where the server would not close SQL connections
New in Octopus Deploy 3.3.17 (Jun 29, 2016)
- Added ability to export permissions as a csv file on the Test Permissions page
- Fixed validation on the SMTP Port to prevent the exception when the field is blank
New in Octopus Deploy 3.3.16 (Jun 29, 2016)
- Improved error messages for incorrectly named packages
- Fixed HA secondary node servers not trusting newly added polling tentacles
- Fixed slowness when channels referenced a deployment step
New in Octopus Deploy 3.3.15 (Jun 29, 2016)
- Fixed a performance problem related to 2484 which could cause Octopus upgrades to 3.3.11 and above to be slow
- Added diagnostics logging for long running requests and queries
New in Octopus Deploy 3.3.14 (Jun 29, 2016)
- Allow Markdown formatting for NuGet package release-notes
- Added example of relative path for script file location in package to on-screen documentation
- Prevent Octopus working files (e.g. variables.json, bootstrap.ps1, etc) from syncing during Azure deployments.
- List all Script Modules rather than only the top 30
- Allow editing of window size for subsequent parallel steps
- 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
- 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) affecting create-channel, create-release, deploy-release, delete-releases, export and import
- The breadcrumb link on Configuration pages now redirects to the correct page
- Modified the dashboard query to resolve timeouts
- 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
- Fail cleanly if environment handed to octo.exe clean-environment is not found
- Added poll-server command to Tentacle to configure polling multiple servers
- You can now set the Octopus.Action.PowerShell.CustomPowerShellVersion variable, and your PowerShell scripts will be invoked with the -version flag
New in Octopus Deploy 3.3.12 (Jun 29, 2016)
- Changed Audit filter behaviour to include results that matched all filters provided
- Extended octo.exe delete-releases command to accept one or more --channel parameters
- Fixed the setting of the Octopus.Tentacle.Agent.InstanceName and Octopus.Tentacle.Agent.ProgramDirectoryPath variables and added the TentacleProgramDirectoryPath Environment Variable
- Improved the documentation for the --environment option for tentacle.exe register-with command
- Correctly show port number for listening Tentacles in the Tentacle Manager and updated path information to hyperlinks
- Unnecessary call to /api/reporting/ when rendering /#app/projects
- Fixed semaphore access when running multiple instances of Tentacle as different users
- Fixed the visibility of the paging control on the User Roles page
- Added octo.exe create-channel command to make it easier to create channels from build servers for per-branch channels (like feature branches)
- 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
New in Octopus Deploy 3.3.11 (Jun 29, 2016)
- Guest user not automatically being added to Everyone
- Long variables overlay history in release page
- Environment restriction from team membership should not override access granted by Administrators membership
- Same package in multiple steps downloads package multiple times on entacle
- Pushing a package with NuGet 3.4 causes a 500 error
- The packages api ignores the take and skip parameters
- Bug fixes to importer when encountering key-collisions and updating validation logic for frozen deployment processes and variable sets.
- Fixed issue with upgrader failing when there are orphaned channels
- Tentacle.exe to allow TLS 1.2 comms
- 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
New in Octopus Deploy 3.3.10 (Jun 29, 2016)
- No longer use $key as a variable name in bootstrap scripts so we don't clash with customer scripts.
- Fixed issue where existing script step templates caused validation errors when adding them to a step