Octopus Deploy 3.4 EAP

Published on: 23 Mar 2016 by: Michael Noonan

Octopus Deploy 3.4 has shipped! Read the blog post and download it today!

We are proud to announce the Early Access Program (EAP) for Octopus Deploy 3.4! This feature release is ambitious, and we want to get it in your hands earlier, rather than waiting to ship a nearly-baked pre-release. Now is absolutely the best time to get involved and let us know what you think!

What will Octopus Deploy 3.4 look like when it ships?

We are targeting two major sets of features for the full release of Octopus Deploy 3.4:

  • Multi-tenant deployments - read more
  • Improved elastic environment and transient machine support - read more however we want to take this further and make it even better!

What's in the box with Alpha 1?

We want to ship targeted, working pieces of the entire puzzle so you can start working with one concept at a time, imagining how each piece will start to fit together into an integrated whole, and respond to us with your feedback.

Multi-tenant deployments in Alpha 1

In Alpha 1 you can:

  • start working with tenants and tenant tags
  • link tenants to projects, and select environments for those projects. This will let you configure which projects are deployed for each tenant, and into which environment(s) - with the most flexibility for complex scenarios.
  • apply new security permissions for managing tenants
  • view new audit events created for tenants
  • do all of this via the Octopus API and client library!

 

Improved elastic environment and transient machine support in Alpha 1

We are testing the concept of a machine policy which could control certain aspects of the machine lifecycle:

  • What to do when a machine comes online (for the first time or recovering from an offline state)
  • Customize the health check script (starting with what we do today as a baseline/default)
  • What to do when a machine is offline at the start of a deployment, or goes offline during a deployment
  • What to do when a machine is offline for too long

In Alpha 1 you can:

  • build machine policies in the library
    • auto-delete machines that are offline for too long
    • skip machines that are offline at the start of a deployment, or that go offline during a deployment
  • apply a machine policy to each machine in your environments
  • apply new security permissions for managing machine policies
  • view new audit events created by machine policies
  • do all of this via the Octopus API and client library!

 

Getting started with Octopus Deploy Alpha 1

Our EAP comes with a 45-day Enterprise trial license. Download the latest EAP release taking a look through the release notes. Since it is so early in the development phase we will not support upgrading from EAP releases. We recommend installing the EAP release on a trial server.

Your feedback really does make a difference

Please post any feedback and join the conversation in our discussion forum. We would especially appreciate feedback on:

  • How well does the explicit mapping of Tenant to Project/Environment(s) map to your situation?
  • Can the combination of settings available in machine policies help reduce friction for your situation?

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