The Octopus Deploy Blog

Exploring how to define variables in a multi-tenant world.

Octopus 3.4 introduces the concept of machine policies which enable the automatic deletion of unavailable machines after a configurable time period has elapsed.

Octopus 3.3.21 introduces ability to pass parameters to scripts.

Octopus 3.4 introduces multi-tenant deployments to allow you to deploy your releases to the same environment within the context of different tenants! So what happens if you don't want to deploy a release to a tenant?

A walk-through of deploying an ASP.NET Core application to Red Hat Enterprise Linux using Octopus Deploy

Multi-tenant deployments have finally arrived! This post takes a look back on why the roadmap for the new feature took such a detour but how it has become ultimately shaped by our users.

Octopus 3.4 introduces elastic and transient environments and this post explores the evolution of auto-deployments in this context.

Octopus 3.4 introduces expanded proxy support so Octopus Server and Tenacle can now communicate to each other through HTTP proxies.

Octopus 3.4 blog series kick off with links to posts talking about new feature deep dives and the decisions that went in to building them.

Octopus 3.4 has finally reached beta maturity, and we are excited for you to try out these features for real in your own environment: now with multi-tenant deployments, improved support for elastic and transient environments, Cloud Regions, and proxy support for Tentacle communications.