{"id":1905,"date":"2017-06-02T07:26:43","date_gmt":"2017-06-01T23:26:43","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/vsnews\/?p=1905"},"modified":"2017-06-02T07:26:43","modified_gmt":"2017-06-01T23:26:43","slug":"hlh6xs","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/vsnews\/akams-hlh6xs\/","title":{"rendered":"Evolving TFS\/Team Services build automation capabilities"},"content":{"rendered":"<p>We first introduced basic build automation capabilities in TFS 2005 and, over the years, it has evolved substantially. \u00a0In TFS 2010, we introduced a major update which we now call \u201cXAML build\u201d\u009d because the build orchestration layer was based on the XAML workflow engine. \u00a0As that got adopted, we found that workflow was just not the best representation of build processes \u2013 wrong granularity for build, not natural to extend for build, provides capabilities (like durability) that really don\u2019t apply to build, etc.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>We first introduced basic build automation capabilities in TFS 2005 and, over the years, it has evolved substantially. \u00a0In TFS 2010, we introduced a major update which we now call \u201cXAML build\u201d\u009d because the build orchestration layer was based on the XAML workflow engine. \u00a0As that got adopted, we found that workflow was just not [&hellip;]<\/p>\n","protected":false},"author":27,"featured_media":8227,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1905","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-allskus"],"acf":[],"blog_post_summary":"<p>We first introduced basic build automation capabilities in TFS 2005 and, over the years, it has evolved substantially. \u00a0In TFS 2010, we introduced a major update which we now call \u201cXAML build\u201d\u009d because the build orchestration layer was based on the XAML workflow engine. \u00a0As that got adopted, we found that workflow was just not [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/posts\/1905","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/comments?post=1905"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/posts\/1905\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/media\/8227"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/media?parent=1905"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/categories?post=1905"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/tags?post=1905"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}