Imaginet’s Top 6 Favorite New Features of TFS 2017
With the recent release of Visual Studio 2017, now is a great time to upgrade your Team Foundation Server (TFS) to 2017!
This new release is jam-packed with over 25 new features and fixes that help your team develop software better by improving communication and collaboration throughout your software development process. Here are just a few reasons why you should consider upgrading to TFS 2017:
1. Build Improvements
Task versioning for Build and Release definitions
- With TFS 2017, you can now control and specify the major version of a task resulting in fewer unpredictable errors caused by automatic updates.
- “When a minor version is released (for example, 1.2 to 1.3), you get that change automatically in your build. But if a new major version is released (for example 2.0), then your build stays locked to version 1.3 until you edit the definition and manually change to the new major version. A flag in the build definition alerts you to new major versions.”
Rollback build definitions
- In the History tab, you can now roll a build definition back to a previous version.
2. Package Improvements
Release views in Package Management
- With release views, you can create and share your package’s consumers to control which versions take dependency.
- This is great when you’re frequently publishing version updates but do not want to announce or support each version.
npm in Package Management
3. Test Improvements
Verify bugs from work item
- You can now verify a bug by re-running the tests which identified the bug. 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.
Update existing bugs from Web Runner
- In addition to creating new bugs from the Web runner, now you can also update an existing bug. All the diagnostic data collected, repro steps, and links for traceability from the current session are automatically added to the existing bug.
Test Impact Analysis for managed automated tests
- The most exciting new feature of TFS 2017 is the Test Impact Analysis. Only the relevant set of managed automated tests that need to be run and be validated are given a code change. Test Impact Analysis requires the latest version of Visual Studio, and is presently supported in CI for managed automated tests.
4. Release Management Improvements
Variable groups support in Release
- Variable groups are used to group your variables and their values to make them available across multiple release definitions. You can also manage security for variable groups and chose who can view, edit, and consume the variables from the variable groups in your release definitions.
Multiple schedules in releases
- Want to schedule your releases to be created more than once a day? You can now configure multiple scheduled triggers in a release definition.
Link build artifacts from another team project
- Until now, release definitions could only link artifact sources from the current project. Now, you can link build artifacts from another project as well. While linking an artifact, the project drop down will list all the projects in the account.
5. Team Room Deprecation
- With so many good solutions available that integrate well with TFS and Team Services, such as Slack and Microsoft Teams, Microsoft has made a decision to depreciate our Team Room feature from both TFS and Team Services. If you are working in Team Services, you will see a new yellow banner appear that communicates our plan. Later this year, Microsoft plans to turn off the Team Room feature completely.
6. Announcing the Process Template Editor
- This extension provides a convenient method for viewing and updating process templates, as well as tools for updating global lists and work item types, and viewing the attributes of work item fields.