Octopus 1.4 with updating variables, cloning projects and other fixes

Published on: 4 Mar 2013

Octopus Deploy 1.4 was just released. It includes a number of bug fixes, as well as improvements to the way we call PowerShell scripts.

In this release we also implemented a couple of the most popular feature requests we've had for a while.

Update release variables

When viewing a release, you can now update the variables in the release:

Updating Octopus release variables

Clicking this button will re-snapshot the current project variables into the release. If you have new variables for a step that didn't exist in the release, those variables will be skipped. An audit message will also be captured to track the fact that the variables were updated, and by whom.

This feature will only be supported on releases created after installing Octopus Deploy 1.4, because it required a small schema change to allow the variables to be imported.

Cloning projects

Need to copy a project? Just go to the project settings tab, and click this button:

Cloning a project

Disabling machines

Sometimes a machine might be down temporarily, and you don't want to deploy software to it. Now, you can just disable it instead of deleting it or moving it to a fake environment:

Disabling a machine

Disabled machines won't be used in deployments, nor in health checks/upgrades.

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!