You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/_posts/2015-07-22-how-to-continuously-deploy-entire-environment.markdown
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,12 @@ title: "How to continuously deploy an entire environment"
4
4
date: 2015-07-22 15:00:00 +0100
5
5
comments: true
6
6
author: Rytis Bieliunas
7
-
categories: agile automation cd octopusdeploy
7
+
categories: agile automation cd octopusdeploy
8
8
---
9
9
10
-
At Bede we are using Octopus Deploy as our deployment automation system. We use it to promote our platform components from integration environment through development, QA to production. It worked wonderfully well for us. However Bede has grown. We have near 100 different projects in Octopus and nowmultiple production environments.
10
+
At Bede we are using Octopus Deploy as our deployment automation system. We use it to promote the numerous components of our platform through various environments, from Integration, through Development and QA, and finally to Production. It's worked wonderfully well for us so far. However Bede has grown. We have near 100 different projects in Octopus and now, more importantly, multiple Production environments.
11
11
12
-
What we need is a way to take QA'd environment, where we know all components work well together, and deploy the entire thing to another environment.
12
+
What we needed was a way to take a QA'd environment, consisting of the entire set of components, and deploy that set, as one, to another environment. This is what we're calling a "Platform Version".
13
13
<!-- more -->
14
14
15
15
Lucky for us Octopus Deploy exposes a complete API. That means every thing that you can do as a user can be automated.
@@ -20,6 +20,10 @@ And so we are building: **Conan The Deployer**
20
20
*He looks innocent enough here, but he can mess up your entire production environment*
Conan essentially acts as a coordination and orchaestration layer on top of Octopus Deploy, and a source of truth for the state of any given OD environment. Conan records the state of an environment, either on demand or to schedule. Conan can coordinate between multiple instances of Octopus Deploy, when for example you may have an OD instance per-client.
24
+
25
+
Quick rundown of what we're using it for:
26
+
23
27
First thing you need to do is take a snapshot, which captures all component release versions on selected environment:
24
28
25
29
{% img center /images/conan_dashboard.png 'Conan Dashboard' 'Conan Dashboard' %}
0 commit comments