<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Deployment pipeline on Mysterious Code - Senior AWS, DevOps &amp; security engineering</title><link>https://mysteriouscode.com/blog/series/deployment-pipeline/</link><description>Recent content in Deployment pipeline on Mysterious Code - Senior AWS, DevOps &amp; security engineering</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Fri, 07 Oct 2016 10:00:01 +0000</lastBuildDate><atom:link href="https://mysteriouscode.com/blog/series/deployment-pipeline/index.xml" rel="self" type="application/rss+xml"/><item><title>Deployment pipeline, part 3: deployment onto an environment</title><link>https://mysteriouscode.com/blog/deployment-pipeline-part-3-deployment-onto-an-environment/</link><pubDate>Fri, 07 Oct 2016 10:00:01 +0000</pubDate><guid>https://mysteriouscode.com/blog/deployment-pipeline-part-3-deployment-onto-an-environment/</guid><description>&lt;p&gt;The purpose of every deployment pipeline is&amp;hellip; a deployment. So this final part of the series, will focus on just that.
If you missed the
intro, &lt;a href="https://mysteriouscode.com/blog/typical-ci-deployment-pipeline-overview/"&gt;check out the video where I describe a typical pipeline here&lt;/a&gt;.
The other parts of this series are &lt;a href="https://mysteriouscode.com/blog/deployment-pipeline-part-1-test-phase/"&gt;part 1: test phase&lt;/a&gt;
and &lt;a href="https://mysteriouscode.com/blog/deployment-pipeline-part-2-build-phase/"&gt;part 2: build phase&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;

&lt;img src="https://mysteriouscode.com/images/blog/2016/10/pipeline-part-3_hu_7b9b6719f4a3f4d1.png" srcset="https://mysteriouscode.com/images/blog/2016/10/pipeline-part-3_hu_b13c94fd8d53f0b9.webp 320w, https://mysteriouscode.com/images/blog/2016/10/pipeline-part-3_hu_873dbe1b6b72d86.webp 640w, https://mysteriouscode.com/images/blog/2016/10/pipeline-part-3_hu_456e34f418b1081.webp 960w, https://mysteriouscode.com/images/blog/2016/10/pipeline-part-3_hu_b9f4a77ee51c1eb1.webp 969w" sizes="(max-width: 800px) 100vw, 800px" alt="pipeline-part-3" loading="lazy"&gt;
&lt;/p&gt;
&lt;p&gt;Once we create an AMI that we&amp;rsquo;d like to deploy, performing a rolling update on existing instances is fairly easy. Usage
of Auto scaling groups and CloudFormation makes it even easier - &lt;a href="http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-updatepolicy.html"&gt;since AWS Auto scaling groups support the rolling updates&lt;/a&gt;
out of the box.&lt;/p&gt;
&lt;p&gt;Or, if your applications requires blue-green deployments, using CloudFormation is almost essential.&lt;/p&gt;</description></item><item><title>Deployment pipeline, part 2: build phase</title><link>https://mysteriouscode.com/blog/deployment-pipeline-part-2-build-phase/</link><pubDate>Mon, 03 Oct 2016 09:00:58 +0000</pubDate><guid>https://mysteriouscode.com/blog/deployment-pipeline-part-2-build-phase/</guid><description>&lt;p&gt;Welcome to the second part of my series on deployment pipelines. If you missed the
intro, &lt;a href="https://mysteriouscode.com/blog/typical-ci-deployment-pipeline-overview/"&gt;check out the video where I describe a typical pipeline here&lt;/a&gt;.
The other parts of this series are &lt;a href="https://mysteriouscode.com/blog/deployment-pipeline-part-1-test-phase/"&gt;part 1: test phase&lt;/a&gt;
and &lt;a href="https://mysteriouscode.com/blog/deployment-pipeline-part-3-deployment-onto-an-environment/"&gt;part 3: deployment onto an environment&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;

&lt;img src="https://mysteriouscode.com/images/blog/2016/10/pipeline-part-2_hu_db446001d7363445.png" srcset="https://mysteriouscode.com/images/blog/2016/10/pipeline-part-2_hu_aacdc607f3689075.webp 279w" sizes="(max-width: 800px) 100vw, 800px" alt="pipeline-part-2" loading="lazy"&gt;
&lt;/p&gt;
&lt;p&gt;After the test phase of the pipeline, once the quality of the code has been checked, we must build a deployable artefact
for this version (commit) of the code. In case of AWS, this would be an
AMI (&lt;a href="http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html"&gt;Amazon Machine Image&lt;/a&gt;), which can then be deployed
as a new instance in our environment.&lt;/p&gt;</description></item><item><title>Deployment pipeline, part 1: test phase</title><link>https://mysteriouscode.com/blog/deployment-pipeline-part-1-test-phase/</link><pubDate>Fri, 30 Sep 2016 10:00:10 +0000</pubDate><guid>https://mysteriouscode.com/blog/deployment-pipeline-part-1-test-phase/</guid><description>&lt;p&gt;Welcome to the first part of my series on deployment pipelines. If you missed the
intro, &lt;a href="https://mysteriouscode.com/blog/typical-ci-deployment-pipeline-overview/"&gt;check out the video where I describe a typical pipeline here.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;

&lt;img src="https://mysteriouscode.com/images/blog/2016/09/pipeline-part-1_hu_1db87839cac00b39.png" srcset="https://mysteriouscode.com/images/blog/2016/09/pipeline-part-1_hu_6e8c42a9b6cfbec3.webp 276w" sizes="(max-width: 800px) 100vw, 800px" alt="pipeline-part-1" loading="lazy"&gt;
&lt;/p&gt;
&lt;p&gt;First step of a deployment pipeline, is usually a series of tests. After a commit is made, the code is checked out from
the source code repository and tested. Those are usually code style tests and unit tests.&lt;/p&gt;</description></item><item><title>Typical CI deployment pipeline - overview</title><link>https://mysteriouscode.com/blog/typical-ci-deployment-pipeline-overview/</link><pubDate>Fri, 23 Sep 2016 00:02:37 +0000</pubDate><guid>https://mysteriouscode.com/blog/typical-ci-deployment-pipeline-overview/</guid><description>&lt;div
					style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;"&gt;
				&lt;iframe
					src="https://player.vimeo.com/video/183889021?dnt=0"
						style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;" allow="fullscreen"&gt;
				&lt;/iframe&gt;
			&lt;/div&gt;

&lt;p&gt;More details on each deployment phase with examples, will be posted at our blog over the coming weeks, so check back
soon.&lt;/p&gt;</description></item></channel></rss>