We are proud to announce the release of Octopus Deploy 3.4 Beta 2. We consider this release to be feature complete apart from small enhancements and bug fixes. There is still time to get involved in the Early Access Program (EAP) for Octopus Deploy 3.4 and let us know what you think!

What's new in Octopus Deploy 3.4 Beta 2?

In this release we have been building on the foundation of 3.4 Beta 1, with improvements to existing features, and have finished upgrading to NuGet 3, adding support for SemVer 2 and F# custom scripts. We have also finished work on octo.exe and the TeamCity and VSTS extensions so you can fully integrate 3.4 Beta 2 into your existing build pipeline, including all of the new Octopus 3.4 features.

You can see which bugs have been fixed in 3.4 Beta 2 in our GitHub repository, and feel free to take a look at the feedback everyone has been posting! Also, check out our Octopus 3.4 blog series for a deeper look into the new features and insight into the decisions that went into building the release.

What's new in multi-tenant deployments?

Apart from small enhancements and bug fixes, we have completed the work for multi-tenant deployments for Octopus Deploy 3.4.0. Rest assured, we will continue to work on improvements over the coming weeks and months.

Notable changes and improvements:

You can now search for tenants by name and tags

The global dashboard has been updated to correct some mistakes we made when displaying tenanted deployments for your projects/environments

The multi-tenant project overview has been improved, including:

improved filtering

the ability to group by tag set

the ability to deploy to groups of tenants, or even all the tenants in a particular environment

it is now easier to understand which tenants are connected to which environments

We have changed the way we calculate which deployment targets and accounts are included in deployments for tenants, which will make it easier to design tenanted and un-tenanted hosting scenarios:

Tenanted deployments use tenanted deployment targets and accounts (with a tenant filter of some kind).

The best place to get started with multi-tenant deployments is our guide.

What's new in elastic and transient environments?

Apart from small enhancements and bug fixes, we have completed work for elastic and transient environments support for Octopus 3.4.0.

Notable changes and improvements:

We have fixed a bug where project triggers were unexpectedly firing after a manual deployment

We have made it possible to use auto-deployments for brand new environments without any existing deployments, which enables you to create test environments on-the-fly. This is really useful for working with immutable infrastructure (thinking of servers as "cattle not pets"), and testing feature branches. You can read more about this in our guide on immutable infrastructure.

NuGet v3

We have replaced our dependencies on NuGet.Core by upgrading to NuGet 3 across the board, which means we have been able to close some long-term bugs, and support external NuGet v3 feeds! See this GitHub Issue for more information.

SemVer 2

You can now use SemVer 2 versions in releases and packages! This will make it much easier to work with SemVer 2 through your build and deployment pipeline, especially with tools like GitVersion.

Updated tools and integrations

We have updated Octopus.Tentacle.exe, the Octopus.Client SDK, octo.exe, and the TeamCity and VSTS extensions. Using these updated tools in conjunction with Octopus Server 3.4 you can now:

Moved proxy configuration to Environments

In Beta 2, we have moved the proxy configuration for Listening Tentacles into the Environment area. In Beta 1 you were required to grant System Administrator permissions to users so they could manage Tentacle proxy configuration. Now users can manage Tentacle proxy configuration after being granted the usual Proxy* permissions.

In a future release of Octopus Deploy we will cease support for the Azure Cloud Service and Azure Web App deployment targets.

Changes to health check results

We have introduced a new property MachineResource.HealthStatus for elastic and transient environments which can be either Healthy, HealthyWithWarnings, Unhealthy and Unavailable. You can continue to use the existing MachineResource.Status which can be either Online or Offline in Octopus 3.4, but we have marked the Status property as Obsolete and will be removing it in a future release.

Tentacle has been patched to work with Octopus 3.4

Registering a brand new Tentacle with Octopus 3.4 will fail if you are using an older version of Tentacle. This happens because old Tentacle doesn't understand Cloud Regions and couldn't deserialize them. We have patched Tentacle to be more resilient to these kinds of changes in the future.

Note: This issue only affects registering new Tentacles with your Octopus Server. Existing Tentacles will continue to work as per normal.

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.

What is still left to be done before we ship Octopus 3.4?

Apart from working with our fantastic Octopus community on feedback, we still need to:

Keep fleshing out our guides to help you make the most of these new features.

Provide guidance for migrating tenants into Octopus 3.4 using the API.

Further improve performance for really big installations with hundreds of tenants, environments and deployment targets.

Getting started with Octopus Deploy 3.4 Beta 2

Try it out on our 3.4 Beta 2 demo server using the guest account or get in touch with with our support team for elevated credentials.

Have an Azure subscription? You can spin up an entire Octopus setup using your own Azure subscription with our newly published template in the Azure Marketplace. This will install the latest stable version of Octopus Server on the VM, but you can use remote desktop to upgrade the Octopus Server to the EAP version. Finally you can easily delete the entire Resource Group when you're done!

Want to install it yourself?

Octopus Deploy comes with a 45-day Enterprise trial license. Download the Octopus 3.4 Beta 2 release taking a look through the release notes. We will support upgrades from these Beta releases to the full release of Octopus 3.4, but we do not support downgrades to a previous version of Octopus. If you want to upgrade an existing Octopus server, don't forget to take and test a backup of your database. Otherwise we recommend installing on a trial server.

Your feedback really does make a difference

Go ahead, get involved and help us build the best Octopus Deploy yet. Happy Deployments!

Octopus Deploy is used by thousands of developers across the globe, from small companies to large enterprises. Find out if it meets your deployment automation needs by taking advantage of our free 30-day trial. You can spin up an instance with just a few clicks!