In the build details view for a build triggered by a pull request, the source will now show a link to the pull request that queued the build. In the Build Definitions view, any build triggered by a pull request will provide a link to the pull request in the "Triggered By" column.
Finally, the Build Explorer view will list pull requests in the source column. Pull requests in VSTS have been improved to show comments left in files on the proper line, even if those files have been changed since the comments were added.
Previously, comments were always shown on the line of the file where they were originally added, even if the file contents changed—in other words, a comment on line 10 would always be shown on line With the latest improvements, the comments follow the code to show what the user expects—if a comment is added on line 10, and two new lines were subsequently added to the beginning of the file, the comment is shown on line Even after the code has changed to shift the line with the original comment from 13 to 14, the comment is appearing in the expected place on line 14 Figure Teams that are using branch policies to protect their branches will want to check out the auto-complete action.
Many times, the author of a pull request is ready to merge their PR, but they are waiting on a build to finish before they can click Complete.
Other times, the build is passing, but there is one reviewer that has not given the final approval. In these cases, the auto-complete action lets the author set the PR to automatically complete as soon as the policies are all approved Figure Just like the manual complete action, the author has a chance to customize the message of the merge commit and select the appropriate merge options Figure Once auto-complete has been set, the PR will display a banner that confirms that the auto-complete is set and waiting for policies to complete Figure When all the policies are met e.
As expected, if there is a build failure or the reviewer does not approve, the PR remains active until the policies are passing. When completing a pull request, you now have the option to squash merge Figure This new option produces a single commit containing the changes from the topic branch that is applied to the target branch. The most notable difference between a regular merge and a squash merge is that the squash merge commit will only have one parent commit.
This will mean a simpler history graph, as any intermediate commits made to the topic branch will not be reachable in the resulting commit graph. You can find more information at Squash merge pull requests. Build status success or failure is now clearly visible in the Code Explorer and Commit Details views Figure More details are just a click away, so you will always know if the changes in the commit passed the build or not.
You can also customize which builds post status in the repository options for the build definition. Additionally, the latest changes to the Commit Details view provide deeper insights about your changes. If you're using pull requests to merge your changes, you will see the link to the pull request that introduced the changes into the main branch or in the case of a merge commit, the PR that created it.
When your changes have reached main, the branch link will appear to confirm that the changes have been included. If you're already working with large files in Git audio, video, datasets, etc. This makes it possible to view the full contents of these large files by simply clicking the file in your repo. For more information, see Manage large files with Git. Share code references easily with code links Figure Just select text in a file and click the Link icon.
It will copy a link to the selected code. When someone views that link, the code you highlighted will have a gold background. It even works for partial line selections. Success or failure of the build is now clearly visible in the code explorer and commit details views Figure More details are just a click away, so you always know if the changes in the commit passed the build or not.
You can also customize which builds post build status in the repository options for the build definition. You will see new file icons matching the extension of the file in the explorer, pull requests, commit details, shelveset, changeset or any other view that shows a list of files Figure The new Git repository creation has been improved by providing users the ability to add a ReadMe file Figure Adding a ReadMe to the repository not only helps others understand the purpose of the codebase, but also allows you to immediately clone the repository.
In this release, we have increased the size of the logs, added Java build templates, and improvements to our Xamarin support to name a few changes. We have implemented a new design for the Queued builds page that shows a longer list of queued and running builds, and in a more intuitive fashion Figure For more information, see Administer your build system. Build result section extensions can now specify which column and the order in which they appear Figure The result view has two columns, and all extensions are in the first column by default.
Note: All third-party extensions will appear after the build result sections we include. Now you can jump from a build error to the line of code that caused it. Looking at the latest error on the primary build we use as a pull request policy internally, you see this Figure 40 :.
The previous log view only supported logs up to 10, lines. The new viewer is based on the Monaco editor used in VS Code and will support logs up to , lines. We have made it even easier for Java developers to get started with build by adding build templates for Ant, Maven, and Gradle Figure For more information on templates, see Build steps. The Xamarin License step is no longer necessary and has been removed from the build templates. As part of this effort we are deprecating the task. All build definitions that use this task should be updated to remove it in order to prevent any disruption when the task is finally removed.
Finally, we have enhanced the Xamarin build definition templates to use these new tasks. Build your Xamarin app. Take advantage of the build capabilities to build your Docker images and upload them to the Docker Hub as part of your continuous integration flow Figure Then, deploy those images to a number of Docker hosts as part of Release Management.
The Marketplace extension adds all the service endpoint types and tasks necessary for you to work with Docker. If the build run to merge a pull request contains SonarQube MSBuild tasks, you will now see new code analysis issues as discussion comments in the pull request Figure This experience works for any language for which a plug-in is installed on the SonarQube server.
You can now choose which build definitions report their status back to the Git status API. This is particularly useful if you have many definitions that build a given repository or branch, but only have one that represents the real health. It has been always possible to add notifications of XAML builds in the team room. With this sprint, users can also receive notifications from Build vNext completions. CI triggers for hosted Git repositories can include or exclude certain paths.
This enables you to configure a build definition to run only when files in specific paths have changed Figure Since the introduction of integrated web-based Release management in Team Foundation Server , we have made several enhancements in this version.
We have incorporated the ability to clone, export, and import release definitions within Release hub, without requiring installation of an extension Figure For more details, see Clone, export, and import a release definition documentation.
In the release summary page, we have enabled a contribution point for an external service to show environment-specific information. In Team Services, this functionality is used to display a summary of test results when tests are run as part of a release environment Figure For more details, see Understand the summary view of a release documentation. A new option when you configure an environment allows scripts to run as tasks in the environment to access the current OAuth token Figure For more details, see Environment general options documentation.
Build and release tasks have an option to Continue on error in the Control Options parameters for each task. In a build definition, this results in a Build partially succeeded result if a task with this option set should fail.
The same behavior is now available in release definitions. If a task fails, the overall release result will show as "Release partially succeeded" Figure By default, a partially successful release will not automatically trigger a release to a subsequent environment, even if this behavior is specified in the environment deployment options. However, a new option can be set in each release environment that instructs Release Management to trigger a release to a subsequent environment when the previous release is partially successful Figure For more details, see Environment deployment triggers documentation.
Sometimes you may want to consume artifacts stored in a version control system directly, without passing them through a build process, as described in this topic. NET 4, Node, and Python based web apps. The task also supports common publishing options such as the ability to retain app data, take an app off-line, and remove additional files at the destination.
More features, such as configuration transformations, may appear in forthcoming versions Figure A task group lets you encapsulate a sequence of tasks already defined in a build or a release definition into a single reusable task that can be added to a build or release definition just like any other task Figure You can choose to extract the parameters from the encapsulated tasks as configuration variables, and abstract the rest of the task information. The new task group is automatically added to the task catalogue, ready to add to other release and build definitions.
For more details, see Task Groups documentation. When you delete a release, or it is automatically deleted by a retention policy, the release is removed from the overview and details lists. However, it is retained with the release definition for a period typically 14 days before it is permanently deleted. During this period, it is shown in the Deleted tab of the overview and details lists. You can restore any of these releases by opening the shortcut menu and choosing Undelete Figure For more details, see Restore deleted releases documentation.
The release retention policy for a release definition determines retention duration for a release and linked build. By default, a release is retained for 60 days. Releases that have not been deployed or modified during that time are automatically deleted.
However, you may want to retain more releases that have been deployed to specific environments, such as your production environment, or retain them longer than those that were just deployed to other environments such as test, staging, and QA.
You can also retain the build linked to a release for the same period as the release to ensure that the artifacts are available if you need to redeploy that release Figure For more details, see Release and build retention documentation. Including a Manual Intervention task in an environment enables you to temporarily halt a deployment, perform manual steps, and then resume further automated steps. You can also reject the deployment and prevent further steps from executing after a manual intervention Figure For more details, see Manual intervention documentation.
The scripts can be provided as a file, or inline within the task. Pin a release definition to the dashboard - an easy way to make a summary of releases for that definition visible to all your team. For more details, see Add release information to the dashboard documentation. Want all your production deployments to happen at midnight? You can configure a condition on an environment that selects a successful deployment or just the latest one from another environment, and deploys it at the specified time Figure Until the previous version, you could do parallel deployments forkdeployments , but you could not start a deployment to an environment based on the status of multiple environments join deployments.
Now you can. For more details, see Parallel forked and joined deployments documentation. For more information, see the API reference documentation. Send release notifications when new releases are created, deployments are started or completed, or when approvals are pending or completed. Integrate with third party tools such as Slack to receive such notifications. For more details, see Azure Classic service endpoint documentation.
In this release, we are migrating the test result artifacts to a new compact and efficient storage schema. Since test results are one of the top consumers of storage space in TFS databases, we expect this feature to translate into reduced storage footprint for TFS databases.
For customers who are upgrading from earlier versions of TFS, test results will be migrated to the new schema during TFS upgrade. This upgrade may result in long upgrade times depending on how much test result data exists in your databases.
It is advisable to configure the test retention policy and wait for the policy to kick in and reduce the storage used by test results so that the TFS upgrade is faster. See TFSConfig. If you do not have the flexibility to configure test retention or clean up test results before upgrade, make sure you plan accordingly for the upgrade window.
See Test result data retention with Team Foundation Server for more examples about configuring test retention policy. We have brought test configuration management to the web UI by adding a new Configurations tab within the Test Hub Figure Now you can create and manage test configurations and test configuration variables from within the Test hub.
For more information, see Create configurations and configuration variables. Assigning configurations just got easier. You can assign test configurations to a test plan, test suite, or test case s directly from within the Test hub Figure Right-click an item, select Assign configurations to … , and you're off and running. You can also filter by Configurations in the Test hub Figure For more information, see Assign configurations to Test plans and Test suites. We have added new columns to the Test results pane that show you the test plan and test suite under which the test results were executed in.
These columns provide much-needed context when drilling into results for your tests Figure You can now order manual tests from within the Test Hub Figure 65 , irrespective of the type of suite in which they are included: static, requirement-based, or query-based suites. You can simply drag and drop one or more tests or use the context menu to reorder tests. Once the ordering is completed, you can sort your tests by the Order field and then run them in that order from the Web runner. You can also order the tests directly on a user story card on the Kanban board Figure Test teams can now order the test suites as per their needs.
Prior to this capability, the suites were only ordered alphabetically. As part of the rollout of new identity picker controls across the different hubs, in Test hub, we have also enabled the option to search for users when assigning testers to one or more tests Figure You can now pick the "build" you want to test with and then launch the Web runner, using 'Run with options' in Test hub Figure Any bug filed during the run is automatically associated with the build selected.
In addition, the test outcome is published against that specific build. The Microsoft Test Runner launches without opening the entire Microsoft Test Manager shell and will shut-down on completion of the test execution. For more information, see Run tests for desktop apps. You can now choose your data collectors and launch the Exploratory Runner client in a performant way from Test hub, without having to configure them in Microsoft Test Manager client.
Invoke 'Run with options' from the context menu Figure 72 for a Requirement based suite and choose Exploratory runner and the data collectors you need. The Exploratory runner launches similar to Microsoft Test Runner as described above. We have now added the ability to configure the behavior of test outcomes for tests shared across different test suites under the same test plan Figure Users can set the "Configure test outcomes" option for a particular test plan either from the Test hub test plan context menu or from the Kanban board test page in the common settings configuration dialog.
This option is turned off by default and you will have to explicitly enable it to take effect. You can now verify a bug by re-running the tests which identified the bug Figure You can invoke the Verify option from the bug work item form context menu to launch the relevant test case in the web runner. Perform your validation using the web runner and update the bug work item directly within the web runner. You can now add, view, and interact with test cases directly from your stories on the Kanban board.
Use the new Add Test menu option to create a linked Test case, and then monitor status directly from the card as things progress Figure With this new capability, you can now perform the following actions directly from a card on your board:. If you need advanced test management capabilities like assign testers, assign configurations, centralized parameters, exporting test results, etc. For more information, see Add, run, and update inline tests.
Clicking on this link Figure 76 will take you to the Test hub, open the right test plan, and then select the specific suite that controls those inline tests. Use the new Tests page in common settings configuration dialog on Kanban board to control the test plan where the inline tests are created Figure Now, you can override this behavior by configuring an existing test plan of your choice — all the tests are added to the selected test plan. Note that this functionality is only enabled if the Test annotation is turned on.
We have enhanced the Web test runner to give you the ability to add test step attachments during manual testing Figure These step result attachments automatically show up in any bugs you file in the session and subsequently in the Test results pane. You can now take screenshots and annotate them inline when you use Web runner in Chrome Figure You can also capture on-demand screen recordings of not just the web apps, but also your desktop apps.
These screenshots and screen recordings are automatically added to the current Test step. You need to specify the browser window on which to capture your actions — all actions on that window any existing or new tabs you open in that window or any new child browser windows you launch, will automatically be captured and correlated against the test steps being tested in the Web runner.
These screenshots, screen recordings and image action logs are then added to any bugs you file during the run and attached to the current test result. Similarly, the system information data is automatically captured and included as part of any bugs you file from the Web runner.
For more information, see Collect diagnostic data during tests. When running tests in Web runner, launched either from a card on the board or from a requirement-based suite in Test hub, any new bugs filed will now be automatically created as a child to that user story.
Similarly, if you are exploring a user story from the exploratory testing extension, any new bugs you file are also created as a child to that user story. This new behavior allows for simpler traceability across stories and bugs.
This is applicable only if the "Working with bugs" settings in the Common Settings Configuration page is set to "Bugs do not appear on backlogs or board" or "Bugs appear on the backlogs and boards with tasks".
For all other settings for "Working with bugs" option and in certain other scenarios, such as adding to an existing bug that already has a parent defined, a Related link is created instead. In addition to creating new bugs from the Web runner, now you can also update an existing bug Figure All the diagnostic data collected, repro steps, and links for traceability from the current session are automatically added to the existing bug.
You can now do exploratory testing for a specific work item Figure This lets you associate the selected work item with your ongoing testing session, and view the acceptance criteria and description, from within the extension.
It also creates end-to-end traceability between bugs or tasks that you file on the selected work item. You can explore the work item either directly from a work item, or from within the extension:. We have added entry points on all cards, grids, and in the Test hub. Image Action Log: The extension gives you a new option to add the steps that lead you to the bug automatically with just one click.
Select the "Include image action log" option Figure 83 to capture the mouse, keyboard, and touch actions, and add the corresponding text and images directly into the bug or task. Screen recording as video: You can also capture on-demand screen recordings using the extension.
These screen recordings can be captured not just from the web apps, but also your desktop apps. You can configure the extension to automatically stop screen recordings and attach them to a bug being filed using the extension's "Options" page. Page Load Data: We have added a new background capture capability to the extension — capturing of "web page load" data. Just like the "image action log" captured your actions performed on a web app being explored, in the form of images in the background, the "page load" functionality automatically captures details for a web page to complete the load operation.
Once the bug is filed, in addition to the tile view, a detailed report is also attached to the bug, which can help the developer with their initial set of investigations. When you create test cases during your exploratory session, the test steps with images are automatically filled in for you Figure Simultaneous test design and test execution is the basis of true exploratory testing, and this new capability makes this a reality. For more information, see Create test cases based in image action log data.
You can get to this insights page by clicking the "Recent exploratory sessions" link in the Runs hub within the Test Hub group in web access. This new view helps you derive meaningful insights, including:. For more information, see Get insights across your exploratory testing sessions. You start by specifying a shared query for work items that you are interested in and the sessions page shows a list of all the work items from the query, with a breakdown of both explored and unexplored items in the summary section.
In addition, using the "Unexplored Work Item" group by pivot, you can see the list of items that have not been explored yet. This is extremely useful to track down how many stories have not been explored or gone through a bug-bash yet. This opens the Request feedback form where you can choose the stakeholders you want feedback from and optionally provide a simple set of instructions prompting for the areas of the product you would like input.
This will send off individual mails to the selected stakeholders along with the instructions provided, if any. Additionally, stakeholders can navigate to the "Feedback requests" page to view in one place all feedback requests received by them. From the list, they can select the feedback request they want to provide feedback on, manage their "Pending feedback requests" Figure 88 by marking them as complete or by declining them and can switch between different types of feedback requests by clicking on the desired radio button Figure In addition to the solicited flow mentioned above, stakeholders can also use the extension to provide voluntary feedback Figure Test result console logs that are captured in.
You have an option to preview them in Tests tab, and do not need to download the trx file to view logs anymore. We have added a new 'Test result trend' widget to the Widget Gallery Figure Use this widget to add a test result trend chart of up to 30 most recent builds for a build definition to the dashboard. Widget configuration options can help you customize the chart to include pivots like passed test count, failed test count, total test count, pass percentage, and test duration.
It is a recommended practice to use Release Environments to deploy applications and run tests against them. With this release, we have integrated test pass rate of Release Environments in the Environments section of the Release summary page Figure As shown in the screenshot, if an Environment has failed, you can quickly infer if the failure is because of failing tests by looking at the Tests column.
You can click on the pass rate to navigate to the Tests tab and investigate the failing tests for that Environment. It is a common scenario for an individual test to run on multiple branches, environments, and configurations. When such a test fails, it is important to identify if the failure is contained to development branches like the main branch or if failures also impact release branches that deploy to production environments. It is especially useful for those who are required to download files continually.
More Compatibility Pack for the Office system Microsoft has added new file formats to Microsoft Office Word, Excel, and PowerPoint to reduce file size, improve security and reliability, and enhance integration with external sources.
Office File Validation is a security add-in for Office and More Microsoft Office Microsoft Office is a powerful tool that can provide you with the best way of delivering your work. Descriptions containing tfs office integration download. More WinRAR 6. WinRARs main features are very strong general and multimedia compression, solid compression, archive protection from damage, processing … more info More Microsoft OneDrive Store any file on your free OneDrive fromer SkyDrive and it's automatically available from your phone and computers—no syncing or cables needed.
More Windows Live Essentials Windows Live Essentials previously Windows Live Installer is a suite of freeware applications by Microsoft which aims to offer integrated and bundled e-mail, instant messaging, photo-sharing, blog publishing, security services and other … more info Audio chipsets from Realtek are used in motherboards from many different manufacturers.
If you have such a motherboard, you can use the drivers provided by Realtek. More UpdateStar Premium Edition UpdateStar 10 offers you a time-saving, one-stop information place for your software setup and makes your computer experience more secure and productive.
Additional titles containing tfs office integration download. Latest News.
0コメント