Check out the release notes for a more comprehensive list of what’s new in Update 2 but I’ll list some of the highlights here.<\/p>\n
Delivery Plans<\/h3>\n
Delivery Plans provide the ability for you to align the work of many teams on a common timeline the work can be viewed at any level of granularity.\u00a0 You can expand and collapse teams to see more or less detail and you can add tags for key milestones to see how all the work lines up for delivery.\u00a0 This is a fantastic new ability for managing work in an organization with more than just a couple of teams.\u00a0 To enable it on your server, you will need to install the Delivery Plans extension <\/a>on your TFS 2017.2 or later server.\n Using the same Elastic Search based infrastructure that Code Search uses, work item search provides a simple an intuitive way to find work items when creating a query is overkill.\n The improvements to Pull requests and branch policies are too numerous to mention – there are dozens.\u00a0 In Update 2 we spent a ton of time working to address feedback and suggestions from people who have been using our PR experience over the past year or so.\u00a0 To summarize:<\/p>\n We added important new Git features – like a commit history graph and support for adding\/finding Git tags.\n We made numerous improvements to the TFS build system – one of the larger ones is an improved build definition editor and task improvements.\u00a0 Build templates enable you to start with a good base template for your application type.\u00a0 A simple drag and drop task composition experience makes the process super easy.\u00a0 A new “Process parameters” allows you to promote key build process parameters to a consolidated configuration section, making it even quicker to get a base definition configured.\u00a0 Conditional build tasks allow you to consolidate build definitions in cases where you may have had to have multiple very similar definitions.\n We made tons of smaller improvements to our release management and deployment capabilities.<\/p>\n The biggest improvement was the consolidation of the Build, Deploy and Test agents into a single agent.\u00a0 This makes it easier to share agents in pools.\u00a0 We also added support for manually triggering automated test runs from our web UI (a capability that has been in the rich client for a long time but has been missing from our web experience).<\/p>\n And lots of stuff I didn’t mention – check out the release notes <\/a>for full details.\u00a0 Overall, it’s a substantial advance over Update 1.\u00a0 We really hope you like it and, as always, feedback is appreciated.\u00a0 This is the last “feature update” in the TFS 2017 line.\u00a0 Update 3 will really focus on fixes for customer reported bugs.\u00a0 The first release candidate for the next major TFS release will be available within the next couple of months – for those of you trail blazers out there.\nFeedback vehicles:<\/p>\n Thanks,\nBrian<\/p>\n","protected":false},"excerpt":{"rendered":" Today we released the final version of Team Foundation Server 2017.2.\u00a0 Thank you to everyone who installed one of the two release candidates over the past few months and helped us ensure that this is a high quality release. This post lists some important links and info about this release. <\/p>\n","protected":false},"author":244,"featured_media":14617,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[5],"class_list":["post-13275","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-tfs"],"acf":[],"blog_post_summary":" Today we released the final version of Team Foundation Server 2017.2.\u00a0 Thank you to everyone who installed one of the two release candidates over the past few months and helped us ensure that this is a high quality release. This post lists some important links and info about this release. <\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/13275","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/users\/244"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/comments?post=13275"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/13275\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/media\/14617"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/media?parent=13275"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/categories?post=13275"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/tags?post=13275"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"\"](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/8\/2019\/02\/DeliveryPlans.png\")
<\/a><\/p>\nWork Item Search<\/h3>\n
![\"\"](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/8\/2019\/02\/WorkItemSearch.png\")
<\/a><\/p>\nPull requests and branch policies<\/h3>\n
\n
New Git features<\/h3>\n
![\"\"](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/8\/2019\/02\/GitGraph.png\")
<\/a><\/p>\nA new build definition editor<\/h3>\n
![\"\"](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/8\/2019\/02\/BuildEditor.png\")
<\/a><\/p>\nRelease Management<\/h3>\n
\n
Testing<\/h3>\n
Conclusion<\/h3>\n
\n