<img height="1" width="1" src="https://www.facebook.com/tr?id=&amp;ev=PageView &amp;noscript=1">

Posted by Laura Bria
Thu, Aug 13, 2015

Welcome to the 35th edition of #ThisWeekInDevOps !
This blog aims to keep you up to date with the latest news from the world of DevOps.

Posted by Laura Bria
Thu, Mar 12, 2015

Welcome to the 13th edition of #ThisWeekInDevOps ! 

This blog aims to keep you up to date with the latest news from the world of DevOps.

Posted by Tom Stockton
Tue, May 27, 2014

What is this?

Martin Fowler provides a fairly definitive explanation of this () so I’ll try not to regurgitate what he’s written too much! However, in my mind (and in my own words) I’d say that blue green is about 'getting the latest version of your software into production as quickly and efficiently as possible'. Essentially it involves creating a (green) version of your existing (blue) system with your latest code deployment, then (after confirming it works) switching end user requests to use the green version.  If there are any issues then you can easily roll back to blue and forget green ever happened.

Posted by Cornel Foltea
Thu, May 22, 2014

The AIM

The aim is to expose the key steps in order to set up a Jenkins master instance able to spin up slaves on demand within the AWS cloud. Cutting cost is the main goal if managers wonder what’s the use of having such a setup. More to that, taking the on-demand approach will keep your executors fresh and healthy, always running on a recently spawned machine.

Posts by Topic

see all

Subscribe to Email Updates