What are rolling deployments and why are they useful? This post covers the rolling deployment pattern and practical examples of how to implement it with different tooling.
Octopus Cloud: Western Europe region is now available
See pods being deployed with either rolling updates, recreates, or blue/green deployments.
This post provides a step by step template you can use to generate high quality runbooks in Octopus.
By automating deployments, they become less painful and more reliable, which allows you to make them more frequently.
Rob Pearson sharing what it's like to work at Octopus Deploy and a bit about the company culture.
Octopus 3.4 introduces expanded proxy support so Octopus Server and Tenacle can now communicate to each other through HTTP proxies.
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?
Introducing multiple tenants to your deployment process in 3.4.0 has impacts on how that release progresses through its life cycle. Tenants can define required environments and un tenanted deployments can ensure deployments can be made where a tenant context is not relevant.
How to dynamically include new infrastructure during a deployment
Reasons you should deploy early and often.
A guest post that explores the benefits of automated deployments.
Why and how your should automate your database deployments
Proposed changes to better support using Octopus to deploy in distributed environments.
This post explores why automating scripts to deploy database changes is valuable and some of the benefits of database deployment automation.
Octopus 3.4 introduces elastic and transient environments and this post explores the evolution of auto-deployments in this context.
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.
Exploring how to define variables in a multi-tenant world.
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.
The Octopus CLI (octo) is the Octopus command line tool that builds on top of the Octopus REST API.
Pushes build information to Octopus Server.
Using the Octopus CLI to delete/remove machines with a particular status from environments on your Octopus instance.
Cleans all Offline Workers from a Worker Pool
Using the Octopus CLI to create automatic deployment release overrides.
Using the Octopus CLI to create channels.
Using the Octopus CLI to create environments.
Using the Octopus CLI to create projects.
Can't find what you are looking for? You can also search our support forum.