{"id":54060,"date":"2019-02-01T16:18:55","date_gmt":"2019-02-02T00:18:55","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/devops\/?p=54060"},"modified":"2019-02-15T08:05:13","modified_gmt":"2019-02-15T16:05:13","slug":"azure-devops-roadmap-update-for-2019-q1","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/azure-devops-roadmap-update-for-2019-q1\/","title":{"rendered":"Azure DevOps Roadmap update for 2019 Q1"},"content":{"rendered":"

Last week we updated the Features Timeline<\/a> to provide visibility on our key investments for this quarter.\u00a0The features listed below link to the public roadmap project where you can find more details about each item. Here are a few highlights on some of the features for Q1 and Q2.<\/p>\n

Azure Boards:<\/strong><\/p>\n

Editing and deleting of work item comments<\/a> \u2013 2019 Q1<\/strong> With this capability, you’ll be able to edit or delete existing comments on work items.<\/p>\n

Azure Repos:<\/strong><\/p>\n

Rebase<\/a> & Fast-forwarding<\/a> as merge options for pull requests \u2013 Public Preview \u2013 2019 Q1<\/strong><\/p>\n

Teams use pull requests to review and merge code changes in their git repositories. Today Azure Repos only supports merge with the option to squash commits when completing the pull requests. We are working on enhancing this to enable rebase and fast-forwarding as options when completing pull requests. These improvements will also include the capability of enforcing any subset of the pull request completion options via branch policies.<\/p>\n

Branch policies administration improvements<\/a> \u2013 Public Preview \u2013 2019 Q2<\/strong><\/p>\n

Branch policies<\/a> are powerful features of Azure Repos that help teams protect their branches. In Q2 we plan to ship improvements to the branch policies administration experience to make it easier for users to set policies for multiple branches and repos without having to navigate away from the branch policies administration page. We will also enable the capability to set a policy for all repositories in the same project.<\/p>\n

Azure Pipelines:<\/strong><\/p>\n

GitHub Enterprise and BitBucket support for YAML-based pipelines<\/a> \u2013 2019 Q1<\/strong> You will be able to configure a pipeline in Azure Pipelines for your GitHub Enterprise or BitBucket repository using a YAML file.<\/p>\n

Hosted pools and visibility into concurrency usage<\/a> \u2013 2019 Q1<\/strong> Currently, you see multiple hosted pools and agent slots for each of the agent pools in your organization. We are updating the hosted pools experience to have a single agent pool. This will allow you to browse all the jobs running in that pool in a single place.<\/p>\n

YAML editor in the web<\/a> \u2013 2019 Q1<\/strong> To make it easier for you to author YAML pipelines, we are adding some of the features of the<\/p>\n

visual designer<\/a> into the YAML editor. For example, you will be able to use a task assistant to add new tasks to the YAML file.<\/p>\n

Multi stage pipelines<\/a> \u2013 2019 Q1<\/strong> We will expand the current single-stage YAML pipelines to support multiple stages with approvals. With this, you will be able to author the entire pipeline from build to release in code using YAML.<\/p>\n

Azure Artifacts:<\/strong><\/p>\n

Full support for Azure Artifacts in Release Management, continued rollout of upstream sources<\/a> \u2013 2019 Q1<\/strong><\/p>\n

In Q1, we\u2019ll be enabling all Azure Artifacts package types \u2013 Maven, npm, NuGet, Python, and Universal \u2013 to be used as an artifact that triggers a release. We\u2019ll also continue to invest in upstream sources, bringing them to Maven, making them available across Azure DevOps organizations, and shortening the \u201crefresh time\u201d to fifteen minutes between when a package is published to a feed and when it\u2019s available via upstream sources.<\/p>\n

Reporting:<\/strong><\/p>\n

Build failures report<\/a> \u2013 2019 Q1<\/strong><\/p>\n

As adoption of Azure Pipelines continues to grow, we want to provide metrics and actionable insights to improve the throughput and stability of a pipeline. In Q1, we will report on the trend of a pipeline by showing the success rate along with insights on how to improve it.<\/p>\n

Administration:<\/strong><\/p>\n

Connect to Azure Active Directory (AAD), set up billing, and updated security and org settings<\/a> \u2013 2019 Q1<\/strong><\/p>\n

We\u2019re continuing to make it easier to administer Azure DevOps by adding improved experiences for connecting to AAD and setting up or modifying billing within Azure DevOps administration. We\u2019re also addressing two of the top voted Developer Community posts by rolling out an improved security and organizations settings and giving users the ability to change their project profile image from the Project Overview settings page.<\/p>\n

Marketplace:<\/strong><\/p>\n

Publisher Certification<\/a> \u2013 2019 Q1<\/strong><\/p>\n

We plan to ship a top publisher program designed to help you acquire extensions with confidence.\u00a0 A top publisher icon will be displayed for a publisher once it meets our policies, adoption and support benchmarks.<\/p>\n

We appreciate your feedback, which helps us prioritize. If you have new ideas or changes you\u2019d like to see, provide a suggestion on the Developer Community<\/a><\/strong> or vote for an existing one.<\/p>\n","protected":false},"excerpt":{"rendered":"

Last week we updated the Features Timeline to provide visibility on our key investments for this quarter. The features listed below link to the public roadmap project where you can find more details about each item.<\/p>\n","protected":false},"author":1006,"featured_media":54298,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[224],"tags":[],"class_list":["post-54060","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure"],"acf":[],"blog_post_summary":"

Last week we updated the Features Timeline to provide visibility on our key investments for this quarter. The features listed below link to the public roadmap project where you can find more details about each item.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/54060","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/1006"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=54060"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/54060\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/54298"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=54060"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=54060"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=54060"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}