With task group versioning, now you can draft and preview task group versions while still offering stable versions to your most important definitions until you are ready to switch.
To help you track the consumers of a task group, you now have a view into the build definitions, release definitions, and task groups that reference your task group (Figure 79).
Beyond applying a keyword filter across displayed columns and selecting tags, you can also filter on work item types, states, and assigned to, in order to quickly get to the work items you are looking for.
Based on past running time of tests, which considers past running time to create batches of tests such that each batch has approximately equal running time (Figure 100).
With the newly available expand option on Kanban cards, you can now benefit from hiding empty fields across the board, but still have single click access to update a particular field on a card.
Visual Studio helps you find your way around more easily, without losing the context of the code or the markup you started from, with capabilities like Peek to definition, Navigate To, and Quick Find.
Like the way you to do for test results in Build, you can now create trend charts showing test pass rate, count of total, passed or failed tests, and test duration for Release Environments.
See the Load test your app in the cloud using Visual Studio and VSTS quickstart as an example of how you can use this together with load testing.
We are adding support for Release Environments in the Test Result Trend widget (Figure 99) so that you can track status of test environments on VSTS dashboards.
You can already clone and make templates from your build definitions, but many users have wanted to take a copy of their CI build logic and reuse it in another team project.
It can be especially beneficial for instances where you need to create USB setup media from bootable ISOs (Windows, Linux, and so on), to service a system that doesn't have actually an.
Any variables defined and available in the release can be included, and the values are used in the notifications as well as in the email sent to users (Figure 86).
Wise Registry Cleaner could situate and also remedy problems in the Windows windows registry, such as missing out on references to shared DLLs, extra enrollment entries for data extensions, and also missing referenced application paths.
When preparing a PR or commenting you sometimes have a short list of things that you want to track but then end up editing the text or adding multiple comments.
In the Trigger section of the environment Deployment conditions dialog (Figure 87), select the artifact conditions such as the source branch and tags for builds that will trigger a new deployment to that environment.
For old repositories, the number of tags can grow significantly with time; there can also be repositories that have tags created in hierarchies, which can make finding tags difficult.
Similarly, if you plan to upgrade agent machines, you can choose to pause a build definition, which enables VSTS to still accept new build requests but hold them in queue without running until you resume the definition.
Sometimes, it is hard to make sense out of a PR comment after the code it is referencing has changed (many times, when a requested change has been made) (Figure 35).
We ship a number of them in the box today and while you could upload new ones to your account, it was never possible for extension authors to include new templates as part of an extension.
Any word on whether there will be a version of TFS 2017 power tools available soon, or if it safe to use the TFS 2015 power tools with VS2017?
The filter matches any part of the path of the files in the pull request, so you can search by folder names, partial paths, file names, or extensions (Figure 33).
Today, if you want to know whether a commit is deployed to your customer production environment, you first identify which build consumes the commit and then check all the release environments where this build is deployed.
Up until now, users would need to temporarily boot the TWRP recovery image and then flash the TWRP installer script to permanently install TWRP on the said devices.
If you have branch structure in a hierarchical format where all branches are prefixed with a text, then this feature will help you to find a commit in all the branches starting with that prefix text.
In addition to the filters on Test fields like Outcome, Configuration, and Tester, you can now filter on Test Case work item fields like Title, State, and Assigned To (Figure 98).
The name of the author has been added to the subject to make it simpler to apply rules and filters based on the person that created the PR.
The Manual Intervention task (Figure 85) now supports the use of variables within the instruction text shown to users when the task runs, at the point where the user can resume execution of the release process or reject it.
This archive contains SDK releases and updates for earlier Windows and Windows Phone platform versions, as well as emulator releases supporting development and UX testing for mobile device experiences.
Instead of getting notifications for all folders in a repo, you can now choose to get notified when team members create pull requests or push code in only the folders that you care about.
You can update Test Result comments in the Result Summary page with Update analysis and Test Run comments in the Run Summary page with Update comments in Test hub.
By specifying variable multipliers for server side (agentless) tasks (Figure 84), you can now run the same set of tasks in a phase on multiple configurations, which run in parallel.
In previous versions of the task's publish command, the task modified the output path by putting all the files in a folder that was named after the project file name, even when you passed an explicit output path.
If you used the web version of the Team Project creation, you can run the tfsconfig command on the Application Tier to provision or update the SSRS reports.
Release Management now supports configuring a continuous deployment trigger (Figure 89) for Git repositories linked to a release definition in any of the team projects in the same account.
If you plan to make changes to your build definition and you want to avoid queuing any new builds until you are done, simply disable the build definition.
Validation expressions follow the familiar expression syntax used for task conditions and can use any of the supported functions besides the general functions supported by task conditions, including URL, IPV4, email, number range, sha1, length, or match.
After some drafting and iteration, you can publish a stable version and, while publishing, if the changes are breaking in nature, you can choose to publish the task group as preview (a new major version).
Use the secure files library to store files such as signing certificates, Apple Provisioning Profiles, Android Keystore files, and SSH keys on the server without needing to commit them to your source repository.
This is a smart filter that shows child files of a folder when you filter by folder name and shows a collapsed tree view of a file to display the file hierarchy when you filter by file name.
Quick Info tool tips let you inspect API definitions, and squiggly lines let you know about issues, often showing them as you type.
Now this experience is much easier with the integration of the deployment status in the Code hub status badge to show the list of environments that your code is deployed to.
If you are unable to find the tag that you were looking for on the Tags page, then you can simply search for the tag name using the filter on top of the Tags page (Figure 27).
When this happens, you will now see a badge with an update number that you can click to see what the code looked like at the time the comment was originally created (Figure 36).
If you find yourself managing multiple Team Projects for an organization and have recurring tasks and questions that repeat themselves over and over again, Team Project Manager probably has some answers for you.
This is especially useful for large accounts that have multiple stakeholders for releases, and for those other than the approver, release creator, and environment owner that might want to be notified (Figure 97).
Finally, work items created while not specifically exploring any requirement are filed in the team's default iteration instead of the current iteration so that no new work items come into the current iteration after the sprint planning is complete.
Previously, if you were using an extension that had build tasks and build summary sections, you would see the build summary section even if you were not using the build task in that build.
This means you can specify the releases that are deployed to each environment when the deployment trigger conditions (such as a build succeeding and creating a new release) are met.
Work item form custom controls, groups, and pages can now block work item save to validate data and ensure the user fills out any required information before saving the work item form.
All of our work item tracking grid experiences (queries, backlogs, Kanban boards, sprints backlogs, and test case management) now make use of our common, consistent filtering component (Figure 4).
