Team Foundation Server 2008 Overview
- 1. Steve Lange | Developer Technology Specialist | Microsoft [email_address] Team Foundation Server
- 2. Introductions What is Team Foundation Server? TFS Walkthrough Process Guidance & Automation Project Portal Source Control Work Item Tracking Interfaces/Integrations Build Automation Reporting Q&A Close & Next Steps
- 3. Team Foundation Server A unified project server Tester Developer Architect Project Manager Business Analyst Designer Database Professional
- 6. Data Tier Data Warehouse Version Control Work Items Team Build SQL Server 2005 Windows SharePoint Services Web Services Application Tier SQL Reporting Services Client Interface Visual Studio Team Explorer MS Project MS Excel TFS Web Access Command Line Build Environment Build Process Version Control Proxy Version Control Proxy Service
- 8. Embedded into Team Foundation Server Provides contextual guidance (documentation) Delivered via Process Templates Helps ensure predictability
- 9. Configures TFS to support your Development Process MSF Agile and MSF for CMMI Several 3 rd party templates Scrum, RUP, EssUP, XP, ThoughtWorks, Avanade … Create your own or modify an existing one Stored in an XML file Process Template Editor tool
- 10. Configures: Types of Work Items Use Case, Task, Bug, Change Request, … Contents of each Work item Type UI for each Work Item Type Process Guidance documentation Layout for SharePoint Portal Types of Reports
- 11. Leverages SharePoint WSS 3.0 SharePoint Portal Server 2007 / MOSS Surface guidance, documentation, reports, external collaboration
- 15. Logical container of data related to check-in File and branch information Links to work items Check-in notes Comment Policy compliance Metadata (date, time, user) Unit of atomic checkin Uniquely identified Numeric identifier Incremental Represents a point in time of source repository
- 16. 12 V5 9 12 4 12 Changeset 12 WorkItem 158 Checkin Event Artifact Link Workspace Validate Policies 1 Checkin Policy Engine Checkin Tests Work Items Custom Policy Static Analysis Commit Changes 2 Update Work Items 3 Checkin Mail 4
- 17. Client side copy of source checked out from repository Owned by one user on one machine Changes in workspace create “pending changes” Workspace Mapping = Repository folder mapped to Local Folder
- 18. Atomic A changeset is guaranteed to have all changes from a check-in Integrated Check-in policy applied (but override-able) Work Items associated Builds associated with Work Items Check-in notes All related to changeset Pending Check-in Window Notification possibilities Check-in Policy Customizable, extensible
- 20. Branch A branch relationship is created in TFS to avoid duplication of history and metadata Path-space branching Intelligent copies Merge Sync a branch into another Cherry Picking changesets (include or omit) Ability to show changes that have not been merged
- 21. Set aside pending changes without checkin Optionally revert to unmodified files Restore shelved changes by “unshelving” Unshelve other user’s changes Power of task branching with less overhead Shelving Developer Switch Tasks Backup Work-In-Progress Checkpoint Work-In-Progress Share Work-In-Progress Perform a Code Review
- 22. Capability VSS TFS Changesets X Atomic Check-in X Shelving X Branching & Merging X X Work Item Integration X Check-in Policies X Annotation X Locking Exclusive Exclusive/Shared/None Diff/Merge Tools Supplied only Supplied or external, per file type Storage File system SQL Server Communication File system/UNC HTTP/S Security Read/Write Multi-layered Authentication App-specific Active Directory Integrated Build X Reporting X
- 24. Manages any “item of record” Extensible (fields, dialogs, workflow) Use familiar tools, including:
- 25. Title Description Current State Who it is assigned to Attachments Links to other Work Items Full Audited history Anything else you want … Closed Active Resolved Closed Active Resolved Proposed Scenario Tasks Bugs
- 27. Extension of MS Build Several scenarios supported Continuous Integration Scheduled Rolling Ad-hoc Provides build reporting back to TFS Integrated testing
- 45. © 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
- 49. Visual Studio Team System Team System Case Studies TFS Best Practices Guide SOX Compliance & Team System Requirements Management Whitepaper Steve’s Blog on RM and TFS Videos “How Do I?” VSTSRocks.com
- 54. © 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Editor's Notes
- 06/08/09 12:49 © 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.