Outage on octopus.com - report and learningsPublic incident report and our learnings about the octopus.com DNS disruption from January 25 – 26, 2023.
The ultimate guide to rolling deploymentsWhat 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 availableOctopus Cloud: Western Europe region is now available
Kubernetes deployment strategies visualizedSee pods being deployed with either rolling updates, recreates, or blue/green deployments.
Runbooks best practicesThis post provides a step by step template you can use to generate high quality runbooks in Octopus.
Still deploying manually? What you're missingBy automating deployments, they become less painful and more reliable, which allows you to make them more frequently.
My First Year Working at OctopusRob Pearson sharing what it's like to work at Octopus Deploy and a bit about the company culture.
Expanding Proxy SupportOctopus 3.4 introduces expanded proxy support so Octopus Server and Tenacle can now communicate to each other through HTTP proxies.
What is an un-tenanted deployment in 3.4?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?
Tenant aware lifecyclesIntroducing 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.
Deploying to dynamically provisioned infrastructureHow to dynamically include new infrastructure during a deployment
Deploying software shouldn't feel like visiting the dentistReasons you should deploy early and often.
The big 5 benefits of automated deploymentA guest post that explores the benefits of automated deployments.
The why and more importantly the how of automated database deploymentWhy and how your should automate your database deployments
RFC: Improving the deployment processProposed changes to better support using Octopus to deploy in distributed environments.
Why consider database deployment automation?This post explores why automating scripts to deploy database changes is valuable and some of the benefits of database deployment automation.
The Evolution of Auto-Deployments and Event-SourcingOctopus 3.4 introduces elastic and transient environments and this post explores the evolution of auto-deployments in this context.
Keeping environments cleanOctopus 3.4 introduces the concept of machine policies which enable the automatic deletion of unavailable machines after a configurable time period has elapsed.
Script ParametersOctopus 3.3.21 introduces ability to pass parameters to scripts.
Defining variables in a multi-tenant worldExploring how to define variables in a multi-tenant world.
Octopus 3.4 blog series kick offOctopus 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 Command Line (CLI)The Octopus CLI (octo) is the Octopus command line tool that builds on top of the Octopus REST API.
Build informationPushes build information to Octopus Server.
Clean environmentsUsing the Octopus CLI to delete/remove machines with a particular status from environments on your Octopus instance.
Clean Worker poolCleans all Offline Workers from a Worker Pool
Create auto deployment overrideUsing the Octopus CLI to create automatic deployment release overrides.
Create channelUsing the Octopus CLI to create channels.
Create environmentUsing the Octopus CLI to create environments.
Can't find what you are looking for? You can also search our support forum.