<?xml version="1.0"?>
<oembed><version>1.0</version><provider_name>Brian Harry's Blog</provider_name><provider_url>https://devblogs.microsoft.com/bharry</provider_url><author_name>Brian Harry</author_name><author_url>https://devblogs.microsoft.com/bharry/author/bharry/</author_url><title>Improvements for Continuous Integration using TFS</title><type>rich</type><width>600</width><height>338</height><html>&lt;blockquote class="wp-embedded-content" data-secret="GqfZiruwcK"&gt;&lt;a href="https://devblogs.microsoft.com/bharry/improvements-for-continuous-integration-using-tfs/"&gt;Improvements for Continuous Integration using TFS&lt;/a&gt;&lt;/blockquote&gt;&lt;iframe sandbox="allow-scripts" security="restricted" src="https://devblogs.microsoft.com/bharry/improvements-for-continuous-integration-using-tfs/embed/#?secret=GqfZiruwcK" width="600" height="338" title="&#x201C;Improvements for Continuous Integration using TFS&#x201D; &#x2014; Brian Harry's Blog" data-secret="GqfZiruwcK" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" class="wp-embedded-content"&gt;&lt;/iframe&gt;&lt;script type="text/javascript"&gt;
/* &lt;![CDATA[ */
/*! This file is auto-generated */
!function(d,l){"use strict";l.querySelector&amp;&amp;d.addEventListener&amp;&amp;"undefined"!=typeof URL&amp;&amp;(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&amp;&amp;!/[^a-zA-Z0-9]/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret="'+t.secret+'"]'),o=l.querySelectorAll('blockquote[data-secret="'+t.secret+'"]'),c=new RegExp("^https?:$","i"),i=0;i&lt;o.length;i++)o[i].style.display="none";for(i=0;i&lt;a.length;i++)s=a[i],e.source===s.contentWindow&amp;&amp;(s.removeAttribute("style"),"height"===t.message?(1e3&lt;(r=parseInt(t.value,10))?r=1e3:~~r&lt;200&amp;&amp;(r=200),s.height=r):"link"===t.message&amp;&amp;(r=new URL(s.getAttribute("src")),n=new URL(t.value),c.test(n.protocol))&amp;&amp;n.host===r.host&amp;&amp;l.activeElement===s&amp;&amp;(d.top.location.href=t.value))}},d.addEventListener("message",d.wp.receiveEmbedMessage,!1),l.addEventListener("DOMContentLoaded",function(){for(var e,t,s=l.querySelectorAll("iframe.wp-embedded-content"),r=0;r&lt;s.length;r++)(t=(e=s[r]).getAttribute("data-secret"))||(t=Math.random().toString(36).substring(2,12),e.src+="#?secret="+t,e.setAttribute("data-secret",t)),e.contentWindow.postMessage({message:"ready",secret:t},"*")},!1)))}(window,document);
//# sourceURL=https://devblogs.microsoft.com/bharry/wp-includes/js/wp-embed.min.js
/* ]]&gt; */
&lt;/script&gt;
</html><thumbnail_url>https://devblogs.microsoft.com/bharry/wp-content/uploads/sites/8/2018/08/vstsfeature.png</thumbnail_url><thumbnail_width>716</thumbnail_width><thumbnail_height>448</thumbnail_height><description>One of the big complaints we&#x2019;ve gotten from customers trying to build a Continuous Integration or similar automated build and test system with VSTS has been around the difficulty of authoring and maintaining the test lists that identify what tests to run as part of the build process. Buck has come to the rescue and [&hellip;]</description></oembed>
