What's new in Octopus Deploy 3.1
Octopus Deploy High Availability is our offering for customers where Octopus Deploy has become a critical piece of infrastructure. In addition to the benefits of extra reliability, High Availability provides performance gains over a single Octopus Server. Our aim was to provide a linear performance increase as you add nodes to your High Availability cluster.
Very soon we'll be launching Octopus: High Availability (HA) edition. To prepare for High Availability, we're making a few changes which will make it easier to manage Octopus server workloads.
Some lessons we've learned in the last few months that change the way we work. Plus tools for a distributed team
Octopus and Tentacle have always been built against .NET 4.0, but from Octopus 3.1 onwards we'll be building against .NET 4.5.
We recently made big changes to deployment targets and Azure cloud services in Octopus 3.0, and it turns out we got our design wrong. In 3.1, we'll be reverting to the 2.6-era way of deploying cloud services. This change will also affect the way we deploy Azure web apps.
Variables can be scoped to multiple values. What's the simplest way to score them?
Now that 3.0 has shipped, we'll be moving towards iterating quickly and releasing new versions of Octopus as soon as there is something to release.
Blue/green style deployments by varying the port number between each deployment