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:
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:
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:
Disabled machines won’t be used in deployments, nor in health checks/upgrades.
Happy deployments!
Tags:
Related posts
Certificates Feature
Certificates can be uploaded in PFX, PEM, or DER formats, and may include private-keys. They can be scoped to Environments and\or Tenants.
Deploying to no targets
As part of Octopus Deploy 3.8.7 we released a new feature related to Elastic and Transient Environments that we thought warranted a call out.
Octopus Deploy 3.7 - Effortless step templates
The new release of Octopus Deploy steps it up a notch by improving the UI for adding a step template, providing direct access to community step templates from a project's deployment process and improving the management of step templates in the library.
